Latest Integration-Architect Actual Free Exam Updated 130 Questions [Q35-Q59] | DumpsMaterials

Latest Integration-Architect Actual Free Exam Updated 130 Questions [Q35-Q59]

Share

Latest Integration-Architect Actual Free Exam Updated 130 Questions

Online Questions - Valid Practice Integration-Architect Exam Dumps Test Questions

NEW QUESTION # 35
Northern Trail Outfitters has a registration system that is used for workshopsoffered at its conferences.
Attendees use a Salesforce community to register for workshops, but the scheduling systemmanages workshop availability based on room capacity. It is expected that there will be a big surge of requests for workshop reservationswhen the conference schedule goes live.
Which integration pattern should be used to manage the influx in registrations?

  • A. RemoteCall-In
  • B. Remote Process Invocation-Fire and Forget
  • C. Batch Data Synchronization
  • D. Remote Process Invocation-Request and Reply

Answer: C

Explanation:
The Batch Data Synchronization pattern is suitable for this business use case because it allows transferring large volumes of data between Salesforce and the scheduling system in batches. This can handle the surge of requests for workshop registrations without overloading the systems or affecting the performance. The batch process can run at regular intervals or on demand to synchronize the data between the systems1
1: Batch Data Synchronization Pattern


NEW QUESTION # 36
A company's security assessment noted vulnerabilities on the un managed packages in their Salesforce orgs, notably secrets that are easily accessible and in plain text, such as usernames, passwords, and OAuth tokens used in callouts from Salesforce.
Which two persistence mechanisms should an integration architect require to be used to ensure that secrets are protected from deliberate or inadvertent exposure?
Choose 2 answers

  • A. Encrypted Custom Fields
  • B. Named Credentials
  • C. Protected Custom Settings
  • D. Protected Custom Metadata Types

Answer: B,C

Explanation:
Explanation
Named Credentials and Protected Custom Settings are two persistence mechanisms that can be used to ensure that secrets are protected from deliberate or inadvertent exposure. Named Credentials allow you to specify the URL of a callout endpoint and its required authentication parameters in one definition. Salesforce manages all the authentication for Apex callouts that specify a named credential as the callout endpoint, and you don't have to add more authentication logic in your Apex code. Named Credentials can be defined to provide a secure and convenient way of setting up authenticated callouts, and they can also be used in Lightning components, Visualforce pages, and flows1.
Protected Custom Settings are a type of custom settings that store application-specific data that is hidden from subscribers. They are only accessible by the managed package that created them, and they can be used to store secrets such as encryption keys, passwords, or tokens. Protected Custom Settings can be accessed by Apex code, formulas, or validation rules within the same namespace as the settings2.
Encrypted Custom Fields are not a suitable mechanism for storing secrets, because they are not designed to prevent unauthorized access to sensitive data. Encrypted Custom Fields allow you to encrypt text fields using a standard encryption scheme. The encrypted data is masked in reports, list views, and search results, but it can still be viewed by users who have the "View Encrypted Data" permission. Encrypted Custom Fields are intended to protect data from unauthorized access by users within your organization, not from external threats or malicious code3.
Protected Custom Metadata Types are another type of custom metadata types that store application-specific data that is hidden from subscribers. They are similar to Protected Custom Settings, but they have some advantages such as being deployable using change sets or Metadata API, being accessible by SOQL queries, and being able to reference other metadata types or settings. However, Protected Custom Metadata Types cannot be used to store secrets, because they do not support encryption or masking of sensitive data. Protected Custom Metadata Types are intended to store configuration data that is specific to your managed package, not secrets that need to be secured.
Therefore, the correct answer is B and D, because Named Credentials and Protected Custom Settings are the only persistence mechanisms that can be used to securely store secrets in Salesforce.
References: 1: Named Credentials | Apex Developer Guide | Salesforce Developers 2: Custom Settings | Apex Developer Guide | Salesforce Developers 3: Encrypted Fields | Salesforce Help : [Protected Custom Metadata Types | ISVforce Guide | Salesforce Developers]


