Free Access to Salesforce.Integration-Architect.v2026-08-26.q122 with Valid Practice Test (Page 6)

Question 21

business requires automating the check and update of the phone number type classification (mobile vs. landline) for all in-coming calls delivered to their phone sales agents. The following conditions exist:
1. At peak, their call center can receive up to100,000 calls per day.
2. The phone number type classification is a service provided by an external serviceAPI.
3. Business is flexible with timing and frequency to check and update the records (throughout the night or every 6-12 hours is sufficient).
ARemote-Call-In pattern and/or Batch Synchronization (Replication via ETL: System -> Salesforce) are determinedto work with a middleware hosted on custom premise.
In order to implement these patterns and mechanisms, which component should an integration architect recommend?

A.ConnectedApp configured in Salesforce to authenticate the middleware.
B.IoConfigure Remote Site Settings in Salesforce to authenticate the middleware.
C.An API Gateway that authenticates requests from Salesforce into the Middleware (ETL/ESB).
D.Firewall and reverse proxy are required to protect internal APIs and resource being exposed.

Question 22

Northern Trail Outfitters needs to secure an integration with an external Microsoft Azure API Gateway.
What integration security mechanism should be employed?

A.Configure mutual server authentication with two-way SSL using CA issued certificates.
B.Configure a connected app with an authorization endpoint of the API gateway and configure OAuth settings.
C.Use an API only user profile and implement use an external identity provider with federated API access.
D.Implement Salesforce Shield with Encryption at Rest and generate a tenant secret.

Question 23

Northern Trail Outfitters uses a custom Java application to display code coverage and test results for all of their enterprise applications and is planning to include Salesforce as well.
Which Salesforce API should an Integration Architect use to meet the requirement?

A.SOAP API
B.Analytics REST API
C.Metadata API
D.Tooling API

Question 24

A company accepts payment requests 24x7. Once they accept a payment request, their service level agreement (SLA) requires them to make sure each payment request is processed by their Payment System. They track payment requests using a globally unique identifier created at the Data Entry Point. Their simplified flow is as shown in the diagram.
They encounter intermittent update errors when two or more processes try to update the same Payment Request record at the same time.
Which two recommendations should an integration architect make to improve their SLA and update conflict handling?
Choose 2 answers

A.Payment System should process a payment request only once.
B.Data Entry Point and Middleware should automatically retry requests.
C.Middleware should coordinate request delivery and payment processing.
D.Payment System and Middleware should automatically retry requests.

Question 25

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 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.
C.Use an ESB tool with a Fire and Forget pattern, and then publish a platform event for the requested historical data.

Correct Answer: 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.

Question 21

Question 22

Question 23

Question 24

Question 25

Download PDF File