Pass the Salesforce Developer Plat-Arch-202 Questions and answers with ExamsMirror

The correct selection is B, C. Unlocked-package adoption should begin by checking metadata packaging support and testing package versions in non-production environments before production installation. The Metadata Coverage Report identifies what can be packaged, while source control remains essential and a single monolithic package defeats modular package-development principles. 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 rejected choices either rely on manual review alone, use the wrong development abstraction, or introduce custom complexity where Salesforce already provides a source-driven engineering mechanism. For this scenario, the decisive point is therefore the platform behavior represented by the selected options (B. Consult the metadata coverage report to identify features supported by packages.; C. Test developed packages in test environments before installing to 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: Building — Salesforce DX; package development; coding standards; static analysis; source control; secure development.

The correct selection is A, C, D. ALM reduces production defects by enforcing controlled development and testing, creates measurable delivery processes, and enables a predictable release cadence. User training may be part of change management, but it is not required after every release, and no lifecycle can guarantee that existing functionality never fails. From an ALM perspective, the controlling principles are a clear source of truth, repeatable change tracking, controlled promotion, testable release artifacts, and traceability from requirement through production. Mature teams separate the lifecycle from any single tool so the process remains consistent even when the deployment mechanism changes. The alternatives fail because they either create manual tracking or treat one delivery technology as the lifecycle, which weakens auditability and makes releases harder to reproduce. For this scenario, the decisive point is therefore the platform behavior represented by the selected options (A. Avoiding defects from being deployed to production.; C. Defining metrics for application development project success.; D. Releasing new features on a consistent schedule.). 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: Application Lifecycle Management — ALM stages; source control; change tracking; package/org development models; CI/CD; release traceability.

The correct selection is A, C. Aura accessibility checks can be invoked in JavaScript tests and WebDriver-based browser tests. Those environments can inspect rendered DOM behavior for common accessibility violations, making accessibility a repeatable part of automated component quality rather than a purely manual review. 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 other options are weaker because they sacrifice isolation, realism, or repeatability and therefore make failures harder to reproduce and diagnose across environments. For this scenario, the decisive point is therefore the platform behavior represented by the selected options (A. JSTEST; C. WebDriver Test). 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 D. A governed citizen-development program can shift low-complexity backlog work to trained business technologists using declarative tools, freeing scarce expert developers for complex engineering. Guardrails, standards, testing, and controlled release processes are still required to prevent low-code technical debt. 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 option (D. UC should start a citizen development program.). 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. 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.