NEW QUESTION # 37
A large consumer goods manufacturer operating in multiple countries is planning to implement Salesforce for its sales and support operations globally. The Manufacturer has the following security requirements:
* Internal users from each country have to be authenticated with their local active directory.
* Customers can create their own login or use Google login.
* Partners have to be authenticated through a central system which is to be determined.
* Internal users will have access to the central Enterprise Resource Planning (ERP) with their credentials maintained in the ERP system.
* Additional internal systems will be integrated with Salesforce for sales and support business processes.
Which requirement should the integration architect evaluate while designing the integration needs of this project?

  • A. Consider a third-party single sign-on (SSO) solution supporting all user authentication including customer and partner.
  • B. Evaluate the build of a custom authentication mechanism for users in each country and support for customers and partners.
  • C. Evaluate Salesforce native authentication mechanism for all users including customers and partners.

Answer: A

Explanation:
Managing identity across a global enterprise with diverse user personas (Employees, Customers, Partners) requires a centralized Identity and Access Management (IAM) strategy. In a landscape involving multiple local Active Directories, social logins (Google), and a central ERP system, attempting to manage authentication natively within Salesforce or through custom-built local silos would result in high technical debt and security vulnerabilities.
The architect should recommend a third-party Single Sign-On (SSO) solution, acting as a central Identity Provider (IdP). This IdP serves as the orchestration layer for all authentication requests.
* For Internal Users: The IdP can federate with the various local Active Directories, allowing users to log in with their existing corporate credentials.
* For Customers: The IdP can handle "Social Sign-On" (OpenID Connect) with Google and manage self-registration.
* For Partners: It provides the "central system" required for their authentication.
By using a central SSO solution, Salesforce acts as a Service Provider (SP). When a user attempts to access Salesforce, the request is redirected to the IdP via the SAML 2.0 or OpenID Connect protocol. Once the IdP validates the user against the appropriate backend (AD, Google, or its own directory), it sends a secure assertion back to Salesforce to grant access.
Furthermore, this central IdP can facilitate access to the ERP system and other internal systems. If these systems support SAML, the same SSO session used for Salesforce can be extended to them, providing a true single sign-on experience. This architecture centralizes security auditing, simplifies user de-provisioning (the
"kill switch" effect), and ensures a consistent user experience across the global manufacturing landscape.
Implementing a thir2d-party IdP is the industry-standard approach for complex integrations where security, scalabi3lity, and multi-protocol support are primary requirements.


NEW QUESTION # 38
A global financial company sells financial products and services that include the following:
1. Bank Accounts
2. Loans
3. Insurance
The company has a core banking system that is state of the art and is the master system to store financial transactions, financial products and customer information. The core banking system currently processes 10M financial transactions per day. The CTO for the company is considering building a community port so that customers can review their bank account details, update their information and review their account financial transactions.
What should an integration architect recommend as a solution to enable customer community users to view their financial transactions?

  • A. Use Salesforce Connect to display the financial transactions as an external object.
  • B. Use Iframe to display core banking financial transactions data in the customer community.
  • C. Use Salesforce External Service to display financial transactions in a community lightning page.
  • D. Use Salesforce Connect to display the financial transactions as an external object.

Answer: C


NEW QUESTION # 39
An architect decided to use Platform Events for integrating Salesforce with an external system for a company.
What should an architect consider when proposing this type of integration mechanism?

  • A. To subscribe to an event, the integration user in Salesforce needs Read access to the event entity.
  • B. Salesforce needs to be able to store information about the external system in order to know which event to send out.
  • C. External system needs to have the same uptime in order to be able to keep up with Salesforce Platform Events.

Answer: A

Explanation:
When proposing Platform Events as an integration mechanism, an architect must ensure that the security model is correctly configured to allow for the publication and subscription of events. Unlike standard objects, Platform Events have specific permission requirements for the "Integration User" or any system entity interacting with the event bus.
For an external system to subscribe to a Platform Event stream (via CometD or the Pub/Sub API), the user account used to authenticate the connection must have the "Read" permission on the specific Platform Event entity. Similarly, if the external system needs to publish events back into Salesforce, the user must have " Create" permissions. These permissions are typically managed through a Profile or a Permission Set assigned to the Integration User.
Regarding the other options, Option A is incorrect because Platform Events are designed for asynchronous communication. They are inherently decoupled; the external system does not need the same uptime as Salesforce. High-volume platform events are stored in the event bus for 72 hours, allowing an external system to "catch up" using a Replay ID once it comes back online. Option C is also incorrect because Platform Events follow a Publish/Subscribe pattern. Salesforce "broadcasts" the event to the bus without needing to know which specific external systems are listening. This decoupling is a primary advantage of event-driven architecture, as it allows for a "one-to-many" distribution model where multiple systems can consume the same message without additional configuration within Salesforce. Thus, ensuring the correct object-level permissions (Read/Create) is the most critical technical consideration for the architect to guarantee successful message delivery.


