Salesforce Plat-Arch-204 Exam Questions

When integrating with a legacy SOAP-only application using a Fire and Forget pattern, Salesforce Outbound Messaging is the native, declarative choice.

Outbound Messaging is a platform feature that sends a SOAP message to a designated endpoint when specific criteria are met. It is inherently asynchronous and provides built-in reliability; if the legacy system is offline, Salesforce will automatically retry the delivery for up to 24 hours. This perfectly fits the 'Fire and Forget' requirement.

For the strongly-typed response back (Remote Call-In), the Enterprise WSDL is the correct recommendation.1415

Enterprise WSDL: This is a strongly-typed WSDL generated specifically for one org's metadata. It includes specific references to16 custom objects and fields, ensu17ring that the legacy system can communicate with Salesforce using a rigid, predictable data structure.

Partner WSDL (Option C): This is a loosely-typed WSDL designed for developers building tools that must work across many different orgs; it is not ideal for an internal, strongly-typed legacy integration.

While Platform Events (Option B) are a modern alternative, they typically use REST or Streaming APIs, making them a less natural fit for an application that 'can only support SOAP'. By combining Outbound Messaging and the Enterprise WSDL, the architect provides a robust, SOAP-native solution that satisfies the business's technical constraints and reliability requirements.

To fulfill the SLA of ensuring every payment is processed while simultaneously resolving the issue of intermittent update errors, the architect must introduce an orchestration layer capable of managing state and concurrency. In a high-volume payment environment, 'Fire and Forget' messages (as seen in the provided diagram) can lead to race conditions if multiple threads attempt to update a single record simultaneously---a common challenge when scaling payment systems.

The recommendation to have Middleware coordinate request delivery and payment processing (Option C) transforms the architecture into a managed queueing system. By coordinating delivery, the middleware can act as a traffic controller, ensuring that requests are delivered sequentially or that appropriate locks are respected before an update is attempted. This orchestration allows the system to meet its SLA by implementing a 'guaranteed delivery' pattern, where the middleware tracks the status of each payment and only 'forgets' the message once the Payment System confirms successful processing.

Furthermore, the architect should emphasize idempotency by leveraging the globally unique identifier created at the Data Entry Point. The Payment System should be designed to use this identifier to check if a specific transaction has already been processed before attempting an update. This prevents duplicate entries and conflicting updates, even if the middleware retries a message due to a network timeout. While retries (Options A and B) are part of a resilient system, they do not solve the root cause of record contention; only the coordination and sequencing provided by the middleware can ensure a stable, conflict-free integration flow.78

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.