Salesforce Plat-Arch-202 - Platform Development Lifecycle and Deployment Architect

The correct selection is C. A managed package provides versioned distribution and controlled upgrades across independent trading-partner orgs while allowing the publisher to maintain the product. Change sets require related orgs, unmanaged packages are effectively one-time distributions, and raw metadata ZIP deployment would make every partner a custom deployment target. From a release perspective, approved functionality must be isolated from unfinished work and promoted through a predictable, auditable path. Release calendars, validation, stakeholder approval, rollback planning, and branch discipline reduce the risk that a technically correct change becomes an operational failure during production promotion. The rejected alternatives weaken release control by mixing development states, skipping required validation, or treating production promotion as an ad hoc administrative task. For this scenario, the decisive point is therefore the platform behavior represented by the selected option (C. Managed package). Applying that rule consistently keeps the implementation aligned with Salesforce-supported lifecycle practices and makes the resulting change easier to review, validate, and operate across environments.

Study Guide reference: Releasing — release management; branching and hotfixes; production readiness; rollback strategy; seasonal releases; approvals.

The correct selection is A. A production defect should be fixed in a dedicated hotfix environment based on the production baseline, not in UAT that may already contain future-release work. After verification, the same correction must be deployed to production and synchronized back into all relevant downstream branches and environments. From an operating perspective, production stability depends on disciplined incident handling, environment synchronization, backup/recovery, observability, and control of configuration drift. Emergency actions can be faster than normal releases, but they still require traceability and must be reconciled back into the managed development baseline. The rejected choices do not provide a sustainable operating control because they fail to preserve traceability and synchronization after the immediate incident or environment change. For this scenario, the decisive point is therefore the platform behavior represented by the selected option (A. UC should spin up a new sandbox to use as a hot fix environment. Once the bug is corrected, the change should be applied to production and downstream environments.). Applying that rule consistently keeps the implementation aligned with Salesforce-supported lifecycle practices and makes the resulting change easier to review, validate, and operate across environments.

Study Guide reference: Operating — production governance; environment drift; incident response; backup/recovery; post-refresh controls; hotfix synchronization.

The correct selection is A. A deployment train should not unintentionally span incompatible Salesforce release versions. During a preview window, sandboxes used together for promotion should be deliberately aligned so the same release artifact is tested against a consistent platform version before production deployment. From a release perspective, approved functionality must be isolated from unfinished work and promoted through a predictable, auditable path. Release calendars, validation, stakeholder approval, rollback planning, and branch discipline reduce the risk that a technically correct change becomes an operational failure during production promotion. The rejected alternatives weaken release control by mixing development states, skipping required validation, or treating production promotion as an ad hoc administrative task. For this scenario, the decisive point is therefore the platform behavior represented by the selected option (A. Refresh all non-preview sandboxes during the release preview window.). Applying that rule consistently keeps the implementation aligned with Salesforce-supported lifecycle practices and makes the resulting change easier to review, validate, and operate across environments.

Study Guide reference: Releasing — release management; branching and hotfixes; production readiness; rollback strategy; seasonal releases; approvals.

The correct selection is B. UC must use the Sandbox Preview Guide and preview cutoff information to deliberately maintain one production-aligned path for the imminent release and another environment for regression against the upcoming Salesforce release. Refresh behavior depends on instance timing and cannot safely be assumed. From a release perspective, approved functionality must be isolated from unfinished work and promoted through a predictable, auditable path. Release calendars, validation, stakeholder approval, rollback planning, and branch discipline reduce the risk that a technically correct change becomes an operational failure during production promotion. The remaining choices either bypass release governance, delay an urgent correction unnecessarily, or fail to isolate approved production content from work that is still in progress. For this scenario, the decisive point is therefore the platform behavior represented by the selected option (B. Use the Sandbox Preview Guide to check if there is any necessary action needed. UC might have to prepare, refresh, and redeploy to UAT.). Applying that rule consistently keeps the implementation aligned with Salesforce-supported lifecycle practices and makes the resulting change easier to review, validate, and operate across environments.

Study Guide reference: Releasing — release management; branching and hotfixes; production readiness; rollback strategy; seasonal releases; approvals.

The correct selection is B. After a sandbox refresh, production-oriented external identifiers can point to invalid records in the UAT integration landscape. A post-refresh process should transform those identifiers to a known UAT-safe mapping so test orchestration remains internally consistent and cannot accidentally target production systems. From an operating perspective, production stability depends on disciplined incident handling, environment synchronization, backup/recovery, observability, and control of configuration drift. Emergency actions can be faster than normal releases, but they still require traceability and must be reconciled back into the managed development baseline. The other options are weaker because they either expose production to unnecessary risk or do not reconcile the operational change back into the governed lifecycle. For this scenario, the decisive point is therefore the platform behavior represented by the selected option (B. In the post refresh plan, modify external ids to a known valid set of values for UAT.). Applying that rule consistently keeps the implementation aligned with Salesforce-supported lifecycle practices and makes the resulting change easier to review, validate, and operate across environments.

Study Guide reference: Operating — production governance; environment drift; incident response; backup/recovery; post-refresh controls; hotfix synchronization.