NEW QUESTION # 40
Salesforce users need to read data from an external system via HTTPS request.
Which two security methods should an integration architect leverage within Salesforce to secure the integration?
Choose 2 answers

  • A. Connected App
  • B. Named Credentials
  • C. Authorization Provider
  • D. Two-way SSL

Answer: B,D

Explanation:
Named Credentials and Two way SSL are two security methods that an integration architect can leverage within Salesforce to secure the integration with an external system via HTTPS request. Named Credentials are a type of metadata that store authentication settings for accessing external services. They allow you to specify the URL of a service,the authentication protocol, and the credentials for accessing the service. Two way SSL is a type ofmutual authentication that requires both the client and the server to present their certificates to each other. This ensures that both parties are who theyclaim to be, and that the communication is encrypted. Two way SSL can be configured in Salesforce by uploading a certificate and a private key, and associating them with a named credential. References: Certification - Integration Architect - Trailhead, [Named Credentials],
[Mutual Authentication]


NEW QUESTION # 41
Universal Containers (UC) is a global financial company. UC support agents would like to open bank accounts on the spot for a customer who is inquiring ab UC products.
During opening the bank account process, the agents execute credit checks for the customers through external agencies. At a given time, up to 30 concurrent rewill be using the service for performing credit checks for customers.
What error handling mechanisms should be built to display an error to the agent when the credit verification process failed?

  • A. In case the verification process is down, Use mock service to send the response to the agent.
  • B. Handle integration errors in the middleware in case the verification process is down, then the middleware should retry processing the request multiple times.
  • C. In case the verification process is down, use fire and forget mechanism instead of request and reply to allow the agent to get the response back when the service is bar online.
  • D. Handle verification process error in the Verification Webservice API in case there isa connection issue to the Webservice if it responds with an error.

Answer: D

Explanation:
Handle verification process error in the Verification Webservice API in case there is a connection issue to the Webservice or if it responds with an error. This solution ensures that the agent can see an error message when the credit verification process failed, and take appropriate actions. The Verification Webservice API can implementerror handling logic to catch anyexceptions or errors that occur during the callout to the external agencies, and return a meaningful error message to the agent. The agent can then retry the verification process, or escalate the issue to a supervisor. References: Certification - Integration Architect - Trailhead,
[Apex Web Services and Callouts]


NEW QUESTION # 42
An Integration Architect has designed a mobile application for Salesforce users to get data while on the road using a custom 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 it 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 done to meet the requirement?

  • A. The mobile device makes a SOAP API inbound call.
    The mobile device receives a REST Apex callout call.
  • B. The mobile device makes a REST Apex inbound call.
  • C. The mobile device makes a REST API inbound call.

Answer: C


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

Answer: A,C

Explanation:
Explanation
Middleware should coordinate request delivery and payment processing, and Payment System should process a payment request only once. This solution ensures that each payment request is delivered to the Payment System in a reliable and consistent manner, and avoids duplicate or conflicting updates to the same Payment Request record. Middleware can act as a mediator between the Data Entry Point and the Payment System, and implement logic to handle errors, retries, and acknowledgments. Payment System can use the globally unique identifier to check if a payment request has already been processed, and avoid processing it again.
References: Certification - Integration Architect - Trailhead, [Integration Patterns and Practices]


NEW QUESTION # 44
Northern Trail Outfitters is planning to create a native employee facing mobile app with the look and feel of Salesforce's Lighting Experience. The mobile ap needs to integrate with their Salesforce org.
Which Salesforce API should be used to implement this integration?

  • A. Connect REST API
  • B. Streaming API
  • C. REST API
  • D. User Interface API

Answer: D


NEW QUESTION # 45
Universal Containers has a requirement for all accounts that do NOT qualify for a business extension (Custom field on the account record) for the next month to send a meeting invite to their contacts from the marketing automation system to discuss the next steps. It is estimated there will be approximately 1MilIion contacts per month.
What is the recommended solution?

  • A. Use Batch Apex.
  • B. Use Process builder.
  • C. Use Time-based workflow rule.
  • D. Use Trigger.

