Section 6 · App Deployment · 13% of exam
6.1 Plan the Application Lifecycle and Sandbox Strategy
Exam objective
Given business requirements, recommend an application lifecycle solution, including appropriate sandbox types.
Application lifecycle management moves configuration and code from an isolated development space through validation and release into production, then monitors and maintains it. A disciplined lifecycle separates building from live business use, stores source in version control when the development model supports it, and defines how work is reviewed, tested, approved, and deployed. Even declarative changes benefit from a repeatable process: identify dependencies, develop safely, validate with realistic data, document the release, and prepare a rollback or recovery plan. Salesforce sandbox types trade off data freshness, storage, and refresh frequency. A Developer sandbox supports isolated development and testing with configuration but limited data storage. Developer Pro offers more storage for larger test data needs. Partial Copy includes a template-selected subset of production data and metadata for realistic testing. Full sandbox copies production data and metadata and is suited to comprehensive testing such as performance or staging, subject to availability and refresh constraints. Confirm current limits and refresh intervals in Salesforce Help before selecting.
Choose the smallest environment that supports the required validation. A Developer sandbox may be sufficient for a focused flow change; integrated testing across complex data relationships may need Partial Copy or a carefully prepared test dataset. Full-copy data creates privacy and storage responsibilities. Mask sensitive information where required and restrict access. A sandbox refresh overwrites its contents, so preserve work and coordinate refresh timing. A lifecycle plan should include dependency discovery, merge and conflict handling, test ownership, acceptance criteria, change windows, communication, post-deployment checks, and data migration where needed. Sandboxes can become stale or diverge from production. Establish a refresh cadence and avoid parallel teams unknowingly overwriting shared metadata. Use change sets, packages, or a source-driven deployment method according to the org model and release needs.
Applied scenario: A team is changing case routing and a related screen flow. Use an isolated Developer sandbox for initial configuration. If the change must be tested with realistic account and case relationships or alongside other teams’ work, use an integration environment or a Partial Copy sandbox with a prepared data template. Validate permissions, test cases, and deployment dependencies before release. If a Full sandbox is selected for user acceptance testing, mask sensitive production data and make refresh timing explicit so testers do not lose work.
Design and risk review: Sandbox names do not guarantee a particular data set or test quality; check what the selected type actually copies. A Full sandbox is not automatically the best choice for every team because refresh frequency, storage, and privacy matter. A developer org can still contain valuable unreleased work, so refreshes must be coordinated. Also distinguish environment strategy from deployment mechanism: a sandbox is where work happens, while change sets, packages, or source tools move it. Salesforce Certified Platform App Builder | SU ·26 guide alignment 25 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 business requirements, recommend an application lifecycle solution, including appropriate sandbox types
- 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://help.salesforce.com/s/articleView?id=sf.deploy_sandboxes.htm&type;=5 https://trailhead.salesforce.com/content/learn/modules/app_deployment
