Get 2026 Free Salesforce Integration-Architect Exam Practice Materials Collection [Q30-Q54]

Get 2026 Free Salesforce Integration-Architect Exam Practice Materials Collection

Get Latest and 100% Accurate Integration-Architect Exam Questions

Salesforce Integration-Architect Certification Exam is a proctored exam that consists of 60 multiple-choice questions. Integration-Architect exam duration is 120 minutes, and candidates must score at least 67% to pass the exam. Integration-Architect exam fee is $400, and candidates can take the exam at a proctored testing center or online.

 

NEW QUESTION # 30
Northern Trail Outfitters is in the final stages of merging two Salesforce orgs but needs to keep the retiring org available for a short period of time for lead management as it is connected to multiple public web site forms.
The sales department has requested that new leads are available in the new Salesforce instance within 30 minutes.
Which two approaches will require the least amount of development effort?
Choose 2 answers

• A. Call the Salesforce REST API to insert the lead into the target system.
• B. Use the Composite REST API to aggregate multiple leads in a single call.
• C. Use the tooling API with Process Builder to insert leads in real time.
• D. Configure named credentials in the source org.

Answer: B,D

Explanation:
The two approaches that will require the least amount of development effort are configuring named credentials in the source org and using the Composite REST API to aggregate multiple leads in a single call.
Named credentials are a type of metadata that store authentication information for accessing external services, such as the target Salesforce org. By using named credentials, you can simplify the code for making callouts and avoid hardcoding credentials or tokens.
The Composite REST API is a resource that allows you to execute multiple REST API requests in a single call.
You can use the Composite REST API to create, update, or delete up to 25 records in one request.
This can reduce the number of API calls and improve performance.
References: [Named Credentials], [Composite Resources]

NEW QUESTION # 31
Northern Trail Outfitters' ERP is integrated with Salesforce and syncs several million contacts per day. To prevent specific data from syncing, the integration uses a SOQL query filtered by sharing hierarchy.
Which two things should an architect do to improve the performance of the integration?
Choose 2 answers

• A. Include selective criteria in query filters.
• B. Include non-selective criteria in query filters.
• C. Remove the sharing restrictions.
• D. Remove the query filters.

Answer: A,C

Explanation:
Explanation
Option C is correct because including selective criteria in query filters can improve the performance of the integration. Selective criteria are filters that reduce the number of records that need to be scanned by the query optimizer, such as indexed fields, standard indexes, or custom indexes. Selective criteria can help the query run faster and avoid hitting the query timeout limit or the query row limit.
Option D is correct because removing the sharing restrictions can improve the performance of the integration. Sharing restrictions are filters that limit the access to records based on the user's role, profile, or sharing rules. Sharing restrictions can add complexity and overhead to the query execution, as they require additional joins and calculations. Removing the sharing restrictions can simplify the query and reduce the number of records that need to be processed.
Option A is incorrect because including non-selective criteria in query filters can degrade the performance of the integration. Non-selective criteria are filters that do not reduce the number of records that need to be scanned by the query optimizer, such as non-indexed fields, formula fields, or OR conditions. Non-selective criteria can cause the query to run slower and hit the query timeout limit or the query row limit.
Option B is incorrect because removing the query filters can degrade the performance of the integration.
Query filters are conditions that specify which records to retrieve from the database, such as WHERE clauses or LIMIT clauses. Query filters can help the query run faster and avoid retrieving unnecessary or unwanted data. Removing the query filters can increase the number of records that need to be processed and transmitted by the integration.
References: Working with Very Large SOQL Queries: Improve performance with custom indexes using Salesforce Query Plan tool: Querying Data That Respects User Permissions: How does sharing affect SOQL performance?: SOQL SELECT Syntax : SOQL Best Practices

NEW QUESTION # 32
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.

Answer: A

Explanation:
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.

NEW QUESTION # 33
A company is planning on sending orders from Salesforce to a fulfillment system. The integration architect has been asked to plan for the integration.
Which two questions should the integration architect consider?
Choose 2 answers