Answer: A


NEW QUESTION # 46
A new Salesforce program has the following high-level abstract requirement: Business processes executed on Salesforce require data updates between their Internal systems and Salesforce.
Which relevant detail should an integration architect seek to specifically solve for integration architecture needs of the program?

  • A. Core functional and non-functional requirements for User Experience design, Encryption needs, Community and license choices
  • B. Integration skills, SME availability, and Program Governance details
  • C. Timing aspects, real-time/near real-time (synchronous or asynchronous), batch and update frequency

Answer: C

Explanation:
Explanation
Timing aspects, real-time/near real-time (synchronous or asynchronous), batch and update frequency are relevant details that an integration architect should seek to specifically solve for integration architecture needs of the program. These details help to determine the appropriate integration pattern, technology, and solution for the business requirements. Core functional and non-functional requirements for User Experience design, Encryption needs, Community and license choices are important for the overall program design, but not specific to the integration architecture needs. Integration skills, SME availability, and Program Governance details are also important for the program execution, but not specific to the integration architecture needs.


NEW QUESTION # 47
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 and logging for audit purposes.
  • B. Platform events allow integration to payment gateway through the exchange of real-time event data, platform events are scalable and secure.
  • C. Build a custom Apex Callout to external Payment gateway service and provide success message to the CSR, the details of callouts and responses are logged for audit purposes.
  • D. Use External Services feature to integrate gateway to Salesforce ensuring real-time updates the CSR and support post payment processes.

Answer: A

Explanation:
Explanation
Make a callout to the payment gateway through ESB supporting error handling and logging for audit purposes. This solution meets the requirements of integrating with an external RESTful service, ensuring real-time updates to the CSR, and supporting post payment processes. ESB stands for Enterprise Service Bus, which is a software architecture model that allows communication between different applications via a common bus. ESB can handle the callout to the payment gateway service, and provide error handling, logging, routing, transformation, and orchestration capabilities. ESB can also integrate with other systems or services that are involved in the post payment processes, such as billing, invoicing, or reporting.
References: Certification - Integration Architect - Trailhead, [Enterprise Integration Patterns]


NEW QUESTION # 48
An Integration Developer is developing an HR synchronization app for a client. The app synchronizes Salesforce record data changes with an HR system that's external to Salesforce.
What should the integration architect recommend to ensure notifications are stored for up to three days if data replication fails?

  • A. Change Data Capture
  • B. Generic Events
  • C. Platform Events
  • D. Callouts

Answer: A

Explanation:
https://trailhead.salesforce.com/en/content/learn/modules/change-data-capture/understand-change-data-capture


NEW QUESTION # 49
A large B2C customer is planning to implement Salesforce CRM to become a Customer centric enterprise. Below, is their current system landscape diagram.

The goals for implementing Salesforce follows:
1. Develop a 360 view of customer
2. Leverage Salesforce capabilities for Marketing, Sales and Service processes
3. Reuse Enterprise capabilities built for Quoting and Order Management processes Which three systems from the current system landscape can be retired with the implementation of Salesforce?
Choose 3 answers

  • A. Quoting System
  • B. Sales Activity System
  • C. Case Management System
  • D. Email Marketing System
  • E. Order Management System

Answer: B,C,D


NEW QUESTION # 50
Given the diagram below, a Salesforce org, middleware, and Historical data store (with
20million records and growing) exists with connectivity between them
Historical records are archived from Salesforce and moved toHistorical Data store (which houses 20M records and growing; fine-tuned to be performant with search queries).
Call center agents use Salesforce, when reviewing occasional special cases, have requested access to view the related historical case items thatrelate to submit cases.
Which mechanism and patterns are recommended to maximize declarative configuration?

  • A. Use an ESB tool with Request-Reply pattern and then make a real-time Apex callout to the ESB endpoint to fetch and display component related to Case object
  • B. Use ESB tool with Data Virtualization pattern, expose OData endpoint, and then use Salesforce Connect to consume and display the External Objectalongside with the Case object.
  • C. C Use an ESB tool with a fire and forget pattern and then publish a platform event for the requested historical data.
  • D. Use an ETL tool with a Batch Data Synchronization pattern to migrate historical data into Salesforce and into a custom object (historical data) related to Case object.

