OrgReady

Salesforce Skills & Readiness

← Prepare for Your Next Developer Role

Lesson 2 of 18 · 8–12 min

The Salesforce Ecosystem and Major Clouds

Cloud names describe product areas; architects still need to understand the shared platform and data boundaries underneath them.

Learning sequence · data model first, security layers next
  1. What CRM and Salesforce Do
  2. The Salesforce Ecosystem and Major Clouds
  3. Org, App, Object, Field, and Record
  4. Standard and Custom Objects
  5. Common Standard Objects
  6. Field Types and Data Quality
  7. Objects, Fields & Records
  8. Lookup vs Master-Detail
  9. Many-to-Many Relationships and Junction Objects
  10. Profiles, Permission Sets & Object Access
  11. Field-Level Security
  12. OWD and Least-Privilege Record Access
  13. Opening Access: Role Hierarchy, Sharing Rules, Public Groups & Apex Sharing
  14. Apex First Steps
  15. Variables and Collections
  16. SOQL and DML Basics
  17. Why Asynchronous Apex Exists
  18. REST Callout Introduction

Your focus

Prepare for Your Next Developer Role

REVIEW · Review • Apply

  • Identify ownership and integration boundaries between products.

Learning objective

Distinguish the core roles of Sales, Service, Experience, Marketing, and Commerce products without treating them as isolated systems.

The concept

Sales Cloud supports pipeline work; Service Cloud supports customer care; Experience Cloud exposes branded sites; Field Service coordinates work at customer locations; and Health Cloud adds healthcare-focused capabilities. Commerce and marketing products support buying and engagement, Data Cloud unifies data for activation, MuleSoft connects systems, and Agentforce brings AI agents into governed business workflows. You do not need to learn every product now: first learn the core platform and the products relevant to your role.

Worked example

A customer can respond to a marketing journey, become an opportunity, buy through commerce, schedule a field visit, and open a service case. Data, identity, consent, and integrations cross those product boundaries.

Name the user and outcome first. Locate the system that owns each record, then mark integrations, identity, consent, and reporting needs.

Customer journey across products

  1. 1.Marketing

  2. 2.Sales

  3. 3.Commerce

  4. 4.Service

  • Marketing connects to Sales
  • Sales connects to Commerce
  • Commerce connects to Service

Common mistake

Assuming every Salesforce-branded product uses the same objects, runtime, or licensing model.

Interview angle

Explain the role of each cloud, then discuss ownership and integration rather than listing product names.

Pause and apply

Which system should own a customer's support case, and which systems only need a copy?

Official references

Reviewed 2026-09-23. Examples are illustrative; no code is executed here.

Key takeaways

  • Clouds align to business capabilities.
  • Data ownership and integration matter across product boundaries.

Practice next

No linked assessment is available for this lesson. Use the pause-and-apply question to check your reasoning.

Reading these lessons does not yet save completion. Challenge results continue to provide assessment evidence.