• A. Can the fulfillment system make a callback into Salesforce?
• B. Can the fulfillment system implement a contract-first Outbound Messaging interface?
• C. Can the fulfillment system create new addresses within the Order Create service?
• D. Is the product catalog data identical at all times in both systems?

Answer: A,B

Explanation:
Explanation
The integration architect should consider whether the fulfillment system can make a callback into Salesforce and whether it can implement a contract-first Outbound Messaging interface. A callback is a way for the fulfillment system to send a response or an acknowledgment back to Salesforce after receiving an order1. This can help ensure data consistency and reliability between the two systems. A contract-first Outbound Messaging interface is an approach where the integration is designed based on a predefined XML schema that defines the structure and content of the messages2. This can help ensure interoperability and compatibility between the two systems. The other two questions are not relevant for the integration architect to consider. The fulfillment system does not need to create new addresses within the Order Create service, as this is a function of Salesforce3. The product catalog data does not need to be identical at all times in both systems, as long as there is a mapping or synchronization mechanism to handle any discrepancies

NEW QUESTION # 34
Which WSDL should an architect consider when creating an integration that might be used for more than one salesforce organization and different metadata?

• A. SOAP API WSDL
• B. Corporate WSDL
• C. Enterprise WSDL
• D. Partner WSDL

Answer: D

Explanation:
Explanation
The Partner WSDL is the best option for creating an integration that might be used for more than one Salesforce organization and different metadata. The Partner WSDL is loosely typed and can reflect against any configuration of Salesforce. It is static and does not change if modifications are made to an organization's Salesforce configuration. Therefore, it is more flexible and adaptable than the Enterprise WSDL, which is strongly typed and bound to a specific configuration of Salesforce1 References: Differences between Salesforce provided WSDL files

NEW QUESTION # 35
KiA B2C Enterprise Customer has the following use case that involves processing payment from an external payment gateway service in Salesforce.
1. Customer requests Customer Service Representative (CSR) for a Service upgrade.
2. Customer provides credit card details to CSR for payment.
3. CSR submits payment information in Salesforce, and processed in a
4. CSR receives confirmation of payment.
5. CSR upgrades service for customer and confirms Customer.
external payment gateway.
This use case requires the CSR to obtain confirmation of payment before upgrading the service.
The integration with Payment gateway needs to be reliable and monitored for audit purposes.
The payment gateway service is an external RESTful service that the B2C Enterprise Customer has subscribed for.
What should an Integration Architect recommend for this integration?

• A. Make a callout to the payment gateway through ESB supporting error handling andlogging for audit purposes.
• B. Use External Services feature to integrate gateway to Salesforce ensuring real-timeupdates the CSR and support post payment processes.
• C. Platform events allow integration to payment gateway through the exchange ofreal-time event data, platform events are scalable and secure.
• D. Build a custom Apex Callout to external Payment gateway service and provide success message to the CSR, the details of calloutsand responses are logged for audit purposes.

Answer: A

NEW QUESTION # 36
A customer's enterprise architect has identified requirements around caching, queuing, error handling, alerts, retries, event handling, etc. The company has asked the Salesforce integration architect to help fulfill such aspects with their Salesforce program.
Which three recommendations should the Salesforce integration architect make?
Choose 3 answers

• A. Event handling in a publish/subscribe scenario, the middleware can be used to route requests or messages to active data-event subscribers from active data-event publishers.
• B. Provide true message queueing for integration scenarios (including orchestration, process choreography, quality of service, etc.) given that a middleware solution is required.
• C. Transform a fire-and-forget mechanism to request-reply should be handled by middleware tools (like ETL/ESB) to improve performance.
• D. Event handling processes such as writing to a log, sending an error or recovery process, or sending an extra message, can be assumed to be handled by middleware.
• E. Message transformation and protocol translation should be done within Salesforce.Recommend leveraging Salesforce native protocol conversion capabilities as middleware tools are NOT suited for such tasks

Answer: A,B,D

