Latest [Mar 07, 2024] Salesforce Integration-Architect Exam Practice Test To Gain Brilliante Result
Take a Leap Forward in Your Career by Earning Salesforce Integration-Architect
NEW QUESTION # 43
A large consumer goods manufacturer operating in multiple countries is planning to implement Salesforce for their Sales and Support operations globally. They have the following security requirements:
1. Internal users from each country have to be authenticated with their local active directory.
2. Customers can create their own login or use Google login.
3. Partners have to be authenticated through a central system which is to be determined.
4. Internal users will have access to the central ERP with their credentials maintained in the ERP.
5. Additional internal systems will be integrated with Salesforce for Sales and Support business processes.
Which three requirements should the integration architect evaluate while designing the integration needs of this project?
Choose 3 answers
- A. Evaluate Salesforce solution for customers and for partners, using third party solution for internal users.
- B. Consider Third party Single Sign On solution supporting all user authentication including customer and partner.
- C. Assess security requirements for internal systems and decide Integration methods that support the requirements.
- D. Evaluate the build of a custom authentication mechanism for users in each country and support for customers and partners.
- E. Evaluate Salesforce native authentication mechanism for all users including customers and partners.
Answer: C,D,E
NEW QUESTION # 44
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. Handle verification process error in the Verification Webservice API in case there is a connection issue to the Webservice if it responds with an error.
- B. In case the verification process is down, Use mock service to send the response to the agent.
- 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 integration errors in the middleware in case the verification process is down, thenthe middleware should retry processing the request multiple times.
Answer: A
NEW QUESTION # 45
What is the first thing an Integration Architect should validate if a callout from a LightningWeb Component to an external endpoint is failing?
- A. The endpoint domain has been added to Cross-Origin Resource Sharing.
- B. The endpoint URL has added been to an outbound firewall rule.
- C. The endpoint URL has been added to Remote Site Settings.
- D. The endpoint URL has been added to Content Security Policies.
Answer: C
Explanation:
Explanation
The first thing an integration architect should validate if a callout from a Lightning Web Component to an external endpoint is failing is the endpoint domain has been added to Cross-Origin Resource Sharing (CORS).
CORS is a mechanism that allows web browsers to make requests to servers on different origins, such as different domains, protocols, or ports. CORS requires the server to send back a special header that indicates whether the browser is allowed to access the resource or not. If the endpoint domain is not added to the CORS whitelist in Salesforce, the browser will block the callout and throw an error. Option B is not correct because Content Security Policies (CSP) are used to control what resources can be loaded on a Visualforce or Lightning page, such as scripts, stylesheets, images, etc. CSP does not affect the callout from a Lightning Web Component to an external endpoint. Option C is not correct because outbound firewall rules are used to restrict the network traffic from Salesforce to external systems. Firewall rules are configured at the network level, not at the Salesforce level. Option D is not correct because Remote Site Settings are used to specify the domains that are allowed for callouts from Apex code, not from Lightning Web Components. References:
Working with CORS and CSP to Call APIs from LWC
[Cross-Origin Resource Sharing (CORS)]
NEW QUESTION # 46
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. Use External Services feature to integrate gateway to Salesforce ensuring real-time updates the CSR and support post payment processes.
- 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. Platform events allow integration to payment gateway through the exchange of real-time event data, platform events are scalable and secure.
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 # 47
A new Salesforce program has the following high level abstract requirement: Business processes executed on Salesforce require data updates between the internal systems and Salesforce Which three relevant details should a Salesforce Integration Architect seek to specifically solve for Integration architecture needs of the program?
Which three relevant details should a Salesforce Integration Architect seek to specifically solve for Integration architecture needs of the program?
Choose 3 answers
- A. Integration skills, SME availability and Program Governance details.
- B. Integration Style Process based, Data based, Virtual integration. E Core functional and non functional requirements for User Experience design, Encryption needs, Community, and license choices.
- C. Timing aspects - real-time/near real-time (synchronous or asynchronous), batch; update frequency.
- D. Source and Target system, Directionality, data volume & transformation complexity long with any middleware that can be leveraged.
Answer: B,C,D
NEW QUESTION # 48
A large enterprise customer with the following system landscape is planning to implement Salesforce Sales Cloud.
The following business processes need to be supported in Salesforce:
1. Sales Consultants should be able to have access to current inventory.
2. Enterprise Resource Planning System(ERP) is the system of record for pricing information.
3. Quotes should be generated in Salesforce with pricing from ERP.
4. Sales Management uses a Enterprise Business Intelligence (BI) toolto view Sales dashboards.
5. Master Data Management (MDM) is the system of record for customers and prospects.
6. Invoices should be accessible in Salesforce.
Which systems in the landscape should the Integration Consultant consider to be integrated with Salesforce to support the business requirements?
- A. ERP, Invoices system, Data Warehouse and BI Tool
- B. ERP, MDM, BI tool and Data Warehouse
- C. ERP, Inventory, Pricing Engine, Invoices system
- D. ERP, MDM, Data Warehouse, Invoices system
Answer: C
NEW QUESTION # 49
A company wants to standardize exception tracking, handling, and analytics. Given the following actions:
1. Build a companywide logging service hosted on a middleware platform
2. Create case object records for exceptions-based thresholds
3. Change all their Apex Loggers to publish Application Exceptions as custom Platform Events.
Which two specifications should the integration architect include in the logging service architecture?
Choose 2answers
- A. Receive Application Events through Change Data Capture (CDC).
- B. Create Salesforce Cases conditionally using automatic Case creation rules.
- C. Create Salesforce Cases using the Salesforce REST, SOAP or Bulk API.
- D. Subscribe to the Application Exceptions using the Salesforce Streaming API.
Answer: B,C
Explanation:
Explanation
Creating Salesforce Cases using the Salesforce REST, SOAP or Bulk API is a solution that can allow the logging service to create case records in Salesforce based on the exceptions received from the middleware platform. This way, the logging service can use the standard APIs to interact with Salesforce and leverage the features and functionality of the case object. Creating Salesforce Cases conditionally using automatic Case creation rules is a solution that can allow the logging service to create case records in Salesforce based on predefined criteria and actions. This way, the logging service can reduce the number of API calls and avoid creating unnecessary or duplicate cases. Receiving Application Events through Change Data Capture (CDC) is not a solution that is related to this requirement, as CDC is used for capturing data changes in Salesforce and sending them to external systems, not for receiving data from external systems. Subscribing to the Application Exceptions using the Salesforce Streaming API is also not a solution that is related to this requirement, as Streaming API is used for subscribing to events or notifications from Salesforce, not for sending data to Salesforce. Reference: Salesforce Integration Architecture Designer Resource Guide, page 25-26
NEW QUESTION # 50
Northern Trail Outfitters (NTO) has hired an Integration Architect to design the integrations between existing systems and a new instance of Salesforce. NTO has the following requirements:
1. Initial load of 2M Accounts, 5.5M Contacts, 4.3M Opportunities, and 45k Products into the new org.
2. Notification of new and updated Accounts andContacts needs to be sent to 3 external systems.
3. Expose custom business logic to 5 external applications in a highly secure manner.
4. Schedule nightly automated dataflows, recipes and data syncs.
Which set of APIs are recommended in order to meet the requirements?
- A. Bulk API, Chatter REST API, Apex SOAP API, Tooling API
- B. Bulk API, Streaming API, Apex SOAP API, Analytics REST API
- C. Bulk API, Chatter REST API, Apex REST API, Analytics REST API
- D. Bulk API, Streaming API, Apex REST API, Analytics REST API
Answer: D
Explanation:
Explanation
The set of APIs recommended to meet the requirements are Bulk API, Streaming API, Apex REST API, and Analytics REST API. Bulk API is a RESTful API that allows you to quickly load large amounts of data into Salesforce. Bulk API is suitable for the initial load of millions of records into the new org. Streaming API is a type of streaming event that notifies subscribers of changes to Salesforce records that match a SOQL query.
Streaming API is suitable for sending notifications of new and updated Accounts and Contacts to external systems. Apex REST API is an API that allows you to expose custom business logic as RESTful web services that can be accessed by external applications. Apex REST API is suitable for exposing custom business logic in a highly secure manner. Analytics REST API is an API that allows you to access analytics features, such as dashboards, lenses, datasets, and dataflows. Analytics REST API is suitable for scheduling nightly automated dataflows, recipes and data syncs. The other sets of APIs are not suitable for meeting all the requirements.
Chatter REST API is an API that allows you to access Chatter feeds and social data such as users, groups, followers, and files. Chatter REST API is not relevant for this scenario. Apex SOAP API is an API that allows you to expose custom business logic as SOAP web services that can be accessed by external applications.
Apex SOAP API is less preferable than Apex REST API because it requires more bandwidth and processing time due to the XML format. Tooling API is an API that allows you to build custom development tools or apps for Salesforce applications. Tooling API is not relevant for this scenario.
NEW QUESTION # 51
Northern Trail Outfitters has recently experienced intermittent network outages in its call center. When network service resumes, Sales representatives have inadvertently created duplicate orders in the manufacturing system because the order was placed but the return acknowledgement was lost during the outage.
Which solution should an architect recommend to avoid duplicate order booking?
- A. Use Outbound Messaging to ensure manufacturing acknowledges receipt of order.
- B. Have scheduled Apex resubmit orders that do not have a successful response.
- C. Use scheduled apex to query manufacturing system for potential duplicate or missing orders.
- D. Implement idempotent design and have Sales Representatives retry order(s) in question.
Answer: D
Explanation:
Explanation
Idempotent design means that the same request can be repeated multiple times without changing the outcome.
This is useful for avoiding duplicate orders in case of network failures or timeouts. By implementing idempotent design, the sales representatives can retry the order(s) in question without creating duplicates in the manufacturing system. Outbound messaging is not a reliable solution because it does not guarantee delivery or acknowledgement of messages. Scheduled apex is not a real-time solution and may not catch all the duplicate or missing orders
NEW QUESTION # 52
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 storeit 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: B
Explanation:
Explanation
The mobile device should make a REST Apex inbound call to meet the requirement. A REST Apex inbound call allows the mobile device to invoke custom Apex logic on Salesforce using a RESTful interface. The Apex logic can then access the geolocation field using the user's OAuth token and update it with the GPS coordinates from the mobile device. The geolocation field is secured with Field Level Security, so the user can view the value without changing it. A SOAP API inbound call or a REST API inbound call would not be able to access the custom geolocation field, as they are not supported by the standard Salesforce objects and fields.
Reference: Salesforce Integration Architecture Designer Resource Guide, page 20
NEW QUESTION # 53
Customer is evaluating Platform Events solution and would like help in comparing/contrasting it with Outbound Message for a real-time / near-real time needs. They expect 3,000 consumers of messages from Salesforce.
Which three considerations should be evaluated and highlighted when deciding between the solutions?
Choose 3 answers
- A. Number of concurrent subscribers to Platform Events is capped at 2,000. An Outbound Message configuration can pass only 100 notifications in a single message to a SOAP end point.
- B. Message sequence is possible in Outbound Message but not guaranteed with Platform Events. Both offer very high reliability. Fault handling and recovery are fully handled by Salesforce.
- C. Both Platform Events and Outbound Message offer declarative means for asynchronous near-real time needs. They aren't best suited for real-time integrations.
- D. Both Platform Events and Outbound Message are highly scalable. However, unlike Outbound Message, only Platform Events have Event Delivery and Event Publishing limits to be considered.
- E. In both Platform Events and Outbound Messages, the event messages are retried by and delivered in sequence, and only once. Salesforce ensures there is no duplicate message delivery.
Answer: A,D,E
Explanation:
Explanation
Both Platform Events and Outbound Message offer declarative means for asynchronous near-real time needs.
They aren't best suited for real-time integrations (A). In both Platform Events and Outbound Messages, the event messages are retried by and delivered in sequence, and only once. Salesforce ensures there is no duplicate message delivery (B). Message sequence is possible in Outbound Message but not guaranteed with Platform Events. Both offer very high reliability. Fault handling and recovery are fully handled by Salesforce Number of concurrent subscribers to Platform Events is capped at 2,000. An Outbound Message configuration can pass only 100 notifications in a single message to a SOAP end point (D). Both Platform Events and Outbound Message are highly scalable. However, unlike Outbound Message, only Platform Events have Event Delivery and Event Publishing limits to be considered (E). Reference: Salesforce Integration Architecture Designer Resource Guide, page 23
NEW QUESTION # 54
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. Platform events allow integration to payment gateway through the exchange ofreal-time event data, platform events are scalable and secure.
- B. 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.
- C. Make a callout to the payment gateway through ESB supporting error handling andlogging for audit purposes.
- D. Use External Services feature to integrate gateway to Salesforce ensuring real-timeupdates the CSR and support post payment processes.
Answer: C
NEW QUESTION # 55
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 all sales representatives that use Salesforce anytime 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. Tooling API
- C. Connect REST API
- D. REST API
Answer: A
NEW QUESTION # 56
An 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 an Architect determine before recommending a solution?
- A. Determine inbound integration requirements, then identify frequency.
- B. Determine data access prevention requirements, then identify frequency.
- C. Determine data access prevention requirements, then identify system constraints.
- D. Determine data volume requirements, then identify the loading schedule.
Answer: A
NEW QUESTION # 57
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 Change Data Capture to track changes to the Contact object and write a CometD subscriber on the homegrown application.
- B. Leverage Platform Events to publish a custom event message containing changes to the Contact object.
- C. Write an Apex Trigger with the @future annotation.
Answer: A
Explanation:
D Use an ETL tool to keep Salesforce and the homegrown application in sync on a regular candence.
NEW QUESTION # 58
A company has an external system that processes and tracks orders. Sales reps manage their leads and opportunity pipeline in Salesforce. In the current state, the two systems are disconnected and processing orders requires a lot of manual entry on sales rep part. This creates delays in processing orders and incomplete data due to manual entry.
As a part of modernization efforts the company decided to integrate Salesforce and the order management system. The following technical requirements were identified:
1. Orders need to be created in real time from salesforce
2. Minimal customization*, and code should be written due to a tight timeline and lack of developer resources
3. Sales reps need to be able to see order history and be able to see most up to date information on current order status.
4. Managers need to be able to run reports in Salesforce to see daily and monthly order volumes and fulfillment timelines.
5. The legacy system is hosted on premise and is currently connected to the Enterprise Service Bus (ESB). The ESB is flexible enough to provide any methods and connection types needed by salesforce team.
6. There are 1000 sales reps. Each user processes/creates on average 15 orders per shift. Most of the orders contain 20-30 line items.
How should an integration architect integrate the two systems based on the technical requirements and system constraints?
- A. Use Salesforce standard object, REST API and ETL.
- B. Use Salesforce custom object, custom REST API and ETL.
- C. Use Salesforce external object and OData connector.
- D. Use Salesforce big object, SOAP API and Dataloader.
Answer: A
NEW QUESTION # 59
A company that is a leading provider of courses and training delivers courses using third party trainers. The trainer for the company has to be verified from 10 different training accreditation verification agencies before providing training for the company. Each training accreditation agency has its own response time, which could take days to confirm a trainer.
The company decided to automate the trainer accreditation verification process by integrating to the agencies' web services.
What is the recommended approach to automate this process?
- A. Make an apex callout using @future annotation to make the call out to all different agencies. The response should update the trainer status to "verified".
- B. Use salesforce external service to make the call out, Salesforce external service should check the verification agencies until the result is verified, then update the trainer status to "verified".
- C. Use middleware to handle the call out to the 10 different verification services, the middleware will handle the business logic of consolidating the verification result from t 10 services, then make a call-in to salesforce and update the verification status to "verified".
- D. Create a trigger on the trainer record to make a Callout to each verification agencies, write business logic to consolidate the verification then update the trainer status to verified".
Answer: C
Explanation:
Explanation
Answer D is valid because using middleware to handle the call out to the 10 different verification services is a scalable and reliable solution that can handle the complexity and variability of the integration. The middleware can orchestrate the calls to the different web services, consolidate the verification results, and handle any errors or retries. The middleware can then make a call-in to Salesforce and update the verification status to "verified" using an API or a platform event12 Answer A is not valid because using Salesforce external service to make the call out to the 10 different verification services is not a feasible or efficient solution. Salesforce external service is a feature that allows invoking an external service from a flow and mapping its inputs and outputs to flow variables.
However, this feature requires configuring an Apex action, a named credential, and an external service definition for each web service, which is not a low code solution. Moreover, this feature does not support checking the verification agencies until the result is verified, as it only invokes the external service once per flow interview3 Answer B is not valid because creating a trigger on the trainer record to make a callout to each verification agency is not a recommended or robust solution. Triggers are Apex code that execute before or after database events, such as insert, update, or delete. However, triggers cannot make callouts directly, as they are part of a database transaction and must complete quickly. To make a callout from a trigger, an asynchronous process such as a future method or a queueable job must be used, which adds complexity and overhead to the integration. Moreover, triggers have limits on the number of callouts and asynchronous calls they can make per transaction, which may affect the scalability and reliability of the integration.
Answer C is not valid because making an Apex callout using @future annotation to make the call out to all different agencies is not a suitable or reliable solution. The @future annotation allows marking a method for execution at a later time when system resources become available. However, this annotation has several limitations and drawbacks, such as:
Future methods cannot return values, so they cannot update the trainer status to "verified" directly.
Future methods have limits on the number of callouts and future calls they can make per execution, which may affect the scalability and reliability of the integration.
Future methods run in their own thread and do not share any static variables or state with other methods, which makes it difficult to consolidate the verification results from different agencies.
Future methods are not guaranteed to execute at a specific time or order, which may affect the timeliness and accuracy of the integration.
1: Orchestration Pattern 2: Remote Process Invocation-Request and Reply 3: External Services : Apex Developer Guide: Triggers : Apex Developer Guide: Using Future Methods
NEW QUESTION # 60
Northern Trail Outfitters is seeking to improve the performance and security of outbound integrations from Salesforce to on-premise servers.
What should the Architect consider before recommending a solution?
- A. Considerations for using Deterministic Encryption
- B. A Default gateway restrictions
- C. External gateway products in use
- D. ShieldPlatform Encryption Limitations
Answer: C
Explanation:
Explanation
Option A is correct because external gateway products in use can affect the performance and security of outbound integrations from Salesforce to on-premise servers. External gateway products are software or hardware devices that act as intermediaries between Salesforce and the on-premise servers, such as firewalls, proxies, load balancers, or VPNs. They can have different configurations, features, and limitations that can impact the speed, reliability, and security of the data transmission. For example, some external gateway products may require authentication, encryption, or compression of the data, which can add overhead and latency to the integration. Some external gateway products may also have bandwidth or throughput limits, which can affect the scalability and availability of the integration.
Therefore, the architect should consider the external gateway products in use before recommending a solution.
Option B is incorrect because a default gateway restriction is not a factor that can affect the performance and security of outbound integrations from Salesforce to on-premise servers. A default gateway restriction is a feature that allows administrators to restrict outbound requests from Salesforce to a specific IP address or domain name. This can help prevent unauthorized or malicious requests from Salesforce to external systems. However, this feature does not affect the performance or security of the outbound requests themselves, as it only acts as a filter for the destination of the requests.
Option C is incorrect because considerations for using deterministic encryption are not relevant for outbound integrations from Salesforce to on-premise servers. Deterministic encryption is a type of encryption that produces the same ciphertext for the same plaintext input. This can help preserve some functionality and performance of encrypted data in Salesforce, such as filtering, sorting, and indexing.
However, deterministic encryption is not applicable for outbound integrations from Salesforce to on-premise servers, as it is only supported for custom fields and not for standard fields or attachments.
Moreover, deterministic encryption does not affect the security of the data transmission itself, as it only encrypts the data at rest in Salesforce.
Option D is incorrect because Shield Platform Encryption limitations are not relevant for outbound integrations from Salesforce to on-premise servers. Shield Platform Encryption is a feature that allows administrators to encrypt sensitive data at rest in Salesforce using AES 256-bit encryption. This can help protect data from unauthorized access or theft. However, Shield Platform Encryption limitations are not relevant for outbound integrations from Salesforce to on-premise servers, as they only affect the functionality and performance of encrypted data in Salesforce, such as searching, reporting, or validation rules. Shield Platform Encryption does not affect the security of the data transmission itself, as it only encrypts the data at rest in Salesforce.
References: Salesforce Integration Patterns and Practices : Salesforce Integration Guide : Restrict Outbound Requests with a Default Gateway : Deterministic Encryption : Shield Platform Encryption Considerations :
Shield Platform Encryption : Shield Platform Encryption Architecture
NEW QUESTION # 61
Universal Containers is a global financial company that sells financial products and services including, bank accounts, loans, and insurance. UC uses Salesforce Service cloud to service their customer via calls, live chat. The support agents would open bank accounts on the spot for customers who are inquiring about UC bank accounts.
UC Core banking system is the system of record for bank accounts and all accounts opened in salesforce have to be synced in real-time to the core banking system. Support agents need to inform the customers with the newly created bank account ID which has to be generated from the core banking system.
Which integration pattern is recommended for this use case?
- A. Use salesforce platform event.
- B. Use streaming API to generate push topic.
- C. Use outbound message.
- D. Use request and reply.
Answer: D
NEW QUESTION # 62
Which three considerations should an Integration Architect consider when recommending Platform Event as a Integration solution?
Choose 3 answers
- A. Inability to create a Lightning record page for platform events.
- B. You can use Event Monitoring to track user activity, such as logins and running reports.
- C. When you delete an event definition, it's permanently removed and can't be restored.
- D. Inability to query event messages using SOQL
- E. Subscribe to an AssetToken Event stream to monitor OAuth2.0 authentication activity. C
Answer: A,C,D
Explanation:
Explanation
These are three considerations that an Integration Architect should consider when recommending Platform Event as an Integration solution. Platform Events are a type of event-driven architecture that allows you to publish and subscribe to custom events in Salesforce and external systems. Platform Events have some limitations and features that an Integration Architect should be aware of, such as:
Inability to query event messages using SOQL. Platform Events are not stored in Salesforce database, but in an event bus that retains them for 24 hours. You cannot use SOQL to query event messages, but you can use the EventLogFile object or the Event Monitoring feature to access them.
Inability to create a Lightning record page for platform events. Platform Events are not standard or custom objects, but a special type of sObject that can be inserted into the event bus. You cannot create a Lightning record page for platform events, but you can use Apex triggers, Lightning web components, or CometD clients to subscribe to them.
When you delete an event definition, it's permanently removed and can't be restored. An event definition is a metadata type that defines the schema and properties of a platform event message. You can create or modify event definitions in Salesforce Setup or using Metadata API. However, if you delete an event definition, it's permanently removed from your org and can't be restored. You also lose access to any event messages that use that event definition.
References: Certification - Integration Architect - Trailhead, [Platform Events Developer Guide]
NEW QUESTION # 63
An Enterprise Customer is planning to implement Salesforce to support case management. Below, is their current system landscape diagram.
Considering Salesforce capabilities, what should the Integration Architect evaluate when integrating Salesforce with the current system landscape?
- A. Integrating Salesforce with Order Management System, Email Management System and Case Management System.
- B. Integrating Salesforce with Email Management System, Order Management System and Case Management System.
- C. Integrating Salesforce with Order Management System, Data Warehouse and Case Management System.
- D. Integrating Salesforce with Data Warehouse, Order Management and Email Management System.
Answer: D
Explanation:
Explanation
Integrating Salesforce with Data Warehouse, Order Management and Email Management System is the best option considering Salesforce capabilities. Salesforce can be used as the primary case management system, replacing the existing one. Salesforce can also integrate with the Data Warehouse to provide analytics and reporting on case data. Salesforce can integrate with the Order Management System to access order information related to cases. Salesforce can integrate with the Email Management System to send and receive emails from customers and agents. Reference: Salesforce Integration Architecture Designer Resource Guide, page 16
NEW QUESTION # 64
An Integration Architect has built a solution using REST API, updating Account, Contact, and other related information. The data volumes have increased, resulting in higher API calls consumed, and some days the limits are exceeded. A decision was made to decrease the number of API calls using bulk updates. The customer prefers to continue using REST API to avoid architecture changes.
Which REST API composite resources should the Integration Architect use to allow up to 200 records in one API call?
- A. Batch
- B. Composite
- C. SObject Tree
- D. SObject Collections
Answer: D
Explanation:
Explanation
SObject Collections is a REST API composite resource that allows you to create, update, or delete up to 200 records in one API call. You can specify the type of operation (create, update, or delete) for each record in the request body, and the response body will contain the status and IDs of each record. SObject Collections is suitable for bulk operations on records that are not related to each other1.
SObject Tree is another REST API composite resource that allows you to create up to 200 records in one API call. However, unlike SObject Collections, SObject Tree requires the records to be related to each other in a hierarchy. You can specify the parent and child records in a JSON tree structure, and the response body will contain the reference IDs and URLs of each record. SObject Tree is suitable for creating nested data in one request2.
Batch is a REST API composite resource that allows you to combine up to 25 requests in one API call. Each request can be a different type of operation (query, create, update, delete, etc.) on different objects. The response body will contain the status and results of each request. Batch is suitable for grouping multiple requests into one transaction3.
Composite is a REST API composite resource that allows you to execute a series of REST API requests in one API call. You can use the output of one request as the input of another request using a reference ID. The response body will contain the status and results of each request. Composite is suitable for chaining requests that depend on each other.
Therefore, the correct answer is A, because SObject Collections is the only REST API composite resource that allows bulk updates on records that are not related to each other.
References: 1: SObject Collections | REST API Developer Guide | Salesforce Developers 2: SObject Tree | REST API Developer Guide | Salesforce Developers 3: Batch | REST API Developer Guide | Salesforce Developers : [Composite | REST API Developer Guide | Salesforce Developers]
NEW QUESTION # 65
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. Generic Events
- B. Callouts
- C. Platform Events
- D. Change Data Capture
Answer: D
Explanation:
Explanation
Change Data Capture is a feature that enables you to receive near-real-time changes of Salesforce records, including create, update, delete, and undelete operations. Change Data Capture retains change events in the event bus for up to three days, so you can resume data replication from the point of failure. Change Data Capture also provides a consistent and reliable way to synchronize data changes with external systems, without the need for custom triggers or code. Reference: Salesforce Integration Architecture Designer Resource Guide, page 24
NEW QUESTION # 66
Service Agents at Northern Trail Outfitters uses Salesforce to manage cases and B2C Commerce for ordering.
Which integration solution should an architect recommend in order for the service agents to see order history from a B2C Commerce system?
- A. REST API offered by Salesforce Platform
- B. Mulesoft Anypoint Platform
- C. A REST API offered by Commerce Platform
- D. Salesforce B2C Commerce to Service Cloud Connector
Answer: D
Explanation:
https://help.salesforce.com/articleView?id=icx_b2c_conversationalcommerce_connector.htm&type=5
NEW QUESTION # 67
......
Authentic Best resources for Integration-Architect Online Practice Exam: https://dumpstorrent.actualpdf.com/Integration-Architect-real-questions.html
