Plat-Arch-202 Exam Questions & Answers

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 C, D. A multi-org Customer 360 strategy should avoid uncontrolled point-to-point connectivity. A reusable package can standardize common customer-view functionality across orgs, while a hub-and-spoke pattern centralizes authoritative customer data and lets business-unit orgs integrate to that master. 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 rejected designs either centralize too much, fragment without justification, or use a mechanism that does not create the required architectural contract between systems or teams. For this scenario, the decisive point is therefore the platform behavior represented by the selected options (C. Implement a Single Package multi-org strategy by developing and deploying to all orgs a managed package which reads and consolidates customer 360-degree view from the different orgs.; D. Implement a Hub-and-Spoke multi-org strategy by consolidating customer data in a single org, which will be the master of customer data, and using integration strategies to let the LOBS orgs read and write from it.). 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 A. GitHub Flow uses short-lived feature branches around an always-deployable mainline and is suitable when teams have separate work streams and delivery dates. Each stream can be integrated through pull requests without forcing unfinished work into a common trunk prematurely. 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 remaining choices either bypass release governance, delay an urgent correction unnecessarily, or fail to isolate approved production content from work that is still in progress. For this scenario, the decisive point is therefore the platform behavior represented by the selected option (A. GitHub flow). 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. ANT Migration Tool and VS Code with Salesforce Extensions support file-based metadata deployment to multiple independent orgs. Change sets depend on deployment connections between related orgs, while Developer Console is not an enterprise distribution mechanism for a reusable global application. 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 (C. ANT Migration Tool; D. VS Code with Salesforce Extension). 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. Failure to enforce object CRUD and field-level security is a recurring AppExchange security-review problem because packaged Apex must respect subscriber authorization. Secure designs explicitly enforce user access rather than assuming UI configuration alone protects records and fields. 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 (B. CRUD/FLS (field level security)). 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.