Answer: B

Explanation:
The Data Virtualization pattern allows Salesforce to access external data sources without storing the data in Salesforce. This reduces the data storage and synchronization costs and enables real-time access to the historical data. Salesforce Connect can be used to consume OData endpoints exposed by the ESB tool and display the external objects as related lists or custom components on the Case object


NEW QUESTION # 51
Which three considerations should an Integration Architect consider when recommending Platform Event as a Integration solution?
Choose 3 answers

  • A. You can use Event Monitoring to track user activity, such as logins and running reports.
  • B. Subscribe to an AssetToken Event stream to monitor OAuth 2.0 authentication activity. C
  • C. When you delete an event definition, it's permanently removed and can't be restored.
  • D. Inability to create a Lightning record page for platform events.
  • E. Inability to query event messages using SOQL

Answer: C,D,E


NEW QUESTION # 52
Northern Trail Outfitters (NTO) has an affiliate company that would like immediate notifications of changes to opportunities in the NTO Salesforce instance. The affiliate company has a CometD client available.
Which solution is recommended in order to meet the requirement?

  • A. Create a PushTopic update event on the Opportunity Object to allow the subscriber to react to the streaming API.
  • B. Configure External Services to call the subscriber in Apex in the Onchange Trigger event as part of the flow.
  • C. Create a connected app in the affiliate org and select the "Accept CometD API Requests".
  • D. A Implement a polling mechanism in the client that calls the SOAP API getupdated method to get the ID values of each updated record.

Answer: A


NEW QUESTION # 53
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. Order Management, Case Management, and Email Marketing
  • B. Email Marketing, Sales Activity, and Case Management
  • C. Sales Activity, Order Management, and Case Management

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 # 54
Acustomer is migrating from an old legacy system to Salesforce. As part of the modernization effort, they would like to integrate al existing systems that currently work with their legacy application with Salesforce.
Which three constraints and pain-pointsshould an integration architect consider when choosing the integration pattern/mechanism?
Choose 3 answers

  • A. Error handling mechanisms
  • B. Multi-language and multi-currency requirement
  • C. Data Volume and Processing volume
  • D. System types - APIs, File systems, Email
  • E. Reporting and usability requirements

Answer: A,C,D

Explanation:
The system types, the error handling mechanisms, and the data volume and processing volume are three constraints and pain-points that an integration architect should consider when choosingthe integration pattern
/mechanism. The system types determine what kind of interfaces and protocols are available or required for the integration, such as APIs, file systems, email, etc. The error handling mechanisms ensure that the integration can handleany failures or exceptions gracefully and provide appropriate logging and notification.
The data volume and processing volume affect the performance and scalability of the integration, as well as the choice of synchronous or asynchronous methods. Reference: Salesforce Integration Architecture Designer Resource Guide, page 17


NEW QUESTION # 55
A customer of Salesforce has used Platform Events to integrate their Salesforce instance with an external third party Artificial Intelligence (AI) system. The AI system provides a prediction score for each lead that is received by Salesforce. Once the prediction score is received, the lead information is saved to Platform events for other processes. The trigger on the Platform Events is failing once this was rolled out to Production.
What type of monitoring should the Integration Consultant have considered to monitor this integration?

  • A. Set up debug logs for Platform Event triggers to monitor performance .
  • B. Monitor the volume of leads that are created in Salesforce.
  • C. Monitor Platform Events created per hour limits across the Salesforce instance.
  • D. Validate the Platform Event definition matches leads definition.

Answer: A


NEW QUESTION # 56
An enterprise architect has requested the Salesforce integration architect to review the following (see diagram and description) and provide recommendations after carefully considering all constraints of the enterprise systems and Salesforce Platform limits.
* About 3,000 phone sales agents use a Salesforce Lightning user interface (UI) concurrently to check eligibility of a customer for a qualifying offer.
* There are multiple eligibility systems that provide this service and are hosted externally.
* Their current response times could take up to 90 seconds to process and return.
* These eligibility systems are accessed through APIs orchestrated via ESB (MuleSoft).
* All requests from Salesforce traverse the customer's API Gateway layer, which imposes a timeout constraint of 9 seconds.

