Salesforce Plat-Arch-202 Practice Exam Questions & Answers

The correct selection is C, D. Reliable tests should be self-contained and independent of live external systems. Mock endpoints or Salesforce callout mocks provide deterministic responses for integration logic, while CSV static resources and Test.loadData() provide reusable test records without depending on middleware or external availability. 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 (C. Host a mock endpoint to produce sample information from an endpoint.; D. Load a CSV as a static resource and reference it in a test class.). 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, D, E. Salesforce DX supports local, source-controlled projects; installation of centrally managed application metadata or package versions; and creation of temporary scratch orgs for isolated development and CI. It does not provide a universal native rollback button or use Execute Anonymous as a metadata deployment mechanism. 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 options (A. Can store code on a local machine, or a version control system.; D. Can install application metadata from a central repository.; E. Can create scratch orgs.). 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. The failure results from managed-package Apex being non-certified during testing. The subscriber org must explicitly allow metadata deployment from a non-certified Apex package version; this is an org-level security preference, not a custom metadata setting and not a reason to replace the solution with Tooling API. 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 (A. Apex Settings to allow the access to metadata is not switched on.). 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, D, E. Package development provides modular application boundaries, explicit package dependencies, immutable/versioned release artifacts, and a more agile release process. Those benefits improve change management and independent deployment but do not inherently dictate sandbox counts or impose organizational separation between developers and testers. 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 rejected alternatives either describe a specific tool rather than a lifecycle capability or omit the source-control and traceability needed for repeatable enterprise delivery. For this scenario, the decisive point is therefore the platform behavior represented by the selected options (C. Modular development process with specification of dependencies among packages.; D. Versioning to help with change management.; E. Making the release cycle more efficient and agile.). 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. REST sObject Tree is designed for nested parent-child creation, while REST Composite can chain subrequests and reference IDs returned by earlier subrequests. Both reduce round trips and can create related records in one request structure; Bulk API and Streaming API serve different workload patterns. 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. REST API SObject Tree Request; C. REST API Composite Request). 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.