Explanation:
The recommendations that the Salesforce integration architect should make to fulfill the requirements around caching, queuing, error handling, alerts, retries, event handling, etc. arebased on the best practices and capabilities of the middleware tools. The recommendation B is valid because middleware tools can provide true message queueing for integration scenarios that require asynchronous processing, guaranteed delivery, load balancing, etc. The recommendation D is valid because middleware tools can handle various events that may occur during the integration process, such as logging errors, sending notifications, triggering recovery actions, etc. The recommendation E is valid becausemiddleware tools can support the publish/subscribe pattern for event-driven integration, where the middleware can route messages from publishers to subscribers based on topics or filters. The recommendation A is not valid because transforming a fire-and-forget mechanism to request-reply does not improve performance, but rather increases the latency and complexity of the integration. The recommendation C is not valid because message transformation and protocol translation are tasks that are better suited for middleware tools than Salesforce, as they can handle different formats and protocols more efficiently and flexibly23
1: Integration Architecture Designer Resource Guide 2: Integration Patterns and Practices 3: Salesforce Integration Architecture Designer Certification Exam Guide

NEW QUESTION # 37
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 Outbound Messaging to automatically retry failed service calls.
• B. Use middleware queuing and buffering to insulate Salesforce from system outages.
• C. Use Platform Event replayId and custom scheduled Apex process to retrieve missed events.

Answer: B

Explanation:
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.

NEW QUESTION # 38
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. Store shipping services in a picklist that is dependent on a country picklist.
• B. Invoke middleware service to retrieve valid shipping methods.
• C. Use Platform Events to construct and publish shipper-specific events.

Answer: B

Explanation:
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.

NEW QUESTION # 39
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 service API.
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 determined to 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. Firewall and reverse proxy are required to protect internal APIs and resource being exposed.
• C. IoConfigure Remote Site Settings in Salesforce to authenticate the middleware.
• D. An API Gateway that authenticates requests from Salesforce into the Middleware (ETL/ESB).

Answer: A

Explanation:
Explanation
A Connected App is a framework that enables an external application to integrate with Salesforce using APIs and standard protocols, such as OAuth. By configuring a Connected App in Salesforce, the integration can authenticate the middleware and grant access to the Salesforce data and services. This is a secure and flexible solution that does not require configuring Remote Site Settings, API Gateway, or Firewall and reverse proxy2 References: 1: BatchApexErrorEvent 2: Connected Apps

NEW QUESTION # 40
When user clicks Check Preferences as part of a Lightning flow in Salesforce, preferences from an externally hosted RESTful service are to be checked in real-time. The RESTful service has OpenAPI 2.0 JSON definitions, responding in data types of Boolean and string values.
Which integration pattern and mechanism should be selected to meet the conditions?

• A. Remote Call-In: Salesforce REST API with REST Composite Resources.
• B. Fire and Forget: Process-driven platform events publishes events on Salesforce Event Bus.
• C. Data Virtualization: Salesforce Connect map data external REST data in external objects.
• D. Request-Reply: Enhanced External Services invokes a REST API.

Answer: D

NEW QUESTION # 41
A call center manager uses a custom dashboard to track Case related metrics. The manager wants a component to display the number of closed Cases in real time.
What type of event should be used to meet this requirement?

• A. Platform Event
• B. Change Data Capture Event
• C. Generic Event
• D. Push Topic Event

Answer: B

Explanation:
Explanation
Change Data Capture Event is the best option to meet this requirement. Change Data Capture Event is a type of streaming event that notifies subscribers of changes to Salesforce records, such as creation, update, delete, and undelete operations1. By subscribing to Change Data Capture Event for the Case object, the dashboard component can receive real-time updates on the number of closed Cases. Push Topic Event is another type of streaming event that notifies subscribers of changes to Salesforce records that match a SOQL query2. However, Push Topic Event has some limitations, such as not supporting all SOQL features and not capturing delete and undelete operations3. Platform Event is a type of streaming event that delivers custom notifications within the Salesforce platform or from external sources4. Platform Event is not suitable for this requirement because it is not tied to Salesforce records and requires custom logic to publish and subscribe. Generic Event is a type of streaming event that sends custom JSON notifications to subscribers without a predefined schema5. Generic Event is not suitable for this requirement because it is not tied to Salesforce records and requires custom logic to publish and subscribe.