Which recommendation should the integration architect make?

  • A. Recommend synchronous Apex callouts from Lightning UI to External Systems via Mule and implement polling on an API Gat8eway timeout.
  • B. Implement a "Check Update" button that passes a requestID received from ESB (user action needed).
  • C. Create a platform event in Salesforce via Remote Call-In and use the empAPI in the Lightning UI to serve 3,000 concurrent users when responses are received by Mule.

Answer: C

Explanation:
In this architectural scenario, the Integration Architect must navigate two critical technical "bottlenecks": the
9-second API Gateway timeout and the 90-second backend processing time. Since the backend takes significantly longer than the gateway allows for a synchronous connection, a standard Request-Reply pattern will fail. Furthermore, having 3,000 concurrent agents perform synchronous callouts would risk hitting Salesforce's concurrent long-running request limits.
The most scalable and user-friendly solution is to implement an Asynchronous Request-Reply pattern using Platform Events and the empAPI.
When an agent clicks "Check Eligibility," Salesforce sends an initial asynchronous request to the ESB (MuleSoft). The ESB immediately acknowledges receipt with a 202 Accepted status, freeing up the Salesforce UI thread and avoiding the API Gateway's 9-second timeout. Once the backend eligibility system completes its 90-second process, MuleSoft acts as a client to Salesforce, performing a Remote Call-In to publish a specific Platform Event containing the result and the original Request ID.
On the frontend, the Lightning UI uses the empAPI (Enterprise Messaging Platform API) to subscribe to the streaming channel for that Platform Event. Because the empAPI uses CometD technology to maintain a single long-lived connection, it can efficiently push the response to the agent's screen the moment it arrives, without requiring the agent to manually refresh or click a "Check Update" button (as suggested in Option B).
This provides a "real-time" feel despite the long backend latency.
Option A is non-viable because synchronous polling would exacerbate the load on the API Gateway and likely lead to governance limit issues within Salesforce. By using Platform Events and empAPI, the architect ensures the solution remains within Salesforce's execution limits while providing a seamless, automated experience for a high-volume call center environment.


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

  • A. Determine data volume requirements, then identify the loading schedule.
  • B. Determinedata access prevention requirements, then identify frequency.
  • C. Determine data access prevention requirements, then identify system constraints.
  • D. Determine inbound integration requirements, then identify frequency.

Answer: B

Explanation:
The Architect should determine the data access prevention requirements and then identify the system constraints before recommending a solution. The data access prevention requirements are the business rules and policies that define how to prevent deactivated employees from accessing Salesforce data. For example, the Architect should determine whether the HR system can send a notification to Salesforce when an employee is deactivated, or whether Salesforce needs to query the HR system periodically to check the employee status. Thesystem constraints are the technical limitations and challenges that may affect the integration solution. For example, the Architect should determine whether the HR system supports outbound or inbound integration, what are the security and authenticationprotocols, what are the data formats and protocols, and what are the performance and scalability requirements. The frequency of the integration is not as important as the requirements and constraints, as it can be adjusted based on the business needs and technical feasibility. The data volume requirements and loading schedule are not relevant for this scenario, as they are more applicable for data migration or replication scenarios.


NEW QUESTION # 58
Sales representatives at Universal Containers (UC) use Salesforce Sales Cloud as their primary CRM. UC owns a legacy homegrown application that stores a copy of customer dataas well. Sales representatives may edit or update Contact records in Salesforce if there is a change.
Both Salesforce and the homegrown application should be kept synchronized for consistency. UC has these requirements:
1. When a Contact record in Salesforce is updated, the external homegrown application should be
2. The synchronization should be event driven.
3. The integration should be asynchronous.
Which option should an architect recommend to satisfy the requirements?

  • A. Leverage Platform Events to publish a custom event message containing changes to the Contact object.
  • B. Write an Apex Trigger with the @future annotation.
  • C. Leverage Change Data Capture to track changes to the Contact object and write a CometD subscriber on the homegrown application.

Answer: C

Explanation:
D Use an ETL tool to keep Salesforce and the homegrown application in sync on a regular candence.


NEW QUESTION # 59
......

Integration-Architect Exam PDF [2026] Tests Free Updated Today with Correct 130 Questions: https://www.dumpsmaterials.com/Integration-Architect-real-torrent.html

100% Real Integration-Architect dumps  - Brilliant Integration-Architect Exam Questions PDF: https://drive.google.com/open?id=1eHJkEzfS47bJm5rKS6CfFBptK6Mrmlsc