Salesforce Plat-Arch-204 Exam Questions

For HR synchronization requiring high reliability and a multi-day data retention window, Change Data Capture (CDC) is the optimal architectural choice.12

CDC is an event-driven integration framework that automatically publ3ishes change events for Sale4sforce records (Create, Update, Delete, and Undelete). A critical feature of CDC for failure recovery is its 72-hour (3-day) retention window. If the external HR system or the replication middleware experience downtime, the change events remain stored in the Salesforce event bus for up to three days. Once the HR system is back online, the subscriber can use the Replay ID of the last successfully processed event to retrieve all missed notifications from the bus, ensuring zero data loss during the outage.

In contrast, Outbound Messaging (Option B) only provides a 24-hour retry window. If the target system is unavailable for more than one day, the notifications are dropped, making it unsuitable for a 3-day requirement. Callouts (Option C) are typically synchronous and do not have native, platform-managed storage or retry mechanisms for failed requests; once a callout fails, the data is lost unless a custom retry architecture is built. CDC's native, durable event bus provides the necessary scalability and resilience for critical HR data synchronization without requiring complex custom code for error handling and data recovery.

To satisfy the requirement of encrypting standard fields while maintaining their functionality within record-triggered flows, Shield Platform Encryption is the recommended architectural solution.1

Shield Platform Encryption is a modern security layer that allows for encryption at rest while 2preserving critical platform features. Unlike Classic Encryption (Option B)---which is limited to a specific 'Encrypted Text' custom field type and often breaks platform features like search and automation---Shield is designed to work with standard fields such as Name, Email, and Phone.

Key architectural considerations for Shield include:

Compatibility with Automation: Shield fields can be used in Flows, Apex triggers, and validation rules. This allows NTO to implement the required record-triggered business logic without needing to decrypt the data manually in code.

Search and Filtering: By using Deterministic Encryption, Shield allows users to filter and search for records based on encrypted fields, which is often a requirement for 'widely-used' standard fields.

Compliance and Governance: Shield provides advanced key management (Bring Your Own Key - BYOK) and auditing, ensuring that NTO meets corporate security guidelines while data is being processed by the platform.

Data Masking (Option C) is primarily used for sandboxes to obfuscate PII during testing and is not a production encryption-at-rest solution. By recommending Shield, the architect provides a transparent security model that protects sensitive data without sacrificing the declarative power of Flow Builder.

The evaluation of an integration landscape is a process of rationalization. The goal is to identify which legacy systems Salesforce will replace (System Retirement) and which systems it must coexist with (Integration).

In this scenario, Salesforce is being implemented for Case Management. Salesforce Service Cloud is the industry leader for this specific function. Therefore, the legacy Case Management System should be retired. Any architecture that suggests 'integrating' Salesforce with the legacy Case Management system (Options A and B) is creating a redundant and complex 'dual-master' scenario that increases technical debt.

To provide a successful support experience, Salesforce needs to be the central 'Engagement Layer,' which requires integration with the remaining ecosystem:

Email Management System: To support 'Email-to-Case' and ensure all customer communications are captured within the Salesforce Case record.

Order Management System (OMS): Support agents often need to verify purchase history or shipping status to resolve a case. A 'Data Virtualization' or 'Request-Reply' integration with the OMS is vital.

Data Warehouse: For long-term historical reporting and cross-functional analytics, Salesforce must push case data to the enterprise Data Warehouse.

By evaluating the integration with the Data Warehouse, Order Management, and Email Management systems, the architect ensures that Salesforce is enriched with the context it needs to resolve cases while simultaneously retiring the redundant legacy support system.

A synchronous requirement in Salesforce implies a Request-Reply pattern where the user waits for a response. To implement this correctly while adhering to platform constraints, the architect must initiate the callout from the User Interface (UI) layer.3

Option C is the correct architectural choice. By using a Lightning component and a button (or a Quick Act4ion), the callout is initiated directly from the user's session. The component calls an Apex controller, which performs the synchronous REST callout to the OMS. This allows the user to receive immediate feedback---such as a 'Success' message or an 'Error' notification from the OMS---directly on the Opportunity page.

Option A is incorrect because Apex Triggers are prohibited from making synchronous callouts. If a trigger initiates a callout, it must be asynchronous (using @future or Queueable Apex), which violates the business requirement for synchronicity. Making a synchronous call from a trigger would block the database transaction and could lead to 'Uncommitted Work Pending' errors or system timeouts. Option B (Batch Apex) is inherently asynchronous and delayed; an hourly job would not provide the real-time, synchronous feedback required during the 'Closed/Won' transition. Therefore, moving the integration logic to a UI-driven button is the only way to satisfy the synchronous requirement while staying within Salesforce's execution and transaction limits.

When an integration initiated from the client-side (the browser) fails, the architect must first look at the browser's security policies. In Salesforce, Lightning Web Components are subject to the Lightning Component framework's Content Security Policy (CSP).

CSP is a security layer that prevents cross-site scripting (XSS) and other code injection attacks by restricting which domains the browser is allowed to communicate with. If an LWC attempts to make a fetch() call to an external REST endpoint, the browser will block the request unless that specific domain is whitelisted in CSP Trusted Sites.

Option B (Remote Site Settings) is a common distractor; these settings are strictly for server-side Apex callouts and have no effect on client-side JavaScript requests. Option A (CORS) is also a browser security mechanism, but it must be configured on the external server to allow Salesforce to access its resources. While CORS is necessary, the first thing to validate within the Salesforce environment for a failing LWC callout is the CSP Trusted Site entry. Without this whitelisting, the request will be terminated by the browser before it even leaves the client, regardless of how the external server is configured.