2026年最新のPlat-Arch-204実際問題集には試験のコツがあるPDF試験材料
心強いPlat-Arch-204のPDF問題集問題
質問 # 22
Northern Trail Outfitters needs to make synchronous callouts "available-to-promise" services to query product availability and reserve inventory during the customer checkout process. What should an integration architect consider when building a scalable integration solution?
- A. The maximum query cursors open per user on the service
- B. The typical and worst-case historical response times
- C. The number of batch jobs that can run concurrently
正解：B
解説：
In a Synchronous Request-Reply pattern, the user's experience is directly tied to the performance of the external service. For a mission-critical "Available-to-Promise" (ATP) service during checkout, the most vital scalability consideration is the typical and worst-case historical response times of the target system.
Salesforce imposes strict Governor Limits on synchronous callouts to protect platform health. Specifically, if an ATP callout takes longer than 120 seconds, the transaction will time out. More importantly, Salesforce limits the number of long-running requests (those lasting longer than 5 seconds). If multiple users are checking out simultaneously and the external inventory system begins to respond slowly (worst-case), those requests can quickly occupy all available slots in the concurrent request queue, leading to "Concurrent Request Limit Exceeded" errors for all users in the org.
By analyzing historical response times, the architect can determine if the service is reliable enough for a synchronous callout. If the worst-case response time frequently exceeds 5 seconds, the architect should consider a more resilient pattern, such as the Continuation pattern or an asynchronous approach, to prevent blocking the UI thread and hitting platform limits. Options A and C are irrelevant to synchronous checkout performance; query cursors relate to database state, and batch jobs are asynchronous background processes that do not impact real-time user checkout latency.
質問 # 23
Salesforce is the system of record for Leads, Contacts, Accounts, and Cases. Customer data also exists in an ERP, ticketing system, and data lake, each with unique identifiers. Middleware is used to update systems bidirectionally. Which solution should be recommended to handle this?
- A. Locally cache external IDs at the middleware layer.
- B. Design an MDM solution that maps external IDs to the Salesforce record ID.
- C. Use Change Data Capture to update downstream systems accordingly.
正解：B
解説：
In a complex landscape where multiple systems contain overlapping customer data, each with its own primary key, the core architectural challenge is Identity Management. To ensure that an update in Salesforce (the System of Record) correctly updates "Customer A" in the ERP and "Customer A" in the Data Lake, a Master Data Management (MDM) strategy is required.
An MDM solution creates a Cross-Reference (X-Ref) Table or a "Golden Record" that maps the unique identifiers from all systems. In the Salesforce record, the architect should implement External ID fields for each corresponding system (e.g., ERP_ID__c, Ticket_System_ID__c).
Why this is the superior recommendation:
Bidirectional Integrity: When the middleware receives an update from the ERP, it uses the ERP_ID__c to perform an "upsert" in Salesforce, ensuring no duplicates are created.
Traceability: It allows for easy auditing of data lineage across the enterprise.
Decoupling: Salesforce doesn't need to know the internal logic of the ERP; it simply holds the reference key.
Option B (CDC) is a delivery mechanism, not an identity management strategy; it tells you that something changed, but not which record in the ERP it corresponds to without the ID mapping. Option C (Local caching in middleware) is an "anti-pattern" because it makes the middleware stateful; if the middleware cache is lost or out of sync, the entire integration breaks. By designing an MDM-based mapping solution directly within the data model, the architect ensures a robust, scalable, and transparent identity framework for the entire enterprise.
質問 # 24
Northern Trail Outfitters uses Salesforce to track leads and opportunities, and to capture order details. However, Salesforce isn't the system that holds or processes orders. After the order details are captured in Salesforce, an order must be created in the Remote system, which manages the order's lifecycle. The integration architect for the project is recommending a remote system that will subscribe to the platform event defined in Salesforce. Which integration pattern should be used for this business use case?
- A. Fire and Forget
- B. Request and Reply
- C. Remote Call-In
正解：A
解説：
In this scenario, Salesforce acts as the trigger for a business process that completes in an external system. The architect's recommendation for the remote system to subscribe to a platform event is the classic implementation of the Remote Process Invocation-Fire and Forget pattern.1 In a Fire and Forget pattern, Salesforce initiates a process by publishing a message (the event) to the event bus and then immediately continues its own2 processing without waiting for a functional response from the target system. The "Fire" part occurs when the order details are captured and the event is published; the "Forget" part refers to Salesforce handing off the responsibility of order creation to the remote system. This pattern is ideal for improving user experience and system performance, as it avoids blocking the user interface while waiting for potentially slow back-office systems to respond.
Option A (Request and Reply) is incorrect because that would require Salesforce to make a synchronous call and wait for the remote system to confirm the order was created before allowing the user to proceed. Option C (Remote Call-In) is the inverse of what is described; it would involve the remote system actively reaching into Salesforce to "pull" the data, whereas here Salesforce is "pushing" the notification via an event stream. By using Platform Events to facilitate this hand-off, Northern Trail Outfitters ensures a decoupled, scalable architecture where the remote system can process orders at its own pace while Salesforce remains responsive to sales users.
質問 # 25
Northern Trail Outfitters submits orders to a manufacturing system web service that has experienced multi-day outages. Which solution should an integration architect recommend to handle errors during these types of outages?
- A. Use middleware queuing and buffering to insulate Salesforce from system outages.
- B. Use Platform Event replayId and custom scheduled Apex process to retrieve missed events.
- C. Use Outbound Messaging to automatically retry failed service calls.
正解：A
解説：
When a target system experiences prolonged outages (lasting "several days"), point-to-point integration solutions built within Salesforce are likely to fail or reach their retry limits. For example, Salesforce Outbound Messaging (Option B) only retries for up to 24 hours before dropping the message.
The architecturally robust solution is to introduce a Middleware layer (ESB or iPaaS) that provides queuing and buffering. In this model, Salesforce sends the order to the middleware. The middleware immediately acknowledges receipt (preserving Salesforce performance). If the manufacturing system is offline, the middleware stores the message in a persistent queue.
Middleware is designed for this high level of Quality of Service (QoS). It can be configured with custom retry logic-such as waiting 30 minutes between attempts-and can hold millions of messages for days or even weeks. This effectively "insulates" Salesforce from the manufacturing system's instability. Option C is overly complex and requires custom development in both the event bus and Apex, whereas middleware provides this functionality as a native capability. By using middleware, the architect ensures that no orders are lost during extended manufacturing downtime and that the integration is decoupled and resilient.
質問 # 26
Northern Trail Outfitters requires an integration to be set up between one of its Salesforce orgs and an External Data Source using Salesforce Connect. The External Data Source supports Open Data Protocol. Which configuration should an integration architect recommend be implemented in order to secure requests coming from Salesforce?
- A. Configure Identity Type for OData connection.
- B. Configure a certificate for OData connection.
- C. Configure Special Compatibility for OData connection.
正解：A
解説：
Salesforce Connect is a powerful tool for data virtualization, allowing users to view and manage data in external systems (via OData) as if it were stored natively in Salesforce. However, a critical security decision during the setup of an External Data Source is determining the Identity Type.
The Identity Type determines how the external system authenticates the Salesforce user. There are two primary options:
Named Principal: Every Salesforce user accesses the external system using the same set of credentials. This is easier to maintain but provides less granular security tracking in the target system.
Per User: Each individual Salesforce user must provide their own credentials for the external system. This ensures that the data visible in Salesforce respects the user's specific permissions in the external source.
Configuring the Identity Type is the fundamental way an architect secures OData requests because it defines the authentication boundary between the platforms. While certificates (Option A) can be used for transport layer security, the "Identity Type" configuration is the specific Salesforce Connect setting that governs how a session is authorized. Option B (Special Compatibility) is a technical setting used to handle non-standard OData implementations and does not directly relate to securing the request. By recommending the correct Identity Type, the architect ensures that the integration adheres to the "Principle of Least Privilege," ensuring that users only see the external data they are authorized to access.
質問 # 27
A subscription-based media company's system landscape forces many subscribers to maintain multiple accounts and to log in more than once. An Identity and Access Management (IAM) system, which supports SAML and OpenId, was recently implemented to improve the subscriber experience through self-registration and single sign-on (SSO). The IAM system must integrate with Salesforce to give new self-service customers instant access to Salesforce Community Cloud.
Which requirement should Salesforce Community Cloud support for self-registration and SSO?
- A. SAML SSO and Just-in-Time (JIT) provisioning
- B. SAML SSO and Registration Handler
- C. OpenId Connect Authentication Provider and JIT provisioning
正解：C
質問 # 28
A Salesforce customer is planning to roll out Salesforce for all of their sales and service staff. Senior management has requested that monitoring be in place for Operations to notify any degradation in Salesforce performance. How should an Integration consultant implement monitoring?
- A. Use APIEVENT to track all user initiated API calls through SOAP, REST, or Bulk APIs.
- B. Use Salesforce API Limits to capture current API usage and configure alerts for monitoring.
- C. Identify critical business processes and establish automation to monitor performance against established benchmarks.
正解：C
解説：
Effective operational monitoring focuses on the end-user experience and business outcomes rather than just raw technical metrics. An Integration consultant should identify critical business processes (e.g., "Lead Conversion" or "Order Processing") and establish benchmarks to detect performance degradation.
Monitoring purely technical limits (Option A) or individual API events (Option C) provides "noise" without context. For example, if API usage is high but the system is responding quickly, there is no degradation. However, if a critical process that normally takes 2 seconds starts taking 10 seconds, that is a clear indicator of a performance issue that impacts the business.32 The consultant should use tools like Salesforce Event Monitoring or external APM (Application Performance Management) tools to track the execution time of these key transactions. By setting alerts when performance deviates from established benchmarks, Operations can be proactively notified before users begin to lose productivity or abandon the system. This holistic approach ensures that monitoring is aligned with business value and provides actionable insights for troubleshooting bottlenecks in code, automation, or integrations.
質問 # 29
A security assessment noted vulnerabilities on unmanaged packages; notably, secrets like usernames, passwords, and OAuth tokens are stored in plain text. Which persistence mechanisms should an integration architect require to ensure that secrets are protected from deliberate or inadvertent exposure?
- A. Encrypted Custom Fields and Protected Custom Settings
- B. Named Credentials and Protected Custom Settings
- C. Protected Custom Metadata Types and Named Credentials
正解：B
質問 # 30
The URL for a business-critical external service providing exchange rates changed without notice. Which solutions should be implemented to minimize potential downtime for users in this situation?
- A. Enterprise Service Bus (ESB) and Remote Site Settings
- B. Remote Site Settings and Named Credentials
- C. Named Credentials and Content Security Policies
正解：B
解説：
To minimize downtime when an external endpoint changes, an Integration Architect must ensure that the URL is not "hardcoded" within Apex code or configuration. The standard Salesforce mechanism for abstracting and managing external endpoints is Named Credentials.
Named Credentials specify the URL of a callout endpoint and its required authentication parameters in one definition. If the URL changes, an administrator simply updates the "URL" field in the Named Credential setup. This change takes effect immediately across all Apex callouts, Flows, and External Services that reference it, without requiring a code deployment or a sandbox-to-production migration.
Along with Named Credentials, Remote Site Settings (or the more modern External Website Configurations) are required. Salesforce blocks all outbound calls to URLs that are not explicitly whitelisted.
By having both in place, the remediation process is:
Update the URL in the Named Credential.
Update (or add) the new URL in the Remote Site Settings.
This approach follows the "Separation of Concerns" principle. Option B (ESB) could technically handle this, but it adds an extra layer of failure and complexity for a simple URL change. Option C (Content Security Policies) is used to control which resources (like scripts or images) a browser is allowed to load in the UI; it does not govern server-side Apex callouts. Therefore, the combination of Named Credentials and Remote Site whitelisting is the most efficient and standard way to provide architectural agility and minimize downtime.
質問 # 31
Universal Containers (UC) works with third-party agents on banner initial design concepts. The design files (2.5 GB) are stored in an on-premise file store. UC wants to allow agencies to view these files in the community. Which solution should an integration architect recommend?
- A. Create a custom object to store the file location URL; when a community user clicks on the file URL, redirect the user to the on-premise system file location.
- B. Use Salesforce Files to link the files to Salesforce records and display the record and the files in the community.
- C. Create a Lightning component with a Request and Reply integration pattern to allow the community users to download the design files.
正解：A
解説：
When dealing with extremely large files, such as the 2.5 GB design files mentioned, an architect must consider the platform's file size limits and storage costs. Salesforce Files have a maximum upload size of 2 GB through most interfaces, making Option B technically unfeasible for a 2.5 GB file. Furthermore, storing numerous large files natively in Salesforce would lead to excessive storage consumption and costs.
The most efficient and cost-effective approach is Data Virtualization or Redirection. By creating a custom object to store the file location URL (Option C), the actual file remains in the performant on-premise file store. When the community user needs to access the design, they are redirected to the source system, which handles the massive data transfer. This fulfills the requirement to "view" the files without the overhead of moving gigabytes of data through the Salesforce infrastructure. Option A is less ideal because a 2.5 GB download over a standard Request-Reply pattern would likely lead to timeouts and a poor user experience.
質問 # 32
Northern Trail Outfitters is creating a distributable Salesforce package. The package needs to call into a Custom Apex REST endpoint in the central org. The security team wants to ensure a specific integration account is used in the central org that they will authorize after installation. Which item should an architect recommend?
- A. Contact Salesforce Support and create a case to temporarily enable API access for managed packages.
- B. Create a connected app in the central org and add the callback URL for each org in the package it is installed in to redirect after a successful authentication.
- C. Use an encrypted field to store the password that the security team enters.
正解：B
解説：
For a distributable package to securely access a central "Hub" org, the architecture must support the OAuth 2.0 Web Server Flow. This flow is designed for applications (like the package installed in a "Spoke" org) that can securely store a Client Secret and need to act on behalf of a specific user.
The Connected App in the central org acts as the "Identity and Access" gatekeeper. A critical component of the Connected App configuration is the Callback URL (Redirect URI). When a user in the "Subscriber" org clicks "Authorize," Salesforce redirects them to the central org to log in. After successful authentication, the central org needs to know where to send the "Authorization Code" back to.
In a multi-org packaging scenario, each subscriber org will have a unique instance URL (e.g., na15.salesforce.com). The architect must ensure that the Connected App's callback URLs are correctly configured to handle these redirects.
Option C (Encrypted Passwords) is a major security risk and is considered an "anti-pattern" in modern integration. Option A is unnecessary, as API access is a standard feature. By using the Connected App with correct Callback URLs, the architect allows the security team in the central org to oversee exactly which "Spoke" orgs have authorized access. They can use the "Connected Apps OAuth Usage" page to monitor, rotate secrets, or revoke access for individual orgs, providing the granular security control required for an enterprise-grade distributed Salesforce architecture.
質問 # 33
Northern Trail Outfitters (NTO) uses different shipping services for each of the 34 countries it serves. Services are added and removed frequently. Sales representatives globally need to select between valid service(s) for the customer's country and request shipping estimates. Which solution should an architect propose?
- A. Use Platform Events to construct and publish shipper-specific events.
- B. Invoke middleware service to retrieve valid shipping methods.
- C. Store shipping services in a picklist that is dependent on a country picklist.
正解：B
解説：
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.
質問 # 34
A customer is evaluating the Platform Events solution and would like help in comparing/contrasting it with Outbound Messaging for real-time/near-real time needs. They expect 3,000 customers to view messages in Salesforce. What should be evaluated and highlighted when deciding between the solutions?12
- A. Both Platform Events and Outbound Messaging are highly scalable. However, unlike Outbound Messaging, only Platform Events have Event Delivery and Event Publishing limits to be considered.
- B. Message sequence is possible in Outbound Messaging, but not guaranteed with Platform Events. Both offer very high reliability. Fault handling and recovery are fully handled by Salesforce.
- C. In both Platform Events and Outbound Messaging, the event messages are retried by and delivered in sequence, and 3only once. Sales4force ensures there is no duplicate message delivery.
正解：A
解説：
When comparing Platform Events and Outbound Messaging for a near-real-time architecture, a Salesforce Platform Integration Architect must evaluate fundamental differences in their delivery models and governance. While both provide declarative, asynchronous "Fire-and-Forget" capabilities, their technical constraints differ significantly, particularly regarding scalability and platform limits.
The key architectural highlight in this scenario is that Platform Events operate on a specialized event bus with specific Event Publishing and Event Delivery limits. Unlike Outbound Messaging, which is governed by more general daily outbound call limits (often tied to user licenses), Platform Events have a dedicated allocation for the number of events that can be published per hour and delivered in a 24-hour period to external clients via the Pub/Sub API or CometD. For example, the number of concurrent subscribers to a Platform Event channel is typically capped at 2,000 for standard configurations. Since the customer expects 3,000 customers to view these messages, this limit is a critical evaluation point; the architecture would need to account for this gap, perhaps by using middleware to fan out messages to the larger audience.
In contrast, Outbound Messaging does not have an "Event Delivery" limit in the same sense. It is a point-to-point SOAP-based push mechanism where Salesforce manages retries for up to 24 hours if the receiving endpoint is unavailable. However, it is less flexible for multi-consumer scenarios because it requires a separate configuration for every unique destination.
Regarding the other options: Option A is incorrect because neither system strictly guarantees "exactly-once" delivery without the possibility of duplicates; in fact, Outbound Messaging may deliver a message more than once if it doesn't receive a timely acknowledgment. Option B is incorrect because Platform Events do not have built-in "fault recovery" handled by Salesforce in the same way as Outbound Messaging's automatic retry queue; with Platform Events, it is the subscriber's responsibility to use a Replay ID to retrieve missed events within the 72-hour retention window. Therefore, highlighting the unique delivery and publishing limits is the most vital step for the architect.
質問 # 35
An integration architect has designed a mobile application for Salesforce users to get data while on the road using a custom user interface (UI). The application is secured with OAuth and is currently functioning well. There is a new requirement where the mobile application needs to obtain the GPS coordinates and store them on a custom geolocation field. The geolocation field is secured with field-level security, so users can view the value without changing it. What should be don4e to meet the requirement?
- A. The mobil10e device makes a REST Apex inbound call.
- B. The 15mobile device makes a REST API inboun16d call.
- C. The mobile device receives19 a REST Apex callout call.
正解：B
解説：
When a custom mobile application already secured with OAuth needs to update a record in Salesforce, the standard architectural recommendation is to use the REST API. The REST API is optimized for mobile environments because it uses lightweight JSON payloads and follows standard HTTP methods (such as PATCH for updates), which are highly compatible with mobile development frameworks.
In this specific scenario, the architect must address the Field-Level Security (FLS) constraint. Because the geolocation field is set to read-only for users, a standard UI-based update would typically fail. However, when using an inbound REST API call with a properly authorized integration user or via a "System Mode" context (if utilizing a custom Apex REST resource), the system can be configured to bypass UI-level restrictions while maintaining data integrity.
The mobile device captures the coordinates via the device's native GPS capabilities and initiates an inbound call to the Salesforce REST endpoint. Option A (Apex inbound call) is a subset of REST functionality but is only necessary if complex server-side logic is required that the standard REST API cannot handle. Option C is technically incorrect as mobile devices do not typically "receive" callouts from Salesforce in this pattern; they initiate the requests. By leveraging the standard REST API, the architect ensures a scalable, secure, and standardized integration that adheres to Salesforce's mobile-first integration principles.
質問 # 36
Northern Trail Outfitters (NTO) uses Salesforce to track leads, opportunities, and order details that convert leads to customers. However, orders are managed by an external (remote) system. Sales reps want to view and update real-time order information in Salesforce. NTO wants the data to only persist in the external system. Which type of integration should an architect recommend to meet this business requirement?
- A. Data Synchronization
- B. Data Virtualization
- C. Process Orchestration
正解：B
解説：
The requirement to view and update data in real-time while ens5uring the data only persists in the external system is the definition of a Data Virtualization pattern. In this architectural model, Salesforce does not store a local copy of the data (which would be Data Synchronization), but instead acts as a window into the external system of record.
An Integration Architect implements Data Virtualization primarily through Salesforce Connect. This tool allows the external system's order table to be represented as an External Object in Salesforce. Because the data is retrieved on-demand via a web service call (typically using the OData protocol), it is always "real-time." Furthermore, since Salesforce Connect supports writeable external objects, sales reps can update the order information directly from the Salesforce UI, and those changes are sent back to the external system immediately without being saved to the Salesforce database.
This approach is superior to Data Synchronization (Option A) in this specific use case because it eliminates the need for data storage costs and the complexity of keeping two databases in sync. It is also distinct from Process Orchestration (Option C), which focuses on the sequencing of tasks across multiple systems rather than the real-time presentation of external data. By utilizing Data Virtualization, NTO achieves a seamless user experience where external orders look and feel like native Salesforce records while strictly adhering to the "no persistence" constraint.
質問 # 37
A CSR needs to obtain confirmation of payment from an external RESTful service before upgrading a customer's service. The integration must be reliable and monitored for audit purposes. What should an integration architect recommend?
- A. Make a callout to the payment gateway through ESB supporting error handling and logging for audit purposes.
- B. Build a custom Apex callout to external payment gateway service and provide a success message to the CSR; the details of callouts and responses are logged for audit purposes.
- C. Use External Services feature to integrate payment gateway to Salesforce to ensure real-time updates to the CSR and support post payment processes.
正解：A
解説：
When an integration involves financial transactions (payment gateways) and strict audit and reliability requirements, the most robust architectural pattern is to use an Enterprise Service Bus (ESB) or middleware as the orchestration layer.
An ESB provides critical enterprise-grade capabilities that Salesforce cannot easily replicate natively:
Centralized Auditing/Logging: The ESB can capture the full payload of every payment request and response, storing them in a secure log for regulatory compliance and financial audits.
Sophisticated Error Handling: If the payment gateway returns a transient error, the ESB can manage retries or circuit-breaker patterns to prevent system failure.
Protocol Mediation: The ESB can bridge any technical gaps between the Salesforce UI and the external RESTful service.
Option A (External Services) and Option B (Apex Callouts) are point-to-point integrations. While they can facilitate a real-time response, they place the burden of logging, audit trail management, and complex error handling directly on the Salesforce platform. For a B2C enterprise, "hard-coding" these sensitive financial processes into Apex triggers or Flows creates a maintenance challenge and lacks the transparent, enterprise-wide visibility that a middleware solution provides. By routing the payment through an ESB, the architect ensures that the CSR gets their "real-time" confirmation while the company maintains the high level of reliability and accountability required for financial operations.
質問 # 38
Northern Trail Outfitters needs to present shipping costs and estimated delivery times to its customers. Shipping services used vary by region and have similar but distinct service request parameters. Which integration component capability should be used?
- A. Enterprise Service Bus user interface to collect shipper-specific form data
- B. Apex REST Service to implement routing logic to the various shipping service
- C. Enterprise Service Bus to determine which shipping service to use and transform requests to the necessary format
正解：C
解説：
When dealing with multiple external service providers (like different regional shippers) that have varying API requirements, the most scalable architectural choice is an Enterprise Service Bus (ESB) or middleware solution. This scenario describes a classic "Orchestration" and "Transformation" use case.
An ESB excels at:
1. Routing/Mediation: The ESB can receive a single, standardized request from Salesforce ("Get Shipping Rates") and use business logic to determine which regional carrier's API should be called.
2. Transformation: Each carrier likely has a distinct XML or JSON schema. The ESB can transform the common data model sent by Salesforce into the specific format required by the chosen shipper.
3. Protocol Bridging: If one shipper uses SOAP and another uses REST, the ESB handles these technical differences, allowing Salesforce to interact with a single, simplified interface.
Option A (Apex REST) would require the Salesforce team to maintain custom code for every new shipping provider added, leading to high technical debt and maintenance challenges. Option C is incorrect because an ESB is a back-end infrastructure component, not a user interface tool.
By utilizing an ESB, Northern Trail Outfitters decouples Salesforce from the complexities of the shipping providers' APIs. This "Hub and Spoke" model means that adding a new regional shipper in the future only requires configuration within the ESB, rather than a full code deployment in Salesforce. This provides the agility and architectural separation necessary for a global retail operation.
質問 # 39
An enterprise customer with more than 10 million customers has a landscape including an Enterprise Billing System (EBS), a Document Management System (DMS), and Salesforce CRM. Customer Support needs seamless access to customer billing information from the EBS and generated bills from the DMS. Which authorization and authentication need should an integration consultant consider while integrating the DMS and EBS with Salesforce?
- A. Consider options to migrate DMS and EBS into Salesforce.
- B. Identify options to maintain DMS and EBS authentication and authorization details in Salesforce.
- C. Consider Enterprise security needs for access to DMS and EBS.
正解：C
解説：
When integrating Salesforce with high-security enterprise systems like an Enterprise Billing System (EBS) and a Document Management System (DMS), the primary architectural concern is respecting the Enterprise security needs for access control. These systems often contain highly sensitive financial data and are governed by strict regulatory requirements (e.g., PCI-DSS or GDPR).
The integration consultant must evaluate how to extend existing enterprise identity and authorization policies to Salesforce users. This often involves a Identity Federation strategy using protocols like SAML 2.0 or OpenID Connect. Instead of maintaining separate credentials in Salesforce (which Option A suggests and is generally an "anti-pattern" for 10 million records), the consultant should consider using a central Identity Provider (IdP).
By considering enterprise security needs, the architect ensures that when a support agent clicks a link in Salesforce to view a bill, the request is authenticated against the enterprise's security gateway. This allows for Single Sign-On (SSO) while ensuring that authorization (who can see what) remains mastered in the source systems or the central IdP. Migration (Option C) is physically and technically unfeasible for systems handling 10 million customers' historical bills and real-time processing. The focused objective is to build a "window" into these systems from Salesforce while maintaining the integrity of the enterprise's existing security perimeter.
質問 # 40
A customer imports data from an external system into Salesforce using Bulk API. These jobs have batch sizes of 2,000 and are run in parallel mode. The batches fail frequently with the error "Max CPU time exceeded". A smaller batch size will fix this error. What should be considered when using a smaller batch size?
- A. Smaller batch size may increase time required to execute bulk jobs.
- B. Smaller batch size may exceed the concurrent API request limits.
- C. Smaller batch size can trigger "Too many concurrent batches" error.
正解：A
解説：
The Bulk API is designed to process massive datasets by breaking them into smaller batches that Salesforce processes asynchronously. When a batch fails with the "Max CPU time exceeded" error, it typically indicates that the complexity of the operations triggered by the record-such as Apex triggers, Flows, or complex sharing calculations-exceeds the 10,000ms limit within a single transaction.
Reducing the batch size is the standard architectural remedy because it reduces the number of records processed in a single transaction, thereby lowering the total CPU time consumed by those records. However, the architect must consider the impact on the overall throughput and execution time.
When batch sizes are smaller, the total number of batches required to process the same dataset increases. For instance, moving from a batch size of 2,000 to 200 for a 1-million-record dataset increases the number of batches from 500 to 5,000. Each batch carries its own overhead for initialization and finalization within the Salesforce platform. Consequently, while the individual batches are more likely to succeed, the total time required to complete the entire job will increase.
The architect should also be aware of the daily limit on the total number of batches allowed (typically 15,000 in a 24-hour period). While Option C mentions API request limits, the Bulk API is governed more strictly by its own batch limits. Option B is less likely because "parallel mode" naturally manages concurrency. Thus, the primary trade-off the architect must present to the business is a gain in reliability (successful processing) at the cost of total duration (increased sync time).
質問 # 41
Northern Trail Outfitters is creating a distributable Salesforce package. The package needs to call into a Custom Apex REST endpoint in the central org. The security team wants to ensure a specific integration account is used in the central org that they will authorize after installation. Which item should an architect recommend?
- A. Create an authentication provider in the package and set the consumer key and consumer secret of the connected app in the central org.
- B. Contact Salesforce Support and create a case to temporarily enable API access for managed packages.
- C. Use an encrypted field to store the password that the security team enters.
正解：A
解説：
When building a distributable package (likely a Managed Package) that must securely communicate back to a central "Hub" org, the architect must use a framework that supports OAuth 2.0 flows. Storing plain-text or even encrypted passwords (Option B) is a security violation and is brittle across different environments.
The architecturally sound solution is to leverage the Authentication Provider and Named Credentials framework. In the central org, a Connected App is created to act as the OAuth endpoint. In the package, an Authentication Provider is configured using the Consumer Key and Consumer Secret from that Connected App. This setup allows the administrator in the "Subscriber" org (the org where the package is installed) to initiate an OAuth flow.
When the security team "authorizes" the integration after installation, they are essentially completing the OAuth handshake. This grants the subscriber org an Access Token and a Refresh Token associated with the specific integration user in the central org. This mechanism ensures:
Credential Security: No passwords are ever stored in the code or metadata.
Centralized Control: The security team in the central org can revoke the Refresh Token at any time to kill the integration.
Scalability: The same package can be distributed to hundreds of orgs, each with its own unique, secure connection to the central Hub.
By using an Authentication Provider combined with a Named Credential, the Apex code in the package can simply call the endpoint by its developer name, and Salesforce handles the entire authentication header injection automatically, ensuring a robust and secure cross-org integration.
質問 # 42
An enterprise customer is implementing Salesforce for Case Management. Based on the landscape (Email, Order Management, Data Warehouse, Case Management), what should the integration architect evaluate?
- A. Integrate Salesforce with Data Warehouse, Order Management, and Email Management System.
- B. Integrate Salesforce with Email Management System, Order Management System, and Case Management System.
- C. Integrate Salesforce with Order Management System, Data Warehouse, and Case Management System.
正解：A
解説：
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.
質問 # 43
Given the diagram above, a Salesforce org, middleware, and Historical Data store exist with connectivity between them. Historical records are archived from Salesforce, moved to a Historical Data store (which houses 20 million records and growing), and fine-tuned to be performant with search queries. When reviewing occasional special cases, call center agents that use Salesforce have requested access to view the historical case items that relate to submitted cases.
Which mechanism and patterns are recommended to maximize declarative configuration?
- A. Use an ESB tool with a Data Virtualization pattern, expose the OData endpoint, and then use Salesforce Connect to consume and display the External object alongside the Case object.12
- B. Use an ESB tool with a Fire and Forget pattern, and then publish a platform event for the requested historical data.
- C. Use an ESB tool with a Request and Reply pattern, and then make a real-time Apex callout to the ESB endpoint to fetch3 and display historical Data in a custom Lightning compo4nent related to the Case object.
正解：A
解説：
When designing a solution to view large volumes of archived data (over 20 million records) without physically storing them back in Salesforce, a Data Virtualization pattern is the architecturally preferred approach. This pattern allows users to view and interact with external data in real-time without the overhead of data replication, which would otherwise consume significant storage and impact platform performance.
To maximize declarative configuration, the Salesforce Platform Integration Architect should recommend Salesforce Connect. Salesforce Connect allows for the creation of External Objects, which behave much like standard objects but point to data residing outside of Salesforce. This is achieved by having the middleware (ESB) expose the Historical Data store via an OData (Open Data Protocol) endpoint. Once configured, call center agents can view historical case items directly on the Case record page using standard related lists or lookups, all configured through the point-and-click interface rather than custom code.
The provided landscape diagram illustrates a clear path from Salesforce through middleware to the Historical Data Store. Option A leverages this by using the ESB to bridge the protocol gap. Because the data store is already "fine-tuned to be performant with search queries," Salesforce Connect can efficiently query only the specific historical records needed for the current case view.
In contrast, Option B requires a "Request and Reply" pattern using Apex callouts and custom Lightning components. While functional, this is a code-heavy approach that increases technical debt and does not meet the "maximize declarative configuration" requirement. Option C, using "Fire and Forget" with Platform Events, is unsuitable for a synchronous "view data" request; Platform Events are asynchronous and would require a complex, custom-built UI to "wait" for and display the response. Therefore, the combination of OData and Salesforce Connect provides the most seamless, scalable, and low-maintenance solution for call center agents.
質問 # 44
A business requires automating the check and updating of the phone number type classification for all incoming calls. Up to 100,000 calls per day are received, and the business is flexible with timing (every 6-12 hours is sufficient). A Remote-Call-In and/or Batch Synchronization pattern via middleware is planned. Which component should an integration architect recommend to implement these patterns?
- A. An API Gateway that authenticates requests from Salesforce into the middleware (ETL/ESB)
- B. Remote Site Settings configured in Salesforce to authenticate the middleware
- C. Connected App configured in Salesforce to authenticate the middleware
正解：C
解説：
In a Remote-Call-In or Batch Synchronization pattern where an external middleware initiates the connection to Salesforce, the external system must be authenticated. The standard Salesforce framework for this is the Connected App.
A Connected App provides a framework for external applications to integrate with Salesforce using APIs and standard protocols like OAuth 2.0. For a high-volume (100,000 records) batch process initiated by middleware every 6-12 hours, the architect would recommend a Connected App using a secure flow, such as the OAuth 2.0 JWT Bearer Flow. This allows the middleware to authenticate as a specific "Integration User" without storing clear-text passwords.
Option A (API Gateway) is used to manage and secure outbound calls from Salesforce or between external services; it does not handle inbound authentication to the Salesforce org itself. Option B (Remote Site Settings) is a whitelist configuration used purely to allow Salesforce to make outbound callouts to a specific URL; it provides no authentication mechanism for systems calling into Salesforce. By recommending a Connected App, the architect ensures that the middleware has the necessary permissions (scopes) to use the Bulk API-which is the appropriate mechanism for the 100,000 record volume-while maintaining a secure, auditable, and standard integration boundary.
質問 # 45
Universal Containers (UC) is a leading provider of management training globally. UC embarked on a Salesforce transformation journey to allow students to register for courses in the Salesforce Community. UC has a learning system that masters all courses and student registration. UC requested a near real-time feed of student registration from Salesforce to the learning system. The integration architect recommends using Salesforce Platform Events. Which API should be used for the Salesforce pl1atform event solution?
- A. REST API
- B. SOAP API
- C. Streaming API
正解：C
解説：
Salesforc30e Platform Events are built on top of a highly scalable, event-driven messaging architecture designed to enable real-time communication between apps. To consume these events from outside Salesforce-such as from a legacy learning system-clients must use the Streaming API.
The Streaming API is the technical foundation for receiving event notifications in a Publish/Subscribe model. It utilizes the CometD protocol or the newer gRPC-based Pub/Sub API to maintain a persistent connection between the external client and Salesforce. When a student registers for a course in the Salesforce Community, a Platform Event is "published" to the event bus. The learning system, acting as a "subscriber," remains connected via the Streaming API and receives the event message instantly without needing to poll Salesforce for updates.
This architecture is ideal for "near real-time" requirements because it eliminates the overhead of traditional point-to-point integrations. While the REST and SOAP APIs (Options A and B) can be used to publish events into Salesforce, they are not designed to receive unsolicited notifications from the platform. By using the Streaming API, the integration architect ensures the solution is both responsive and efficient, as Salesforce only pushes data when a relevant event occurs. Furthermore, because Platform Events provide a retention window, the Streaming API allows the learning system to use a Replay ID to catch up on any registration events missed during a brief network outage.
質問 # 46
......
Salesforce Plat-Arch-204 認定試験の出題範囲：
| トピック | 出題範囲 |
|---|---|
| トピック 1 |
|
| トピック 2 |
|
| トピック 3 |
|
結果を保証するには2026年05月最新の無料版提供しています：https://www.passtest.jp/Salesforce/Plat-Arch-204-shiken.html
正真正銘のPlat-Arch-204問題集で無料PDF問題で合格させる：https://drive.google.com/open?id=1uy2TTbI90LSEdXG_4lCujbdT5Esj_EG1