Free PLAT-ARCH-204 Practice Test Questions and Answers (2026) Practice Questions

Salesforce CRM provides native capabilities that directly replace these three systems:

- Email Marketing: Salesforce Marketing Cloud and built-in email capabilities fully replace standalone email marketing systems

- Sales Activity: Sales Cloud core functionality includes comprehensive activity tracking, opportunity management, and sales processes

- Case Management: Service Cloud provides robust case management features including case routing, escalation, and resolution tracking

These are fundamental CRM functions that Salesforce is designed to consolidate and replace.

Option A (Order Management, Case Management, and Email Marketing):

Order Management requires specialized ERP integration and is explicitly mentioned in goals as an "Enterprise capability" to reuse, not retire.

Option B (Sales Activity, Order Management, and Case Management):

Order Management systems handle complex fulfillment processes that extend beyond CRM scope and should be integrated, not replaced.

1. Salesforce Platform Architecture Documentation, "Integration Patterns and Practices" (2023), Section 3.2 - System Consolidation Strategies

2. Salesforce Implementation Guide, "B2C Commerce Architecture" (2023), Chapter 4 - Core vs. Extended Capabilities

3. Service Cloud Implementation Guide (2023), Section 2.1 - Case Management Features

4. Sales Cloud Administrator Guide (2023), Chapter 3 - Activity Management

5. Marketing Cloud Connect Documentation (2023), Section 1.3 - Email Marketing Consolidation

Salesforce Connect is the ideal solution for this scenario. It provides real-time access to data from an external system without storing it in Salesforce, which is critical given the high volume of transactions (1 million/day). Financial transactions can be exposed as external objects in the community, providing a seamless user experience where customers can view their data as if it were native to Salesforce. This avoids data synchronization complexities, storage costs, and potential data staleness issues, making it the superior architectural choice.

B. Using an Iframe creates a disjointed user experience, is harder to style consistently, and poses security risks. It prevents tight integration with other community features.

1. Salesforce Connect Developer Guide, "Salesforce Connect": "Salesforce Connect lets your users view, search, and modify data that’s stored outside your Salesforce org... Instead of copying the data into your org, external objects let you access the data in real time via web service callouts."

2. Salesforce Help, "Notes on Salesforce Connect—All Adapters": "By using external objects, you can get the most up-to-date data from the external system in real time."

3. Salesforce Architects, "Salesforce Integration Patterns and Practices", Page 24, "Data Virtualization": "This pattern is useful when the data is... high volume... [and] real-time access is required... The Salesforce platform feature that supports this pattern is Salesforce Connect."

The requirement is for a synchronous callout when an opportunity is closed. Making a direct synchronous callout from a trigger is prohibited because a database transaction is in progress, which would cause a CalloutException. The correct pattern is to initiate the action from a user interface element, like a Lightning component. The component's controller can perform the synchronous callout to the OMS first. Upon receiving a successful response, it can then perform the DML operation to update the opportunity's stage to "Closed/Won", ensuring a synchronous user experience without violating platform constraints.

B: A trigger cannot make a direct synchronous callout. This would result in an error due to uncommitted work pending in the transaction.

C: A batch job is asynchronous and runs on a schedule (e.g., hourly). This violates the requirement for an immediate, synchronous callout when the opportunity is updated.

1. Apex Developer Guide, "Triggers," Section: "Triggers and Callouts." The documentation states, "You cannot make a callout from a trigger." It recommends processing callouts asynchronously using methods like future or queueable Apex.

2. Lightning Aura Components Developer Guide, "Calling a Server-Side Action." This guide demonstrates the pattern where a component calls an Apex controller method. This method can perform the callout and then the DML, reversing the problematic trigger sequence.

The end-to-end response time, from the user's perspective, is the total elapsed time from their initial action to the final response displayed in the UI. In the provided diagram, this entire duration is represented by the timeline from the start of call 'A' to the completion of call 'H'. Option B, "Sum of A to H," is the only choice that encompasses all the processing steps within this user-perceived timeframe. The term "Sum" is likely used imprecisely and should be interpreted as the total duration of the critical path through these sequential and parallel operations, not the arithmetic sum of each segment's duration.

A. This option only includes the initial request and final response times, completely ignoring the significant server-side processing time (B, C, D, E, F, G), which is incorrect.

