Plat-Arch-202 Exam Dumps and Practice Questions

The correct selection is A, B, E. A serious production bug in a regulated environment requires data-impact analysis, a dedicated hotfix branch, and explicit stakeholder approval. Waiting for the normal release or editing Apex directly in production would bypass the controlled emergency-change process and create unacceptable traceability risk. 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 other options do not create a safe production path because they ignore timing, approval, rollback, or branch synchronization requirements. For this scenario, the decisive point is therefore the platform behavior represented by the selected options (A. Investigate potential data impacts.; B. Fix the bug in a hotfix branch.; E. Seek stakeholder approval for the hotfix.). 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, D. HTTP callouts in Apex tests require mocks, and mocks more broadly isolate a unit from dependencies whose state or behavior must be controlled. They make tests deterministic and let developers simulate success and failure conditions without contacting external systems or bypassing normal Batch Apex testing patterns. 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 options (A. Mock is needed whenever the code makes an HTTP callout.; D. Using a Mock allows the test class to bypass the dependencies of other objects, methods, state, or behaviors. Therefore, the developer has total control of his own code.). 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, B, C. Scrum tooling must support the ordered product backlog, sprint backlog, and assignment or ownership of actionable work. Those capabilities map directly to Scrum planning and execution, whereas email alerts or a generic Kanban view are supporting conveniences rather than the core Scrum controls being asked for. From a system-design perspective, the decision should minimize unnecessary coupling while preserving clear ownership, scalability, governance, and extensibility. Salesforce architecture is strongest when boundaries reflect real business and technical responsibilities instead of using organizational convenience as the primary design driver. The other options introduce tighter coupling, duplicate governance, or solve a different architectural concern and therefore do not satisfy the stated boundary and ownership requirements. For this scenario, the decisive point is therefore the platform behavior represented by the selected options (A. Product backlog prioritization; B. Sprint backlog management; C. Work (for example, user stories or tasks) assignment). 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: System Design --- org strategy; modular architecture; integration topology; data ownership; enterprise governance; scalability.

The correct selection is B. Competing stakeholder priorities should be resolved through a transparent prioritization model rather than by the architect taking ownership of business decisions. Agreed criteria such as value, risk, urgency, effort, and strategic alignment let product leadership order the backlog consistently and defensibly. 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 (B. Facilitate the design of a prioritization model with the stakeholders.). 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, E. Change sets are not designed as a fully automatable CI/CD artifact, successful deployments do not have a native rollback operation, and a change set is not a reusable package for arbitrary production orgs. They can, however, be validated and are intended for related orgs connected to the same production lineage. 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 options (A. Change Sets cannot be automated.; D. Change Sets cannot be rolled back.; E. Change Sets cannot be reused between Production Salesforce 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: Deploying --- Metadata API and Tooling API; deployment validation; package/change-set deployment; data migration; dependency management.