Free Salesforce Plat-Arch-202 Practice Exam with Questions & Answers | Set: 3

The correct selection is C. Tooling API is intended for fine-grained programmatic access to development and metadata-related resources and exposes many of them as queryable objects. That makes it better suited than package-oriented Metadata API when a Java application needs targeted SOQL-driven metadata operations. From a deployment perspective, the same release should be reproducible across environments, with dependencies, metadata/data differences, API behavior, and target-org constraints identified before production. Automation is valuable because it turns deployment knowledge into a controlled process rather than relying on memory or manual reconstruction. The rejected alternatives do not meet the deployment requirement because they introduce drift, ignore target-org compatibility, or substitute a convenience tool for a reproducible release artifact. For this scenario, the decisive point is therefore the platform behavior represented by the selected option (C. Tooling API). 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: Deploying — Metadata API and Tooling API; deployment validation; package/change-set deployment; data migration; dependency management.

The correct selection is C. Automated browser tests depend on the rendered Document Object Model. Salesforce can change internal Lightning markup between seasonal releases even when the business behavior is unchanged, so brittle selectors and DOM assumptions can require test maintenance. From a testing perspective, the goal is deterministic evidence that the solution behaves correctly under the conditions that matter. Tests should isolate external dependencies, use controlled data, exercise positive and negative paths, and reproduce realistic volume or user behavior where required without making production the first place defects are discovered. The alternatives do not provide equivalent evidence: they either validate only a narrow implementation detail or depend on conditions outside the test ' s control. For this scenario, the decisive point is therefore the platform behavior represented by the selected option (C. DOM changes). 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: Testing — Apex testing; test-data isolation; mocks; regression testing; performance/load testing; sandbox test strategy.

The correct selection is B, C. Secure pull-request review and automated static security analysis create complementary controls. Human reviewers assess architecture and context, while scanners detect repeatable vulnerability patterns and can block unsafe changes in CI before they reach downstream environments. From a build perspective, the implementation should be source-driven, reviewable, automatable, and modular. Engineering controls such as version control, package boundaries, static analysis, coding standards, and isolated development environments reduce defects early and make changes easier to understand, test, and promote. The remaining options are weaker because they address symptoms after code is written instead of improving the build process through automation, modularity, and explicit development standards. For this scenario, the decisive point is therefore the platform behavior represented by the selected options (B. Implement a pull request and secure code review.; C. Integrate a static code security analysis tool in the CI/CD process.). 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: Building — Salesforce DX; package development; coding standards; static analysis; source control; secure development.

The correct selection is A. Salesforce Scrum guidance associates courage with being transparent about progress and speaking up when help is needed. Failing to update work-in-progress status hides delivery reality and impediments, undermining empirical planning and team collaboration. From a planning perspective, the architect must reduce uncertainty before execution by defining ownership, governance, environment purpose, prioritization, and measurable acceptance criteria. Decisions should be repeatable and visible across teams so delivery capacity, risk, and stakeholder expectations remain aligned throughout the lifecycle. The other choices either shift accountability to the wrong role, create unnecessary operational work, or ignore the stated timing, governance, and risk constraints. For this scenario, the decisive point is therefore the platform behavior represented by the selected option (A. Courage, because the teams should be transparent about progress and speak up when they need help.). 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: Planning — governance; agile planning; environment strategy; backlog prioritization; sandbox strategy; stakeholder alignment.

The correct selection is D. A release branch isolates the completed sprint from new sprint development. Final UAT fixes can be made against the release candidate while future features continue on the development branch, after which the release fixes are merged back so both production and ongoing development remain synchronized. 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 (D. Using Git, create a release branch from the develop branch. All fixes must be made in the release branch. After deployment, merge release with develop.). 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, C. High code coverage alone does not guarantee useful tests. Test scripts should drive meaningful Apex scenarios and detailed acceptance criteria should define observable behavior, ensuring automated tests validate the actual requirement rather than merely execute additional lines of code. From a testing perspective, the goal is deterministic evidence that the solution behaves correctly under the conditions that matter. Tests should isolate external dependencies, use controlled data, exercise positive and negative paths, and reproduce realistic volume or user behavior where required without making production the first place defects are discovered. The rejected choices either test the wrong layer, introduce live-system dependencies, or detect problems too late to provide the deterministic early feedback expected from a mature test strategy. For this scenario, the decisive point is therefore the platform behavior represented by the selected options (A. The test script should be used to define the test classes.; C. The acceptance criteria should have more details.). 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: Testing — Apex testing; test-data isolation; mocks; regression testing; performance/load testing; sandbox test strategy.

The correct selection is B. A Metadata API-formatted release artifact should be validated and deployed consistently using the Metadata API deployment mechanism. Mixing source-format and mdapi commands introduces needless conversion risk, and because quick deploy is excluded, the normal deployment must run after successful validation. From a deployment perspective, the same release should be reproducible across environments, with dependencies, metadata/data differences, API behavior, and target-org constraints identified before production. Automation is valuable because it turns deployment knowledge into a controlled process rather than relying on memory or manual reconstruction. The alternatives are less reliable because they do not provide the same controlled handling of metadata, data relationships, validation, or environment-specific dependencies. For this scenario, the decisive point is therefore the platform behavior represented by the selected option (B. Authorize to the Full sandbox org; Validate with sfdx:mdapi:deploy On successful validation, deploy with sfdx:mdapi:deploy). 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: Deploying — Metadata API and Tooling API; deployment validation; package/change-set deployment; data migration; dependency management.

The correct selection is A, B. Because regulations prohibit production data in non-production, UC can either mask a production-derived Full sandbox or generate synthetic data with production-like distribution and volume. Both approaches support realistic performance behavior without exposing regulated values. From a testing perspective, the goal is deterministic evidence that the solution behaves correctly under the conditions that matter. Tests should isolate external dependencies, use controlled data, exercise positive and negative paths, and reproduce realistic volume or user behavior where required without making production the first place defects are discovered. The rejected choices either test the wrong layer, introduce live-system dependencies, or detect problems too late to provide the deterministic early feedback expected from a mature test strategy. For this scenario, the decisive point is therefore the platform behavior represented by the selected options (A. Perform data masking on full sandbox after a refresh.; B. Generate mock data that mimics production data shape and volume.). 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: Testing — Apex testing; test-data isolation; mocks; regression testing; performance/load testing; sandbox test strategy.

The correct selection is A. A shared release calendar aligns internal major and minor releases with Salesforce seasonal upgrades, blackout periods, testing windows, and business readiness. The calendar becomes the common coordination mechanism across teams instead of relying on ad hoc metadata spreadsheets or routing every operational decision through the COE. 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. Create a release calendar, train and align all the teams.). 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.