C. This option arbitrarily excludes steps G and H, failing to account for the complete transaction lifecycle from the user's perspective.

1. Salesforce Architects, The Architect's Guide to Performance, "End-to-End Performance" section. This guide defines end-to-end performance as the time it takes for a user to complete a task, which corresponds to the total elapsed time from the initial request to the final UI update.

2. Salesforce Developers Blog, Measuring Network and App Performance in Lightning Experience. This article discusses breaking down performance into components (browser, network, server). The user's perceived time is the total of these components, accounting for the entire process from start to finish.

Before recommending a specific solution (e.g., an API, a third-party tool), an architect must perform a thorough discovery. This involves understanding the complete picture. "Data access prevention requirements" defines the business goal (what should happen to the user and their records). "Integration requirements" covers the technical 'how' (e.g., pattern, protocol, frequency). "System constraints" identifies the limitations of both the source (HR system) and target (Salesforce) systems, such as API capabilities or rate limits. Considering all three aspects is crucial for designing a robust and feasible solution. Focusing on only one or two of these areas risks creating a solution that doesn't meet the business need or isn't technically viable.

A. This is too narrow. It focuses only on the technical integration mechanism and frequency, ignoring the core business requirements and potential system limitations that could block the project.

C. This is incomplete. While it correctly starts with the business requirement, it omits the critical analysis of system capabilities and constraints, which are essential for choosing a viable integration strategy.

1. Salesforce Well-Architected Framework, "Reliable: Evaluate Integration Needs," emphasizes the importance of understanding business requirements, system capabilities, and constraints during the initial evaluation phase of an integration project.

2. Salesforce Architects, "Architect's Guide to Building Forms," (Discovery Phase section) outlines the need to gather business requirements, technical requirements, and constraints before designing any solution. This principle applies broadly to all architectural design.

The scenario involves a synchronous callout during a customer checkout, a time-sensitive, user-facing process. The scalability and user experience of this solution are directly dependent on the performance of the external "available-to-promise" service. An architect must analyze the typical and worst-case response times to design appropriate timeouts, handle potential errors gracefully, and prevent long-running transactions from consuming limited shared resources or causing page timeouts. This analysis is fundamental to building a robust and scalable synchronous integration.

A. Query cursors are a database-specific concept, typically related to the Salesforce platform itself, not a consideration for an external web service callout.

C. The number of concurrent batch jobs is an asynchronous processing limit. This is irrelevant to a synchronous, real-time callout initiated by a user action.

1. Salesforce Architects, "Integration Patterns and Practices," March 2022, p. 18, "Remote Process Invocation—Request and Reply" section. This pattern highlights the tight coupling and dependency on the remote system's availability and performance.

2. Salesforce Developers, "Apex Developer Guide," "Callout Limits and Limitations." The guide specifies a default timeout of 10 seconds and a maximum of 120 seconds, underscoring the importance of understanding external service response times.

3. Salesforce Trailhead, "Apex Integration Services," "Apex Callout Basics." The module emphasizes handling callout responses and potential exceptions, which are directly influenced by the service's response time characteristics.

The Partner WSDL is designed for integrations that need to operate across multiple Salesforce orgs. It is loosely typed, meaning it works with generic sObject structures rather than being tied to the specific metadata (like custom objects and fields) of a single org. This allows a single client application to interact with different Salesforce orgs that may have varying configurations, making it the ideal choice for ISVs or multi-org enterprise tools. The client application dynamically inspects metadata and adapts as needed.

A. The Enterprise WSDL is strongly typed and bound to a specific Salesforce org's metadata. It would break if used against an org with a different configuration.

C. "SOAP API WSDL" is a general term. Both Enterprise and Partner WSDLs are part of the SOAP API. This option is not specific enough to be the correct answer.

1. Salesforce Developer Documentation, SOAP API Developer Guide, "Introduction to the WSDLs". The guide explicitly states, "Use the Partner WSDL if you are... building a client application that can be used against many different Salesforce orgs."

2. Salesforce Developer Documentation, SOAP API Developer Guide, "Enterprise WSDL". This section details how the Enterprise WSDL is "tied to a specific configuration of Salesforce" and is "strongly typed."

3. Salesforce Developer Documentation, SOAP API Developer Guide, "Partner WSDL". This section explains that the Partner WSDL is "loosely typed" and "static," making it suitable for dynamic, multi-org applications.

