Section 5 · Cloud Applications · 11% of exam
5.4 Salesforce product suite and platform extension choices
Exam objective
Given a scenario, identify the appropriate standard Salesforce products that extend the core platform. Salesforce provides products and clouds for different business capabilities, including sales, service, marketing, commerce, analytics, integration, and industry workflows. The administrator's task is not to memorize every product label; it is to identify the business capability and evaluate whether a standard cloud, platform configuration, or external integration is appropriate. Core objects and features can meet many requirements, while a specialized product may provide additional workflows, data models, user experiences, or governance.
Translate a request into capabilities. A sales pipeline, account and opportunity management, and sales forecasting are sales functions. Case management, service entitlements, knowledge, and channel routing are service capabilities. Digital customer portals and self-service can involve Experience Cloud. Integration and API orchestration may call for MuleSoft or platform APIs, depending on scale and complexity. Reporting may be supported by Salesforce reports and dashboards or a separate analytics product. The right choice depends on data volume, user roles, latency, security, and existing architecture.
Before recommending a product, check the organization's license entitlements, editions, limits, and release availability. A product name does not guarantee that the customer's org includes the required capability. Review how the solution connects to existing objects and systems, whether data is copied or referenced, and how identity and access are enforced. Consider implementation effort, maintenance, integration ownership, and user adoption in addition to feature fit. Standard platform extension options include declarative configuration, AppExchange packages, custom code, APIs, and external systems. Prefer supported configuration for straightforward record, process, and interface needs. Use a managed package when a trusted publisher provides a supported capability with an upgrade path; review permissions, data access, package dependencies, and vendor maintenance. An unmanaged package exposes components without the same managed upgrade mechanism. In either case, test installation and upgrades in a sandbox and inspect permission sets before granting access.
A third-party product or integration can introduce new data flows and security responsibilities. Determine what data leaves Salesforce, where it is stored, how it is encrypted, who supports it, and how failures are monitored. Keep a system-of-record map to prevent two applications from independently overwriting the same field. Consider API limits, retry behavior, duplicate prevention, and data retention. A user interface improvement does not solve a data governance problem.
Scenario process: define the job to be done, identify the users and data involved, compare native capability with the available product suite, confirm licenses and technical prerequisites, and map operational ownership. Prototype the minimal solution and test an end-to-end user workflow. If a required feature is not included, show the licensing or integration dependency explicitly. Avoid selecting a product solely because its name appears to match the requirement. Exam focus: recognize that Salesforce offers capabilities beyond the core CRM objects and that product selection depends on requirements and licensing. Distinguish configuration from packaged extension and external integration. Identify security, data movement, support, and maintenance implications. The most appropriate answer is often the simplest supported option already available to the organization, provided it meets the complete requirement.
Product names, packaging, and entitlements change over time. Confirm current availability and licensing in official Salesforce product documentation and the customer's contract.
Product selection should include a capability gap analysis. List required users, records, transactions, channels, and service levels, then compare those requirements to what the current licenses and native platform can do. Mark each requirement as covered, dependent on configuration, dependent on an add-on, or unsupported. This makes assumptions visible before procurement or implementation. Include a future-state view: how the product will be monitored, upgraded, and retired if needs change. A product that solves today's interface request can create a long-term data and integration dependency, so keep a written owner and exit plan.
Practical scenario
A company wants a customer-facing portal for case submission and status tracking. Evaluate Experience Cloud against an internal-only console change: the users are external, so a portal is a capability fit, but external licenses, sharing sets or other supported sharing design, authentication, and case access must be planned. Test account separation and ensure one customer cannot access another customer's cases before launch.
Extra concept
AppExchange due diligence is part of platform extension. Review publisher reputation and support, package permissions, data access, upgrade behavior, external endpoints, and sandbox installation results. Treat installation as a production change with an owner and rollback plan.
Key takeaways
- Translate the requirement into capability before choosing a Salesforce product.
- Verify current licenses, prerequisites, data flows, and support ownership.
- Test packages and integrations in a sandbox with least-privilege access.
- Official references: https://help.salesforce.com/s/articleView?id=005298969&language=en_US&type=1 https://www.salesforce.com/products/ https://appexchange.salesforce.com/ https://trailhead.salesforce.com/content/learn/modules/platform_app_builder
