Section 2 · Salesforce Fundamentals · 18% of exam
2.1 Choose the Right Customization Approach and Extend the
Exam objective
Given a scenario, identify the boundaries of declarative customization and the use cases for programmatic customization; identify common scenarios for extending an org using AgentExchange.
Org
Declarative customization uses setup tools to configure platform behavior without writing application code. Objects, fields, relationships, formulas, validation rules, record-triggered flows, approval processes, Lightning App Builder, page layouts, and access settings are common declarative building blocks. Their advantages are faster iteration, easier handoff to administrators, and alignment with platform-managed behavior. Declarative does not mean effortless: designs still need requirements, access review, testing, documentation, and change management.
Programmatic customization includes Apex, Lightning Web Components, and integrations built with APIs. It becomes appropriate when the requirement needs complex algorithms, specialized user interaction, high-volume processing, reusable services, or integration behavior that declarative tools cannot express or cannot execute within their limits. Code also creates responsibilities: source control, developer skills, automated testing, security review, deployment coordination, and long-term maintenance. The exam tests judgment about fit, not a belief that either approach is always better.
A useful decision sequence is to define the trigger, inputs, outputs, volume, users, and failure behavior. Check whether a standard feature already solves the problem. Then map the requirement to declarative capabilities and test the edge cases. If the solution needs a complex multi-record transaction, an unsupported interaction, or a processing pattern that exceeds declarative limits, explain why a programmatic component is justified. Keep the code surface as small as possible and expose stable, understandable interfaces to administrators.
AgentExchange is Salesforce’s marketplace for solutions that extend Salesforce, including apps, components, and automation-related offerings. Evaluate a listing for the specific requirement, supported Salesforce editions and licenses, security model, data handling, installation instructions, release compatibility, vendor support, update history, and total cost. Installing a package does not remove the need to test it in a sandbox. Review requested permissions and connected-app access; a package can have broad effects even when its visible interface appears narrow. Applied scenario: A service team asks for an intake app that assigns requests by category, calculates a due date, and shows a guided checklist. Start with standard objects and a custom object only if the request has a distinct lifecycle or relationship needs. Use a formula for a display-only due-date calculation if it can be expressed from fields; use a flow if assignment or related-record updates must occur. If agents need a highly specialized interactive workspace beyond standard pages and flow screens, evaluate a custom Lightning component. The decision is based on the behavior and maintenance requirements, not on a preference for code.
Design and risk review: A frequent error is reaching for a marketplace package or code before checking standard functionality. The opposite error is forcing an elaborate flow to imitate a purpose-built component. For AgentExchange, do not infer trust or suitability from popularity alone: check publisher, permissions, data access, license, compatibility, support, and upgrade path. Test installation and uninstall consequences in a nonproduction org. If the package creates metadata or data dependencies, include those in the release plan. Salesforce Certified Platform App Builder | SU ·26 guide alignment 3 Exam lens: First translate the stated requirement into a measurable outcome. Identify the actor, record or object in scope, timing, access boundary, and exception path. Eliminate choices that solve only the visible interface while missing the underlying data, security, or lifecycle requirement. Then compare the remaining supported features by fit, operational complexity, maintainability, and any dependency named in the scenario. A strong answer satisfies the stated need with the least fragile configuration and preserves the platform’s security and governance model. These are study heuristics, not additional official exam rules.
Extra concept: Treat configuration as a system rather than a list of settings. A field may participate in a formula, validation rule, flow, report, permission set, Lightning page, and deployment package at once. Before changing it, identify those dependencies, decide which are intentional, and test the full user journey. This dependency view explains why a locally correct change can still fail after deployment or for a different user. Use Setup dependency tools where available, source comparison, and focused regression checks; no single dependency view is guaranteed to reveal every runtime relationship.
Verification exercise: Turn the lesson scenario into a small test plan before calling the design complete. Record the starting data, the user permissions, the expected outcome, and the evidence that would confirm it. Test one ordinary path, one boundary condition, and one invalid or unauthorized path. Compare the result with the business requirement, then repeat after deployment in the target environment. This catches differences caused by data, activation, page assignment, sharing, or dependencies. Save the test cases with the release notes so another administrator can reproduce the result.
Key takeaways
- Given a scenario, identify the boundaries of declarative customization and the use cases for programmatic customization
- Choose the platform feature that fits the requirement, data, access, and operating context.
- Test realistic users, exceptions, dependencies, and lifecycle effects before release.
- Official references: https://help.salesforce.com/s/articleView?id=005298964&language;=en_US&type;=1 https://trailhead.salesforce.com/content/learn/modules/platform-app-builder-pt1/platform-app-builder-fundamentals
