Salesforce Updated Plat-Arch-202 Exam Questions and Answers by sage

The correct selection is B. Second-generation managed packages that share a namespace can selectively expose public Apex across package boundaries through @NamespaceAccessible. This preserves modular package ownership while creating an explicit contract for only the methods that another same-namespace package should consume. 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 option (B. Create two second generation managed packages with the same namespace and set the methods that should be shared with the @namespaceAccessible Annotation.). 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 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. 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. 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.