NEW QUESTION # 42
Northern Trail Outfitters (NTO) has an integration set up between a Salesforce org and a quoting system.
NTO would like to show a notification to allsales representatives that use Salesforceanytime the quoting system will be taken down for maintenance.
Which Salesforce API should an Integration Architect use to fulfill this requirement?

• A. Streaming API
• B. Connect REST API
• C. Tooling API
• D. REST API

Answer: A

Explanation:
Streaming API is the best option for sending real-time notifications of changes to Salesforce data. Streaming API uses a publish-subscribe model to push relevant data to subscribers without polling. Streaming API supports PushTopic events, whichare based on SOQL queries that define the data changes to listen for. The affiliate company can subscribe to a PushTopic event on the NTO Salesforce org and receive notifications whenever the data that matches the query changes. This way, the affiliate company can be informed of any updates to the opportunities in the NTO Salesforce instance.

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

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

Answer: A

Explanation:
Option D is correct because Tooling API is the Salesforce API that can be used to retrieve code coverage and test results for Apex classes and triggers. Tooling API provides REST and SOAP interfaces to access metadata about code, execute tests, and get test results12 Option A is incorrect because SOAP API is a Salesforce API that can be used to create, retrieve, update, or delete records, but not to get code coverage and test results. SOAP API uses a WSDL file to define the parameters for accessing data through the API3 Option B is incorrect because Analytics REST API is a Salesforce API that can be used to access data from reports and dashboards, but not from code coverage and test results. Analytics RESTAPI provides a programmatic way to interact with analyticsfeatures such as lenses, datasets, and dashboards4 Option C is incorrect because Metadata API is a Salesforce API that can be used to retrieve, deploy, create, update, or delete customization information, such as custom object definitions and page layouts, but not code coverage and test results. Metadata API is mainlyused for development tools or backup tools5 References: 1: Introducing Tooling API 2: Tooling API Examples 3: SOAP API Developer Guide 4:
Analytics REST API Developer Guide 5: Metadata API Developer Guide

NEW QUESTION # 44
Universal Containers (UC) uses Salesforce to track the following customer data:
1. Leads,
2. Contacts
3. Accounts
4. Cases
Salesforce is considered to be the system of record for the customer. In addition to Salesforce, customer data exists in anEnterprise Resource Planning (ERP) system, ticketing system, and enterprise data lake. Each of these additional systems have their own unique identifier. UC plans on using middleware to integrate Salesforce with the external systems.
UC has a requirementto update the proper external system with record changes in Salesforce and vice versa.
Which two solutions should an Integration Architect recommend to handle this requirement?
Choose 2answers

• A. Locally cache external ID'S at the middleware layer and design business logic to map updates between systems.
• B. Design an MDM solution that maps external ID's to the Salesforce record ID.
• C. Store unique identifiers in an External ID field in Salesforce and use this to update the proper records across systems.
• D. Use Change Data Capture to update downstream systems accordingly when a recordchanges.

Answer: B,D

Explanation:
Using Change Data Capture (CDC) to update downstream systems accordingly when a record changes is a solution that can handle this requirement by capturingdata changes in Salesforce and sending them to external systems via a publish-subscribe model. This way, the external systems can receive near real-time updates from Salesforce and synchronize their data accordingly. Designing an MDM solution that maps external ID's to the Salesforce record ID is a solution that can handle this requirement by creating a master data hub that stores and manages the unique identifiers of each system and their relationships. This way, the MDM solution can ensuredata quality,consistency, and accuracy across systems. Locally caching external ID's at the middleware layer and designing business logic to map updates between systems is not a good solution because it can introduce performance and scalability issues, as well as increase the complexity and maintenance cost of the middleware layer. Storing unique identifiers in an External ID field in Salesforce and using this to update the proper records across systems is not enough to handle this requirement, as it does not address how to update Salesforce with record changes from external systems. Reference: Salesforce Integration Architecture Designer Resource Guide, page 27-28

NEW QUESTION # 45
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. Process Orchestration
• C. Data Virtualization

Answer: C

