SalesForce INTEGRATION-ARCHITECT - Questions & Answers

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

In this scenario, the architecture involves a Remote-Call-In pattern or Batch Synchronization , where an external system (the middleware or ETL tool) initiates communication with Salesforce to update records.
For any external system to securely access Salesforce APIs and perform these updates, it must be authenticated and authorized.

The Connected App is the foundational framework that allows an external application to integrate with Salesforce using APIs and standard protocols, such as OAuth 2.0 and SAML. By configuring a Connected
App, the architect can define which permissions (Scopes) the middleware has, such as the ability to access data via the REST or Bulk API. This is the correct choice because the middleware needs to "log in" to Salesforce to push the phone classification data back into the Account or Contact records.

Option B, an API Gateway , is typically used to manage and secure requests going out of an organization to external services, or to provide a facade for on-premise APIs; it does not handle the inbound
authentication into Salesforce itself. Option C, Remote Site Settings , is a configuration used solely to permit Salesforce to make outbound calls to a specific external URL (for example, if Salesforce were calling the phone classification service directly via Apex).

Given that the business is flexible with timing (allowing for nightly or 12-hour syncs) and handles 100,000 calls, a Batch Synchronization pattern via an ETL tool is highly efficient. The ETL tool will authenticate against the Connected App using a secure OAuth flow (such as the JWT Bearer Flow for server-to-server integration), retrieve the new phone numbers, call the external classification API, and then bulk-update the Salesforce records. This setup ensures a secure, scalable, and manageable integration that respects Salesforce's security architecture while meeting the high-volume data requirements of the call center.

In a multi-system landscape, maintaining data synchronization requires a robust Identity Mapping strategy.
The standard Salesforce architectural recommendation is to use External ID fields to store the unique identifiers from each secondary system.

By storing the ERP ID, Ticketing ID, and Data Lake ID as External IDs in Salesforce, the middleware can perform upsert operations without needing to first query Salesforce for its internal ID. This reduces the number of API calls and simplifies the integration logic. Conversely, when Salesforce pushes a change to the ERP, it sends the stored ERP ID, allowing the ERP to instantly identify the correct target record.

Option B (Caching at the middleware) is a high-maintenance "anti-pattern" that introduces a new point of failure if the cache goes out of sync with the actual systems.
Option C (Change Data Capture) is a mechanism for notifying systems of changes, but it does not solve the underlying identity mapping problem. Using External IDs creates a stable, searchable, and performant cross-reference that is the backbone of any successful "hub-and-spoke" integration architecture.

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

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.

When dealing with a "big surge" or high-volume influx of requests, a synchronous pattern like Request and Reply (Option A) can lead to significant performance bottlenecks. In a synchronous model, each Salesforce user thread must wait for the external scheduling system to respond, which could lead to "Concurrent Request Limit" errors during peak times.

The Remote Process Invocation-Fire and Forget pattern is the architecturally sound choice for managing surges. In this pattern, Salesforce captures the registration intent and immediately hands it off to an asynchronous process or a middleware queue. Salesforce does not wait for the external system to process the room capacity logic; instead, it receives a simple acknowledgment that the message was received.

This pattern decouples the front-end user experience from the back-end processing limits. Middleware can then "drip-feed" these registration4s into the scheduling system at a rate it can handl5e. If the scheduling system becomes overwhelmed or goes offline, the messages remain safely in the queue. Option C (Batch) is unsuitable because users expect near real-time feedback on their registration attempt, even if the final confirmation is sent a few minutes later. By utilizing Fire and Forget, NTO ensures a responsive Community Experience during the critical launch window while maintaining system stability.

When external services are highly volatile (added/removed frequently), the goal is to decouple the Salesforce UI from the underlying service logic. An Integration Architect should propose invoking a middleware service to retrieve the valid shipping methods.

By using middleware (such as an ESB or MuleSoft) as an abstraction layer, Salesforce doesn't need to "know" the details of the 34 different shipping providers. When a sales rep selects a country, Salesforce makes a single callout to the middleware. The middleware then performs the routing logic to identify which shippers are active for that region and returns a standardized list to Salesforce.

Option A is a "maintenance nightmare"; every time a shipping service changes in any of the 34 countries, an admin would need to manually update picklist values and dependencies in Salesforce, which is not scalable. Option C (Platfor31m Events) is an asynchronous pattern unsuitable for a real-time "request-reply" scenario where a rep is waiting for an estimate during a live customer interaction. Utilizing middleware centralizes the logic, simplifies Salesforce configuration, and allows NTO to change shipping providers without any code deployments or metadata updates in the Salesforce org.

When implementing Salesforce to achieve a 360-degree view of the customer, the platform replaces legacy "siloed" applications that perform core CRM functions. Based on the business goals provided, Salesforce will be the master for Marketing, Sales, and Service.

The systems to be retired are those whose functionality is natively subsumed by Salesforce:

Email Marketing: Replaced by Salesforce Marketing Cloud or native marketing features.

Sales Activity: Replaced by Sales Cloud, which masters lead management, opportunity tracking, and activity logging.

Case Management: Replaced by Service Cloud, which provides the tools for customer support agents to resolve inquiries.

Order Management and Quoting are specifically noted as "Enterprise capabilities" that the business wants to reuse .

This means these systems will stay in the landscape and be integrated with Salesforce, rather than being retired.

Therefore, any option containing "Order Management" (A and C) is incorrect. Retiring the marketing, sales activity, and service systems allows the organization to consolidate its customer data into a single platform, fulfilling the primary goal of the Salesforce transformation.

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.

For monitoring high-volume Bulk API jobs, the standard and most efficient architectural recommendation is to use the native Bulk Data Load Jobs page in Salesforce Setup.

This page provides a comprehensive, out-of-the-box view of all asynchronous API jobs, including their status (Queued, In Progress, Completed, Failed), the number of records processed, and any overall job errors. It allows administrators to download the result files for each batch to see record-level successes and failures without the overhead of custom code or data storage.

Option B is generally discouraged for high-volume nightly loads. Since the Bulk API is designed to bypass standard synchronous logic for performance, writing errors to a custom object for millions of records would consume significant data storage and could trigger additional governor limit issues during the load itself.

Option C is ineffective for Bulk API monitoring; debug logs capture Apex execution but do not monitor the background processing of asynchronous Bulk API batches, and they would quickly become overwhelmed by the volume of data. For enterprise-grade monitoring, the native UI provides the necessary visibility into job health with zero impact on platform performance or storage.