Salesforce Plat-Arch-202 Practice Exam Questions & Answers

The correct selection is D. The requirement is end-to-end automated promotion across sandboxes and production, so a CI/CD pipeline is the correct architecture. A pipeline can integrate source control, tests, approvals, credentials, deployment logging, and repeatable production promotion after UAT acceptance. 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 other choices either rely on manual reconstruction, use a deployment mechanism designed for a different scope, or fail to preserve dependencies and repeatability across target environments. For this scenario, the decisive point is therefore the platform behavior represented by the selected option (D. Recommend using the Continues integration and the Continues deployment tool and build the pipeline to deploy to sandboxes and production.). 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 B. A scheduled Batch Apex cleanup job can delete the day's roughly 1 GB of test records in scalable chunks. A Partial Copy sandbox cannot be refreshed nightly under the normal refresh interval, and manual deletion or nightly sandbox recreation would be inefficient and operationally fragile. 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 option (B. Execute a batch job that deletes all records created on the day.). 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. The workflow and trigger are a business-process enhancement rather than an emergency fix or architectural overhaul, so they fit a minor release. Because the opportunity renewal process changes for users, the release should include communication, readiness, training, and change-management activities. 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. Plan this as a minor release with training and change management.). 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 C, D. Scrum improves visibility through its value of openness, while Kanban explicitly visualizes work items and workflow states. Both directly address team-work status transparency; runtime DevOps monitoring is useful but does not substitute for visible development work management in this scenario. 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 rejected options do not resolve the planning problem at its source; they either add process overhead or make assumptions that leave ownership and delivery risk unclear. For this scenario, the decisive point is therefore the platform behavior represented by the selected options (C. Scrum, because openness is one of the five core Scrum values.; D. Kanban, because one of its basic elements is to make everything visible, creating consistent transparency of work items.). 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 A. Checkmarx findings must be reviewed individually. Real vulnerabilities should be remediated; legitimate false positives should be documented with a technical justification and included in the AppExchange security-review submission rather than ignored or mechanically changed simply to produce a zero-warning report. 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 alternatives do not create the same repeatable engineering control: they either postpone defect detection, couple teams unnecessarily, or bypass the package/source model that should govern the change. For this scenario, the decisive point is therefore the platform behavior represented by the selected option (A. Review the Checkmarx errors. If there is no need to fix, mark them as false positive and attach explanation, then submit.). 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 C, D. Technical reference-data migrations are constrained by relationship shape. Circular references cannot be represented cleanly as one rooted hierarchy, and nested object trees have a finite supported depth, so complex reference structures often need staged loads and follow-up relationship updates. 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 options (C. Circular relationships; D. Depth of nested relationships). 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, C. A Full sandbox used for production defect analysis should remain aligned with the production release state. Refreshing after production deployments and rehearsing every production-bound deployment in that sandbox make it far more likely that a production defect can be reproduced and diagnosed under equivalent metadata conditions. 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 options (A. Refresh the full sandbox after every deployment in production.; C. Before any deployment in production, the same process must be performed in this sandbox.). 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.