Integration-Architect Questions Prepare with Learning Information! 2025 Regularly updated
Get Integration-Architect Products Practice Material for Integration-Architect Exam Question Preparation
NEW QUESTION # 69
Northern Trail Outfitters requires an integration to be set up between one of its Salesforce orgs and an External Data Source using Salesforce Connect. The External Data Source supports Open Data Protocol.
Which configuration should an integration architect recommend be implemented in order to secure requests coming from Salesforce?
- A. Configure a certificate for OData connection.
- B. Configure Special Compatibility for OData connection.
- C. Configure Identity Type for OData connection.
Answer: C
NEW QUESTION # 70
Northern Trail Outfitters' (NTO) Salesforce org usually goes through 8k-10k batches a day to synch data from external sources. NTO's Integration Architect has received requirements for a new custom object, FooBarc, for which 90M records will need to be loaded into the org. Once complete, 20GB (about 30M records) needs to be extracted to an external auditing system.
What should the architect recommend using to meet these requirements in a day?
- A. Insert and query using Bulk API 2.0.
- B. Insert using Bulk API 1.0 and query using REST API.
- C. Insert and query using Bulk API 1.0.
- D. Insert using Bulk API 2.0 and query using REST API.
Answer: A
Explanation:
Answer D is valid because using Bulk API 2.0 for both inserting and querying data canmeet the requirements of loading and extracting large volumes of data in a day. Bulk API 2.0 is a RESTful API that allows creating, updating, deleting, or querying millions of records asynchronously by uploading or downloading CSV or JSON files. Bulk API2.0 has several advantages over Bulk API 1.0, such as:
It does not count against the daily limit of 5,000 batches per rolling 24-hour period.
It supports PK Chunking for queries, which automatically splits large data sets into manageable chunks based onthe primary key.
It simplifies the job lifecycle and reduces the number of API calls needed to perform a bulk operation.
Answer A is not valid because using Bulk API 2.0 for inserting data and REST API for querying data is not an optimal solution for handling large volumes of data in a day. REST API is a synchronous API that allows creating, updating, deleting, or querying individual records or small batches of records using HTTP methods.
REST API has several limitations and drawbacks for this use case, such as:
It counts against the daily limit of 15,000 API requests per 24-hour period.
It does not support PK Chunking for queries, which means that large data sets may exceed the query timeout or heap size limits.
It requires more API calls and processing time to perform a bulk operation than Bulk API 2.0.
Answer B is not valid because using Bulk API 1.0 for both inserting and querying data is not a feasible solution for handling large volumes of data in a day. Bulk API 1.0 is a SOAP-based API that allows creating, updating, deleting, or querying millions of records asynchronously by uploading or downloading XML or CSV files. Bulk API 1.0 has several limitations and drawbacks compared to Bulk API 2.0, such as:
It counts against the daily limit of 5,000 batchesper rolling 24-hour period, which may not be enough to load and extract 90M and 30M records respectively.
It does not support JSON format for data files, which may not be compatible with some external systems or applications.
It requires more API calls andcomplexity to manage the job lifecycle and handle errors or retries than Bulk API 2.0.
Answer C is not valid because using Bulk API 1.0 for inserting data and REST API for querying data is not a suitable or reliable solution for handling large volumes ofdata in a day. As explained above, both Bulk API
1.0 and REST API have limitations and drawbacks that may affect the performance, efficiency, and scalability of the integration.
NEW QUESTION # 71
Which two approaches will require the least amount of development effort?
Choose 2 answers
- A. Use the tooling API with Process Builder to insert leads in real time.
- B. Use the Composite REST API to aggregate multiple leads in a single call.
- C. Configure named credentials in the source org.
- D. Call the Salesforce REST API to insert the lead into the target system.
Answer: B,C
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 # 72
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. Middleware should coordinate request delivery and payment processing.
- B. Data Entry Point and Middleware should automatically retry requests.
- C. Payment System and Middleware should automatically retry requests.
- D. Payment System should process a payment request only once.
Answer: A,D
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 # 73
Northern Trail Outfitters uses a custom Java application to display code coverage and test results for all of their enterprise applications and is planning to include Salesforce as well.
Which Salesforce API should an Integration Architect use to meet the requirement?
- A. SOAP API
- B. Tooling API
- C. Metadata API
- D. Analytics REST API
Answer: B
Explanation:
https://developer.salesforce.com/docs/atlas.en-us.api_tooling.meta/api_tooling/tooling_api_objects_apexcodecoverage.htm
NEW QUESTION # 74
A large enterprise customer has decided to implement Salesforce as their CRM. The current system landscape includes the following:
1. An Enterprise Resource Planning (ERP) solution that is responsible for Customer Invoicingand Order fulfillment.
2. A Marketing solution they use for email campaigns.
The enterprise customer needs their sales and service associates to use Salesforce to view and log their interactions with customers and prospects in Salesforce.
Which system should be the System of record for their customers and prospects?
- A. New CustomDatabase forCustomers and Prospects.
- B. Marketing with all customer data from Salesforce and ERP.
- C. ERP with all prospect data from Marketing and Salesforce.
- D. Salesforce with relevant Marketing and ERP information.
Answer: D
Explanation:
Option C is correct because Salesforce should be the system of record for their customers and prospects, as it is the CRM solution that the sales and service associates use to view and log their interactions with them. Salesforce can also integrate with the Marketing and ERP solutions to display relevant information from those systems, such as campaign history, invoices, and orders12 Option A is incorrect because ERP is not a suitable system of record for customers and prospects, as it is mainly focused on invoicing and order fulfillment. ERP may not have all the data that the sales and service associates need to interactwith them, such as contact details, preferences, activities, and opportunities. ERP may also have different datamodels and definitions than Salesforce and Marketing, which can cause data quality and consistency issues3 Option B is incorrect because Marketing is not a suitable system of record for customers and prospects, as it is mainly focused on email campaigns. Marketing may not have all the data that the sales and service associates need to interact with them, such as account information, service cases, contracts, and quotes. Marketing may also have different data models and definitions than Salesforce and ERP, which can cause data quality and consistency issues.
Option D is incorrect because creating a new custom database for customers and prospects is not a feasible orefficient solution, as it would require additional development, maintenance, and integration costs. It would also create another layer of complexity and potential data duplication in the system landscape. Salesforce already provides a robust and flexibleplatform for managing customer and prospect data, which can be easily customized and integrated with other systems.
References: 1: Salesforce CRM - The Definitive Guide 2: SalesforceIntegration Cloud - Connect Any App, Data, or Device 3: What Is ERP? | Oracle : Salesforce vs ERP: What's the Difference? : Marketing Cloud - Digital Marketing Platform : Salesforce vs Marketing Cloud: What's the Difference? : Salesforce Platform - Build Apps Fast : Why You Shouldn't Build Your Own CRM System
NEW QUESTION # 75
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. Remove the query filters.
- B. Remove the sharing restrictions.
- C. Include non-selective criteria in query filters.
- D. Include selective criteria in query filters.
Answer: B,D
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 # 76
Northern Trail Outfitters wants to use Salesforce as a front end for creating accounts using the lead-to-opportunity process.
1. An order is created in Salesforce when the opportunity is closed and won, but the back-end ERP system is the data master for order,
2. Customer wants to be able to see within Salesforce all the stages of order processing like Order Created, Order Shipped, Order Paid that are within the retention window.
Which two message durability considerations should an Integration Architect make when designing a solution to meet these business requirements?
Choose 2 answers
- A. When subscribing to Salesforce Event bus, ReplaylD is used with a value of -1 to be able to see new events.
- B. High-volume event messages are stored for 24 hours (one day).
- C. High-volume event messages are stored for 72 hours (three days).
- D. When subscribing to Salesforce Event bus, ReplaylD is used with a value of -2 to be able to see old and new events.
Answer: C,D
Explanation:
Explanation
The message durability considerations that an Integration Architect should make when designing a solution to meet these business requirements are:
When subscribing to Salesforce Event bus, ReplayID is used with a value of -2 to be able to see old and new events.
High-volume event messages are stored for 72 hours (three days).
A Salesforce Event bus is a messaging service that allows you to publish and subscribe to events in Salesforce or from external sources. ReplayID is a property of an event message that indicates its position in the event stream. By using ReplayID with a value of -2, you can replay all events stored in the retention window, which can help you see the stages of order processing in Salesforce. High-volume event messages are a type of event message that can handle large volumes of data and are optimized for performance and scalability.
High-volume event messages are stored for 72 hours (three days) in the event bus, which means they can be replayed within that time frame. The other options are not correct. Using ReplayID with a value of -1 means you can only see new events that are published after your subscription. High-volume event messages are not stored for 24 hours (one day), but for 72 hours (three days).
NEW QUESTION # 77
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. Platform Events
- C. Callouts
- D. Generic Events
Answer: A
Explanation:
https://trailhead.salesforce.com/en/content/learn/modules/change-data-capture/understand-change-data-capture
NEW QUESTION # 78
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 connected app in the affiliate org and select the "Accept CometD API Requests".
- B. A Implement a polling mechanism in the client that calls the SOAP API get updated method to get the ID values of each updated record.
- C. Create a PushTopic update event on the Opportunity Object to allow the subscriber to react to the streaming API.
- D. Configure External Services to call the subscriber in Apex in the Onchange Trigger event as part of the flow.
Answer: C
Explanation:
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, which are 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 # 79
A developer has been tasked by the integration architect to build a solution based on the Streaming API. The developer has done some research and has found there are different implementations of the events in Salesforce (Push Topic Events, Change Data Capture, Generic Streaming, Platform Events), but is unsure of to proceed with the implementation.The developer asks the system architect for some guidance.
What should the architect consider when making the recommendation?
- A. Change Data Capture can be published from Apex.
- B. Push Topic Event can define a custom payload.B Change Data Capture does not have record access support.
- C. Apex triggers can subscribe to Generic Events.
Answer: A
Explanation:
Explanation
Push Topic Events can define a custom payload, which is one of the factors that should be considered when choosing a Streaming API implementation. Push Topic Events are based on SOQL queries that define the data changes to be notified of. You can specify the fields to be returned in the event message by using the SELECT clause in the query. This allows you to customize the payload according to your needs2 References: Create a PushTopic
NEW QUESTION # 80
A subscription-based media company's system landscape forces many subscribers to maintain multiple accounts and to login more than once. An Identity and Access Management (IAM) system, which supports SAML and OpenId, was recently implemented to improve their 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 two requirements should the Salesforce Community Cloud support for self-registration and SSO?
Choose 2 answers
- A. OpenId Connect Authentication Provider and Registration Handler
- B. SAML SSO and Registration Handler
- C. OpenId Connect Authentication Provider and just-in-time provisioning
- D. SAML SSO and just-in-time provisioning
Answer: A,D
Explanation:
The Salesforce Community Cloud should support OpenId Connect Authentication Provider and Registration Handler, and SAML SSO and just-in-time provisioning for self-registration and SSO. OpenId Connect is a protocol that allows users to authenticate with an external identity provider and access Salesforce resources. A registration handler is a class that implements the Auth.RegistrationHandler interface and defines how to create new users or update existing users in Salesforce from the information received from the identity provider. SAML SSO is a protocol that allows users to log in to Salesforce with a single credential from an identity provider. Just-in-time provisioning is a featurethat allows creating or updating user accounts in Salesforce based on SAML assertions.
References: [OpenID Connect Authentication Providers], [Registration Handler Interface], [SAML Single Sign-On for Communities].
NEW QUESTION # 81
What should an Architect recommend to ensure all integrations to the Northern Trail Outfitters company portal useSSL mutual authentication?
- A. Generate a Self-signed Certificate.
- B. Generate a CA-signed Certificate.
- C. Enable My Domain and SSL/TLS.
- D. Enforce SSL/TLS MutualAuthentication.
Answer: D
Explanation:
This is because SSL/TLS mutual authentication is a security featurethat allows Salesforce to verify the identity of the client that connects to its API endpoint on port 8443. To enable this feature, you need to upload a client certificate to Salesforce and assign the "Enforce SSL/TLS Mutual Authentication" user permission to the users who need to access the company portal. The other options are not sufficient for this scenario because:
A, Enable My Domain and SSL/TLS, is a prerequisite for using SSL/TLS mutual authentication, but it does not ensure that all integrations use it. My Domain allows you to customize your Salesforce domain name and SSL/TLS provides encryption for your data in transit.
C, Generate a Self-signed Certificate, is a step that you need to do on the client side to create a certificate that can be usedfor SSL/TLS mutual authentication, but it does not ensure that allintegrations use it. You also need to upload the certificate to Salesforce and assign the user permission.
D, Generate a CA-signed Certificate, is an alternative to generating a self-signedcertificate, but it also does not ensure that all integrations use SSL/TLS mutual authentication. You still need to upload the certificate to Salesforce and assign the user permission.
References:
Certificates in Mutual Authentication
Configure Your API Client to Use Mutual Authentication
Salesforce Mutual Authentication Setup
NEW QUESTION # 82
Northern Trail Outfitters (NTO) uses Salesforce to track leads, opportunities andorder details that convert leads to customers. However, Orders are managed by an external (remote) system. Sales representatives 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 Visualization
- B. Process Orchestration
- C. Batch Processing
- D. Data Synchronization
Answer: A
Explanation:
Explanation
Data Visualization is the type of integration that allows users to view real-time data from an external system without storing it in Salesforce. This can be achieved by using Lightning Web Components, Visualforce pages, or Canvas apps that display data from the external system using APIs or web services. Data Synchronization, Process Orchestration, and Batch Processing are types of integration that involve moving data between systems, which is not required by the business requirement. Reference: Salesforce Integration Architecture Designer Resource Guide, page 9
NEW QUESTION # 83
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. Use External Services feature to integrate gateway to Salesforce ensuring real-timeupdates the CSR and support post payment processes.
- C. Make a callout to the payment gateway through ESB supporting error handling andlogging for audit purposes.
- 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: C
NEW QUESTION # 84
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: B
Explanation:
Explanation
Using Salesforce custom object, custom REST API and ETL is a better solution than using Salesforce standard object, REST API and ETL. A custom object can store the order information and provide more flexibility and control over the data model, validation rules, triggers, etc. A custom REST API can be used to create orders in real time from Salesforce, using the ESB as a proxy to communicate with the legacy system. An ETL tool can be used to sync the order history and status from the legacy system to Salesforce, using the last modified date as a filter. This way, sales reps can see the order history and the most up-to-date information on current order status, and managers can run reports on order volumes and fulfillment timelines. A standard object, such as Order, may not meet all the business requirements and may require more customization than a custom object.
A standard REST API may not provide enough security and error handling for creating orders in real time.
Reference: Salesforce Integration Architecture Designer Resource Guide, page 18
NEW QUESTION # 85
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. Inability to create a Lightning record page for platform events.
- C. Inability to query event messages using SOQL
- D. When you delete an event definition, it's permanently removed and can't be restored.
- E. Subscribe to an AssetToken Event streamto monitor OAuth2.0 authentication activity. C
Answer: B,C,D
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 thatallows 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 eventdefinition.
References: Certification - Integration Architect - Trailhead, [Platform Events Developer Guide]
NEW QUESTION # 86
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 Salesforceanytime the quoting system will be taken down for maintenance.
Which Salesforce API should an Integration Architect use to fulfill this requirement?
- A. Connect REST API
- B. REST API
- C. Streaming API
- D. Tooling API
Answer: C
Explanation:
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, which are 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 # 87
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 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.
- B. 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.
- C. Provide true message queueing for integration scenarios (including orchestration, process choreography, quality of service, etc.) given that a middleware solution is required.
- D. 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
- E. Transform a fire-and-forget mechanism to request-reply should be handled by middleware tools (like ETL/ESB) to improve performance.
Answer: A,B,C
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 # 88
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. Inability to create a Lightning record page for platform events.
- C. Inability to query event messages using SOQL
- D. When you delete an event definition, it's permanently removed and can't be restored.
- E. Subscribe to an AssetToken Event stream to monitor OAuth2.0 authentication activity. C
Answer: B,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 # 89
......
Salesforce Certified Integration Architect exam is a rigorous test that covers a wide range of integration topics, from data integration to application integration and everything in between. Candidates must have a deep understanding of the Salesforce platform and its various APIs to pass Integration-Architect exam. They must also be able to design and implement scalable, secure, and reliable integration solutions that meet the business requirements.
Most Reliable Salesforce Integration-Architect Training Materials: https://www.prepawayete.com/Salesforce/Integration-Architect-practice-exam-dumps.html
The Realest Study Materials Integration-Architect Dumps: https://drive.google.com/open?id=1hdoLM039QSuyBFDrdaNvygby5T4wk4sg