Free Practice Questions for Salesforce Plat-Arch-202 Exam

The correct selection is A, B. Salesforce source-oriented retrieve commands require execution inside a Salesforce DX project identified by sfdx-project.json. The error occurs when the developer either never created the project or runs the command from outside the project directory; the terminal application itself is irrelevant. 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 (A. The developer created the project, but ran the Command outside of the project directory.; B. The developer hadn ' t run the sfdx force:project:create command.). 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 B. Kanban provides objective flow metrics such as lead time and throughput and makes work visible across the workflow. Those measures let executives determine whether completed value is actually reaching users rather than relying on conflicting subjective claims about sprint output. 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 alternatives are weaker because they address a symptom rather than establishing the governance or environment decision required before implementation begins. For this scenario, the decisive point is therefore the platform behavior represented by the selected option (B. Kanban traits includes metrics, like lead time and throughput, which increases transparency.). 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, D. Direct Metadata API retrieve() and deploy() calls are primary when custom code or tooling itself must programmatically move metadata. If Salesforce CLI or the Ant Migration Tool is already being used, those clients wrap the API and the developer normally invokes the tool instead of writing direct API calls. 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 options (A. Team development of an application in a Developer Edition organization. After completing development and testing, the application is Distributed via Lightning Platform AppExchange.; D. Development of a custom application in a sandbox organization. After completing development and testing, the application is then deployed Into a production organization using Metadata 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. Reports and dashboards edited directly in production are being overwritten by older source-controlled versions during releases. Regularly retrieving that metadata and merging it into development branches keeps the repository current and prevents subsequent deployments from rolling back business-authored changes. 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 (C. Ensure report metadata is exported daily and that it is merged into the developer branches before the next release.). 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. Scrum depends on transparency and openness about progress, timing, plans, and obstacles. Honest status visibility enables inspection and adaptation; arbitrary daily scope changes or rigid role separation are not Scrum principles. 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 (A. Create transparency by being honest and clear about timing, planning, and obstacles). 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.