Salesforce, as the Customer Relationship Management (CRM) platform, is the natural System of Record (SoR) for customer and prospect data. Its primary function is to manage the entire customer lifecycle, from lead to support. Associates will use Salesforce as their main system of engagement to log interactions and get a 360-degree view. While the ERP is the SoR for financial data (invoices) and the Marketing solution is the SoR for campaign execution, Salesforce should act as the central hub. It will master the core customer record and integrate relevant data from the ERP and Marketing systems to provide a comprehensive view for sales and service users.

B. Creating a new custom database adds unnecessary complexity, cost, and another integration point, which is an architectural anti-pattern when a capable system like Salesforce already exists.

C. An ERP is optimized for financial and logistical transactions, not for managing the sales funnel, prospect data, or rich customer interactions. Making it the SoR for prospects is a misuse of the system.

1. Salesforce Well-Architected Framework, "Data Architecture: Identify Systems of Record," advises that the SoR should be the system best suited for managing a specific data domain. For customer relationship data, this is the CRM.

2. Salesforce Architects, "Integration Patterns and Practices," frequently positions Salesforce as the central system of engagement that aggregates data from other systems of record (like ERPs) to create a unified customer view.

3. Salesforce Trailhead, "Salesforce Architecture: The Big Picture," describes Salesforce's role as the center of the customer experience, making it the logical choice for the customer data SoR.

The requirements for reliability and auditable monitoring point towards a middleware solution like an Enterprise Service Bus (ESB). An ESB centralizes integration logic, providing robust error handling, message queuing for reliability (ensuring the payment request is processed even if the gateway is temporarily down), and centralized logging for auditing. This architectural pattern decouples Salesforce from the payment gateway, enhancing the overall resilience and maintainability of the integration, which is a primary concern for an integration architect dealing with critical financial transactions.

A. External Services is a declarative tool best for simpler, real-time use cases. It lacks the robust, centralized monitoring and reliability features of an ESB for critical, auditable processes.

B. A custom Apex callout creates a tight, point-to-point coupling. While logging can be custom-built, it lacks the enterprise-grade reliability and monitoring features inherent in a middleware pattern.

1. Salesforce Architects, Salesforce Integration Architecture Designer Exam Guide, "Integration Patterns" section. The guide discusses the role of middleware in orchestrating complex integrations that require high reliability and governance.

2. Salesforce Architects, Architect's Guide to Integration Patterns and Practices, "Remote Process Invocation—Request and Reply" pattern documentation. This guide contrasts simple point-to-point calls with more robust middleware-based orchestrations, recommending the latter for enterprise-grade requirements like guaranteed delivery and central monitoring. (See page 10, "Using Middleware").

3. Salesforce Help, Integration Patterns, "Data Integration Patterns". While not a direct match, the principles of using middleware for robust, reliable integrations are a core concept in Salesforce's architectural guidance.

This scenario describes the "Fire and Forget" integration pattern. Salesforce publishes a platform event ("fires" the message) to notify the remote system that a new order is ready. Salesforce does not wait for a response or acknowledgement from the remote system; its part of the process is complete upon publication ("forgets"). The remote system subscribes to these events and processes them asynchronously. This one-way, asynchronous data flow from a source to a target is the defining characteristic of the Fire and Forget pattern, making it ideal for notifications and decoupling systems.

A. Request and Reply is a synchronous pattern where the sender waits for an immediate response from the receiver. The use of asynchronous Platform Events contradicts this pattern.

C. Remote Call-In describes a pattern where an external system initiates a call into Salesforce. This scenario describes Salesforce initiating the communication by publishing an event.

1. Salesforce Architects, Architect's Guide to Integration Patterns and Practices, "Fire and Forget" pattern description (Page 18). This guide defines the pattern and explicitly lists Platform Events as a suitable mechanism for its implementation.

2. Salesforce Developers, Platform Events Developer Guide, "Platform Events and Business Process Automation". The guide illustrates how platform events enable decoupled, asynchronous processes, which is the foundation of the Fire and Forget pattern.

3. Salesforce Trailhead, Platform Events Basics, "Subscribe to Platform Events" unit. This module explains the asynchronous and decoupled nature of platform event communication, which aligns directly with the Fire and Forget pattern.