Explanation:
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.

NEW QUESTION # 46
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. OpenId Connect Authentication Provider and JIT provisioning
• B. SAML SSO and Registration Handler
• C. SAML SSO and Just-in-Time (JIT) provisioning

Answer: A

NEW QUESTION # 47
Northern Trail Outfitters (NTO) use Salesforce to track leads, 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 orders life cylce. The Integration Architect for the project is recommending a remote system that will subscribe to the platform event defined in Salesforce.
Which integration pattern shouldbe used for this business use case?

• A. Request and Reply
• B. Fire and Forget
• C. Batch Data Synchronization
• D. Remote Call In

Answer: B

Explanation:
The Fire and Forget pattern is suitable for this business use case because it allows sending a message from Salesforceto the remote system without waiting for a response or acknowledgement. This reduces the latency and complexity of the integration and enables asynchronous processing of the orders in the remote system. The platform event defined in Salesforce can be used to publish the order details to the remote system, which can subscribe to the event and create the order accordingly1

NEW QUESTION # 48
Northern Trail Outfitters (NTO) is looking to integrate three external systems that run nightly data enrichment processes in Salesforce. NTO has both of the following security and strict auditing requirements:
1. The external systems must follow the principle of least privilege, and
2. The activities of the eternal systems must be available for audit.
What should an Integration Architect recommend as a solution for these integrations?

• A. A shared integration user for the three external system integrations.
• B. A Connected App for each external system integration.
• C. A unique integration user for each external system integration.
• D. A shared Connected App for the three external system integrations.

Answer: B

NEW QUESTION # 49
An integration architect has received a request to prevent employees that leave the company from accessing data in Salesforce after they are deactivated in the company's HR system. What should the integration architect determine before recommending a solution?

• A. Data access prevention requirements, then identify frequency
• B. Data access prevention requirements, integration requirements, and system constraints
• C. Inbound integration requirements, then identify frequency

Answer: C

NEW QUESTION # 50
The goals for implementing Salesforce include a 360-degree view, leveraging CRM for marketing, sales, and service, and reusing enterprise quoting/order management. Which three systems from the current landscape can be retired?

• A. Sales Activity, Order Management, and Case Management
• B. Email Marketing, Sales Activity, and Case Management
• C. Order Management, Case Management, and Email Marketing

Answer: B

Explanation:
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.

NEW QUESTION # 51
Which two approaches will require the least amount of development effort?
Choose 2 answers

• A. Call the Salesforce REST API to insert the lead into the target system.
• B. Use the Composite REST API to aggregate multiple leads in a single call.
• C. Use the tooling API with Process Builder to insert leads in real time.
• D. Configure named credentials inthe source org.

Answer: B,D

Explanation:
The two approaches that will require the least amount of development effort are configuring named credentials in the source org and using the Composite REST API to aggregate multiple leads in a single call.
Named credentials are a type of metadata that store authentication information for accessing external services, such as the target Salesforce org. By using named credentials, you can simplify the code for making callouts and avoid hardcoding credentials or tokens. The Composite REST API is a resource that allows you to execute multiple REST API requests in a single call. You can use the Composite REST API to create, update, or delete up to 25 records in one request. This can reduce the number of API calls and improve performance.
References: [Named Credentials], [Composite Resources]

NEW QUESTION # 52
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?

• A. 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.
• B. Both Platform Events and Outbound Messaging offer declarative means for asynchronous near-real time needs. They aren't best suited for real-time integrations.
• C. In both Platform Events and Outbound Messaging, the event messages are retried by and delivered in sequence, and only once. Salesforce ensures there is no duplicate message delivery.

Answer: B

NEW QUESTION # 53
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. Use Salesforce Files to link the files to Salesforce records and display the record and the files in the community.
• B. 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.
• C. Create a Lightning component with a Request and Reply integration pattern to allow the community users to download the design files.

Answer: B

Explanation:
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.

NEW QUESTION # 54
......

Maximum Grades By Making ready With Integration-Architect Dumps: https://pass4sure.dumps4pdf.com/Integration-Architect-valid-braindumps.html