Salesforce Plat-Arch-204 Practice Exam Questions & Answers

Standard synchronous Apex callouts have a timeout limit, and more importantly, Salesforce limits the number of long-running requests (those lasting longer than 5 seconds) that can execute concurrently. If a payment gateway consistently takes 30 seconds, a few simultaneous users could easily exhaust the org's concurrent request limit, causing the entire system to stop responding.

The Continuation pattern (Option C) is designed specifically for this 'long-wait' scenario. It allows the Apex request to be suspended while waiting for the external service to respond, freeing up the Salesforce worker thread to handle other users. Once the gateway responds, the suspended process resumes and returns the result to the student's browser. This provides the 'real-time' experience required for the student to retry immediately without the risk of bringing down the entire community due to thread exhaustion.

In a standard API-led connectivity model, the First Tier (Experience APIs) is responsible for tailoring data for specific systems of engagement.

The Experience APIs take the core data from the lower tiers and transform it into the specific return formats (e.g., JSON for mobile, XML for legacy web) and security protocols (e.g., OAuth for Salesforce, API Keys for web) required by each consumer. Option B correctly identifies that these transformations and security enforcements should happen at this outer layer. While an API Gateway (Option A) can provide generic security and rate limiting, it is the Experience API layer that provides the functional transformation and specific protocol requirements defined by the business needs of the engagement systems.

An Integration Architect's primary responsibility when evaluating a landscape for a new Salesforce implementation is to identify the system of record for each business process and determine which legacy systems will be replaced by Salesforce. In this scenario, the customer is implementing Salesforce specifically to support case management.

According to the provided landscape diagram, the Case Management System currently exists as a standalone entity. Since Salesforce Service Cloud provides native, best-in-class case management capabilities, this legacy system is the primary candidate for retirement. Retiring the legacy Case Management system avoids data fragmentation and ensures that Salesforce serves as the single source of truth for support interactions.

However, for Salesforce to function effectively as a new case management hub, it must integrate with the remaining surrounding systems:

Email Management System: This system likely handles inbound customer communications. An architect must evaluate integrating this with Salesforce (via Email-to-Case or a specialized connector) so that incoming emails automatically generate or update cases.

Order Management System (OMS): Support agents often need to view order history or status to resolve customer inquiries. Integrating Salesforce with the OMS allows for a 360-degree view, enabling agents to see relevant order data directly within the Salesforce case console.

Data Warehouse: For long-term reporting, trend analysis, and a unified customer profile, case data from Salesforce needs to be pushed to the Data Warehouse. This ensures that the Analytics and Business Intelligence Tool downstream can report on support metrics alongside other enterprise data.

Therefore, the architect should evaluate integrations with the Data Warehouse, Order Management, and Email Management System. Option B and C are incorrect because they suggest integrating with the 'Case Management System,' which is the very system being superseded by Salesforce's native capabilities. By focusing on the integration of these three supporting systems, the architect ensures a seamless transition where Salesforce is fully enriched with the necessary external data to drive support excellence.

In a robust event-driven architecture, 'durability' is the ability of a system to retain events so that a subscriber can retrieve them even after being offline. For an architect needing to minimize data loss over 'every couple of days,' the selection must focus on event types that support a high retention window.

Salesforce provides two modern event types specifically designed for high-scale, durable messaging:

Change Data Capture (CDC): This automatically broadcasts changes to Salesforce records (Create, Update, Delete, Undelete). CDC events are highly durable and are retained in the event bus for 72 hours (3 days).

High-Volume Platform Events: These are custom events defined by the architect. Like CDC, High-Volume Platform Events also provide a 72-hour retention window.

Earlier versions of the Streaming API, such as PushTopic Events and Generic Events (Option C and parts of A), typically offered a 24-hour retention window, which would not satisfy the requirement of a client re-connecting 'every couple of days' (potentially 48-72 hours later).

By utilizing CDC and High-Volume Platform Events, the architect can leverage the Replay ID. When the client re-connects, it can send the Replay ID of the last event it successfully processed. Salesforce then 'replays' all events that occurred during the client's downtime from that specific point, up to the 72-hour limit. This mechanism ensures zero data loss for planned or unplanned outages lasting up to three days, making it the most resilient choice for the specified requirements.

When corporate guidelines mandate a firewall-protected entry point for cloud traffic, the middleware architecture must include a component capable of residing in a Demilitarized Zone (DMZ) or perimeter network. The architect must evaluate the solution's API Gateway capabilities.

A secure API Gateway acts as the intermediary that terminates external (cloud) TLS connections and inspects incoming traffic before proxying it to internal systems. It allows the security team to implement:

IP Whitelisting: Ensuring only Salesforce's IP ranges can access the gateway.

Mutual Authentication: Using certificates to verify that the request is genuinely coming from the Salesforce org.

Rate Limiting: Protecting on-premise resources from being overwhelmed by cloud requests.

Option A (OAuth) is an authorization framework and does not satisfy the network-level firewall requirement on its own. Option B (ODBC) is an internal database protocol that should generally never be exposed to a cloud-facing firewall due to security risks. By prioritizing a solution with a hardened API Gateway, the architect ensures that NTO meets its new security mandates while providing a scalable and secure bridge for Salesforce to access back-office services.

For organizations using both Salesforce Service Cloud and B2C Commerce (formerly Demandware), Salesforce provides a specialized, pre-built integrat25ion known as the Salesforce B2C Commerce to Service Cloud Connector. This connector is part of the Salesforce B2C Solution Architecture and is the recommended choice because it offers 'out-of-the-box' cross-cloud functionality.

The connector enables several critical business processes for service agents:

Unified Customer Profile: Synchronizes customer data between the two platforms, ensuring agents have the most current contact information.

Order History Visibility: Allows agents to view real-time order data and status from the Commerce system directly within the Service Console.

Service Actions: Enables agents to perform commerce-related tasks, such as 'Order on Behalf Of,' without leaving the Salesforce interface.

While an architect could build a custom integration using the Commerce REST API (Option A) or MuleSoft (Option C), these approaches require significant development, testing, and long-term maintenance effort. The B2C Connector reduces time-to-market and leverages Salesforce's own engineering to handle complex synchronization logic and API versioning. Recommending the standard connector aligns with the architectural principle of 'clicks before code' and ensures that the integration remains supported by Salesforce as both platforms evolve.

In the world of Salesforce SOAP APIs, the choice of WSDL depends on the nature of the application being built. When an architect needs to build an integration that is org-agnostic---meaning it can work across multiple different Salesforce organizations with varying custom objects and fields---the Partner WSDL is the correct choice.

The Partner WSDL is loosely-typed. It does not contain information about an org's specific custom metadata; instead, it uses a generic sObject structure. This allows a single client application (like a third-party integration tool or a mobile app) to connect to any Salesforce org and dynamically discover its schema at runtime. Because it is not tied to a specific org's metadata, it does not need to be regenerated every time a custom field is added to one of the target orgs.

In contrast, Option A (Enterprise WSDL) is strongly-typed. It is generated specifically for one org and contains hard-coded references to that org's custom objects and fields. While this provides better compile-time safety for internal, single-org integrations, it is unsuitable for an application intended for 'more than one Salesforce org' because the WSDL would be invalid for any org that doesn't have the exact same metadata. Option C is a general term; the actual choices provided by Salesforce for integration are the Partner or Enterprise WSDLs. Therefore, for maximum flexibility and reusability across a multi-org landscape, the Partner WSDL is the industry standard.