Latest 2026 Realistic Verified Integration-Architect Dumps - 100% Free Integration-Architect Exam Dumps
Get 2026 Updated Free Salesforce Integration-Architect Exam Questions and Answer
Salesforce Integration-Architect exam is designed to test your knowledge and expertise in integrating systems with Salesforce. Salesforce Certified Integration Architect certification is specifically designed for professionals who have experience in designing and implementing complex integration solutions. The Salesforce Integration-Architect certification enables professionals to demonstrate their ability to design and implement complex integration solutions using various tools and technologies.
NEW QUESTION # 57
Northern Trail Outfitters (NTO) wants to improve the quality of callouts from Salesforce to its REST APIs by adhering to RAML (REST API Markup Language) specifications. The RAML specs serve as interface contracts. Which design specification should the integration architect include to ensure that Apex REST API Clients' unit tests confirm adherence to the RAML specs?
- A. Call the HttpCalloutMock implementation from the Apex REST API Clients.
- B. Call the Apex REST API Clients in a test context to get the mock response.
- C. Require the Apex REST API Clients to implement the HttpCalloutMock.
Answer: C
Explanation:
In Salesforce, you cannot perform real HTTP callouts during unit tests. To test integration logic, developers must use the HttpCalloutMock interface to simulate the API's response. To ensure that the Apex code adheres to the RAML contract, the architect should require that the test mock implementation strictly follows the RAML specifications.
By requiring the Apex REST API Clients to implement the HttpCalloutMock (or more specifically, creating a mock class that implements it), the developer creates a controlled testing environment. The mock class should be coded to return a payload that matches the RAML-defined structure (fields, data types, and status codes). When the test runs, the Apex client receives this "contract-compliant" response. The unit test then uses assertions to verify that the Apex code correctly parses and handles this specific data structure.
Option B is technically imprecise; you don't "call" the mock from the client, you provide the mock to the test runtime using Test.setMock(). Option C describes the general process of testing but does not address the
"design specification" needed to ensure contract adherence. By mandating a mock implementation that mirrors the RAML contract, the architect ensures that if the API contract changes in the RAML file, the unit tests will fail if the Apex code is not updated to match, thereby maintaining high integration quality and preventing runtime errors.
NEW QUESTION # 58
Which WSDL should an architect consider when creating an integration that might be used for more than one salesforce organization and different metadata?
- A. Enterprise WSDL
- B. SOAP API WSDL
- C. Partner WSDL
- D. Corporate WSDL
Answer: C
Explanation:
Explanation
The Partner WSDL is the best option for creating an integration that might be used for more than one Salesforce organization and different metadata. The Partner WSDL is loosely typed and can reflect against any configuration of Salesforce. It is static and does not change if modifications are made to an organization's Salesforce configuration. Therefore, it is more flexible and adaptable than the Enterprise WSDL, which is strongly typed and bound to a specific configuration of Salesforce1 References: Differences between Salesforce provided WSDL files
NEW QUESTION # 59
A customer 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-points should an integration architect consider when choosing the integration pattern/mechanism?
Choose 3 answers
- A. Multi-language and multi-currency requirement
- B. Reporting and usability requirements
- C. System types - APIs, File systems, Email
- D. Data Volume and Processing volume
- E. Error handling mechanisms
Answer: C,D,E
Explanation:
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 choosing the 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 handle any 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 # 60
Northern Trail Outfitters (NTO) is planning to create a native employee-facing mobile app with the look and feel of Salesforce Lighting Experience. The mobile app needs to integrate with NTO's Salesforce org. Which Salesforce API should be used to implement this integration?
- A. Connect REST API
- B. REST API
- C. User Interface API
Answer: C
Explanation:
When building custom mobile or web applications that aim to replicate the look and feel of Salesforce Lightning Experience, the User Interface (UI) API is the architecturally recommended choice.
The UI API is specifically designed to provide the metadata and data needed to build high-fidelity user interfaces. Unlike the standard REST API (Option B), which returns raw record data, the UI API returns both data and metadata in a single response. This includes information about page layouts, field-level security, picklist values, and localized labels. By using the UI API, the mobile app can dynamically render fields according to the user's permissions and the organization's layout configurations, ensuring that the custom app stays in sync with changes made in Salesforce Setup without requiring code updates in the mobile app.
Connect REST API (Option A) is primarily used for Chatter, Communities (Experience Cloud), and CMS content, and while it is useful for those specific social features, it does not provide the layout and record-level metadata required for a full CRM interface. The UI API is the same underlying technology that powers the Salesforce mobile app and Lightning Experience itself. Therefore, utilizing this API allows NTO's developers to build a native app that perfectly mimics the Lightning Experience while reducing the amount of custom logic needed to handle complex Salesforce UI requirements.
NEW QUESTION # 61
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 # 62
Universal Containers (UC) currentlyowns a middleware tool and they have developed an API-led integration architecture with three API tiers. The first-tier interfaces directly with the systems of engagement, the second tier implements business logic and aggregates data, while the third-tierinterfaces directly with systems of record. Some of the systems of engagement will be a mobile application, a web application, and Salesforce.
UC has a business requirement to return data to the systems of engagement in different formats while also enforcing different security protocols.
What should an Integration Architect recommend to meet these requirements?
- A. Leverage an Identity Provider solution that communicates with the API tiers via SAML
- B. Implement an API gateway that allsystems of engagement must interface with first.
- C. Enforce separate security protocols and return formats at the second tier of the API-led architecture.
- D. Enforce separate security protocols and return formats at the first tier of the API-ledarchitecture.
Answer: B
Explanation:
Theintegration architect should recommend enforcing separate security protocols and return formats at the first tier of the API-led architecture. The first tier is also known as the experience layer, which is responsible for providing a tailored interface for each system of engagement. By enforcing security and format at this layer, the integration architect can ensure that each system of engagement can access the data in a secure and consistent way, without affecting the other layers.
References: [API-ledConnectivity]
NEW QUESTION # 63
A large enterprise customer operating in a high regulated industry is planning to implement Salesforce for customer facing associates in both Sales and Service, and back-office staff. The business processes that Salesforce supports are critical to the business.
Salesforce will be integrated to multiple back-office systems to provide a single interface for associates.
Reliability and monitoring of these integrations are required as associates support customers.
Which integration solution should the architect consider when planning the implementation?
- A. Architect Services in back-office systems to support callouts from Salesforce and build reliability, monitoring and reporting capabilities.
- B. Leverage Middleware for all back-office system integrations ensuring real time alerting, monitoring and reporting capabilities.
- C. Decouple back-office system callouts into separate distinct services that have inbuilt error logging and monitoring frameworks.
- D. Build a custom integration gateway to support back-office system integrations and ensure reliability and monitoring capabilities.
Answer: B
Explanation:
Leveraging Middleware for all back-office system integrations ensuring real time alerting, monitoring and reporting capabilities is the best integration solution for this scenario.Middleware is a software layer that acts as an intermediary between Salesforce and other systems, providing a common platform for data transformation, routing, orchestration, security, error handling, logging, and monitoring. Middleware can help to ensurereliability and performance of the integrations, as well as provide visibility and control over the integration processes. Middleware can also support various integration patterns and protocols, such as SOAP, REST, JMS, etc. Reference: Salesforce Integration Architecture Designer Resource Guide, page 14
NEW QUESTION # 64
What should an Architect recommend to ensure all integrations to the Northern Trail Outfitters company portal use SSL mutual authentication?
- A. Generate a Self-signed Certificate.
- B. Enable My Domain and SSL/TLS.
- C. Enforce SSL/TLS MutualAuthentication.
- D. Generate a CA-signed Certificate.
Answer: C
Explanation:
Explanation
This is because SSL/TLS mutual authentication is a security feature that 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 used for SSL/TLS mutual authentication, but it does not ensure that all integrations 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-signed certificate, 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 # 65
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) tool to 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, MDM, BI tool and Data Warehouse
- B. ERP, MDM, Data Warehouse, Invoices system
- C. ERP, Invoices system, Data Warehouse and BI Tool
- D. ERP, Inventory, Pricing Engine, Invoices system
Answer: D
NEW QUESTION # 66
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. 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.
- C. 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.
- D. Both Platform Events and Outbound Message offer declarative means for asynchronous near-real time needs. They aren't best suited for real-time integrations.
- E. 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.
Answer: A,B,C
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 # 67
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 by 10 different training accreditation verification agencies before providing training for the company. Each training accreditation agency has its own response time, which means it could take days to confirm a trainer. The company decided to automate the trainer accreditation verification process by integrating it with the agency's web service1s. What is the recommended approach to automa2te this process?3456
- A. Use middleware to handl7e the callout to the 10 different verific8ation services; the middleware will handle the business logic of con9solidating the verification resu10lt from the 10 services. Then, make a call-in to Salesforce and update the verification status to "verified".
- B. Use Salesforce External Service to make the callout; Salesforce External Service should check the verification agencies until the result is verified. Then, update the trainer status to "verified".
- C. Make an Apex callout using @future annotation to make the callout to all different agencies.
Answer: A
Explanation:
In this scenario, the primary architectural challenge is managing high-latency, multi-step orchestration involving 10 disparate external systems. Each agency has a varying response time that can span several days, making a synchronous "Request-Reply" pattern within Salesforce technically impossible due to transaction timeout limits (maximum 120 seconds).
The recommended approach is to leverage Middleware as the orchestration and state-management layer.
Middleware (such as an ESB or iPaaS) is specifically designed for Process Choreography. Salesforce initiates a single "Fire and Forget" request to the middleware. The middleware then takes responsibility for:
* Sequential or Parallel Callouts: Initiating the requests to all 10 verification agencies.
* Callback Management: Handling the asynchronous responses from each agency as they arrive over a period of days.
* Aggregation Logic: Consolidating the results and determining when the "Business Process" is complete (e.g., all 10 agencies have approved).
Once the consolidation logic is satisfied, the middleware performs a Remote Call-In to the Salesforce REST API to update the trainer's record. This pattern keeps Salesforce "clean" by moving complex, long-running orchestration logic off-platform, preventing the consumption of excessive Apex CPU time and ensuring that Salesforce only receives a single, final status update.
Option B (External Services) is unsuitable for a multi-day asynchronous process as it is designed for real- time, synchronous Flow actions. Option C (@future) is restricted by the same 120-second timeout and cannot handle the "waiting" state required for days of verification. Using middleware provides the necessary Quality of Service (QoS), durability, and error handling required for such a critical enterprise compliance process.
NEW QUESTION # 68
Northern Trail Outfitters (NTO) has recently implemented middleware for orchestration of services across platforms. The ERP system being used requires transactions be captured near real time at a REST endpoint initiated in Salesforce when creating an order object. Additionally, the Salesforce team has limited development resources and requires a low code solution.
Which two options will fulfill the use case requirements?
Choose 2 answers
- A. Use Remote Process Invocation fire and forget pattern on insert on the order object using Flow Builder.
- B. Implement a Workflow Rule with Outbound Messaging to send SOAP messages to the designated endpoint.
- C. Use a process builder to create a Platform Event, selecting the record type as the Platform Event Name on insert of record.
- D. Implement Change Data Capture on the order object and leverage the replay Id in the middleware solution.
Answer: A,D
NEW QUESTION # 69
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. 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.
- C. 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.
- D. Both Platform Events and Outbound Message offer declarative means for asynchronous near-real time needs. They aren't best suited for real-time integrations.
- E. 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.
Answer: A,B,C
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 # 70
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. Multi-language and multi-currency requirement
- B. Reporting and usability requirements
- C. System types - APIs, File systems, Email
- D. Data Volume and Processing volume
- E. Error handling mechanisms
Answer: C,D,E
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 # 71
Which two approaches will require the least amount of development effort?
Choose 2 answers
- A. Configure named credentials in the source org.
- B. Use the tooling API with Process Builder to insert leads in real time.
- C. Call the Salesforce REST API to insert the lead into the target system.
- D. Use the Composite REST API to aggregate multiple leads in a single call.
Answer: A,D
Explanation:
The two approaches that will require the least amount of development effort are configuring named credentials in the source org and using the Composite REST API to aggregate multiple leads in a single call. Named credentials are a type of metadata that store authentication information for accessing external services, such as the target Salesforce org. By using named credentials, you can simplify the code for making callouts and avoid hardcoding credentials or tokens. The Composite REST API is a resource that allows you to execute multiple REST API requests in a single call. You can use the Composite REST API to create, update, or delete up to 25 records in one request. This can reduce the number of API calls and improve performance.
References: [Named Credentials], [Composite Resources]
NEW QUESTION # 72
The URL for an external service has been changed without prior notice. The service provides up to date money exchange rates that is accessed several times from Salesforce and is a business critical function for end users.
Which two solutions shouldan Integration Architect recommend be implemented to minimize potential downtime for users in this situation?
Choose 2 answers
- A. Enterprise ESB
- B. Content Security Policies
- C. Remote Site Settings
- D. Named Credentials
Answer: A,D
Explanation:
Explanation
The best solutions for minimizing potential downtime for users in this situation are to use named credentials and an enterprise ESB. Named credentials allow you to store the URL and authentication parameters of an external service in one definition, and then use it in Apex callouts or declarative integrations. If the URL of the external service changes, you only need to update the named credential once, and all the integrations that use it will be updated automatically. An enterprise ESB is a middleware layer that acts as a broker between different systems and services. It can provide routing, transformation, orchestration, and monitoring capabilities for integrations. If the URL of an external service changes, you only need to update the ESB configuration once, and all the integrations that use it will be updated automatically. Option B is not correct because remote site settings only allow you to specify the domains that are allowed for callouts from your org. They do not store any authentication parameters or provide any routing or transformation capabilities. Option C is not correct because content security policies are used to control what resources can be loaded on a Visualforce or Lightning page. They do not store any authentication parameters or provide any routing or transformation capabilities. References:
Named Credentials
Streamline and Secure: Mastering Named Credentials in Salesforce
NEW QUESTION # 73
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. 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.
- C. Handle verification process error in the Verification Webservice API in case there isa connection issue to the Webservice if it responds with an error.
- D. Handle integration errors in the middleware in case the verification process is down, then the middleware should retry processing the request multiple times.
Answer: C
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 # 74
Universal Containers (UC) is currently managing a custom monolithic web service that runs on an on-premise server. This monolithic web service is responsible for Point-to-Point (P2P) integrations between:
* Salesforce and a legacy billing application
* Salesforce and a cloud-based Enterprise Resource Planning (ERP) application
* Salesforce and a data lake
UC has found that the tight interdependencies between systems are causing integrations to fail.
What should an integration architect recommend to decouple the systems and improve the performance of the integrations?
- A. Leverage modular design by breaking up the web service into smaller pieces for a microservice architecture.
- B. Use the Salesforce Bulk API when integrating back into Salesforce.
- C. Move the custom monolithic web service from on-premise to a cloud provider.
Answer: A
NEW QUESTION # 75
An integration architect has built a Salesforce application that integrates multiple systems and keeps them synchronized via Platform Events. What is taking place if events are only being published?
- A. The platform events are published immediately before the Apex transaction completes.
- B. The platform events are published after the Apex transaction completes.
- C. The platform events are being published from Apex.
Answer: B
Explanation:
The timing of Platform Event publishing is a critical detail for an Integration Architect, as it affects data consistency and transaction integrity. In Salesforce, the default and most common behavior for publishing Platform Events from Apex is "Publish After Commit." When an architect chooses the "Publish After Commit" setting (defined at the event level), the events are held in a buffer and are only released to the event bus after the Apex transaction completes successfully. This ensures that if the database transaction fails and rolls back, the event-which might trigger external actions- is never sent. This prevents "ghost" events where an external system is told to process data that was never actually saved to the Salesforce database.
The question implies a standard scenario where events are being "published" into the bus. In this state, the events have passed the transaction boundary. If the events were only "being published from Apex" (Option C), it doesn't describe the state of the delivery or the transaction. Option B is technically incorrect for standard event publishing logic, as Salesforce explicitly separates the event bus from the database commit to maintain atomicity.
Understanding this "After Commit" behavior is vital when designing synchronization patterns. If the architect requires the event to be sent regardless of whether the transaction succeeds (e.g., for logging a failure), they would need to configure the event as "Publish Immediately." However, in a standard synchronization use case where events are "only being published," it signifies that the source transaction has finalized, and the messages are now available for subscribers (like middleware or other Salesforce orgs) to consume.
NEW QUESTION # 76
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. A Default gateway restrictions
- B. Considerations for using Deterministic Encryption
- C. External gateway products in use
- D. Shield Platform Encryption Limitations
Answer: C
NEW QUESTION # 77
Northern Trail Outfitters uses a custom Java application to display code coverage and test results for all of their enterprise applicationsand is planning to include Salesforce as well.
Which Salesforce API should an Integration Architect use to meet the requirement?
- A. Tooling API
- B. Metadata API
- C. Analytics REST API
- D. SOAP API
Answer: A
Explanation:
Explanation
Option D is correct because Tooling API is the Salesforce API that can be used to retrieve code coverage and test results for Apex classes and triggers. Tooling API provides REST and SOAP interfaces to access metadata about code, execute tests, and get test results12 Option A is incorrect because SOAP API is a Salesforce API that can be used to create, retrieve, update, or delete records, but not to get code coverage and test results. SOAP API uses a WSDL file to define the parameters for accessing data through the API3 Option B is incorrect because Analytics REST API is a Salesforce API that can be used to access data from reports and dashboards, but not from code coverage and test results. Analytics REST API provides a programmatic way to interact with analytics features such as lenses, datasets, and dashboards4 Option C is incorrect because Metadata API is a Salesforce API that can be used to retrieve, deploy, create, update, or delete customization information, such as custom object definitions and page layouts, but not code coverage and test results. Metadata API is mainly used for development tools or backup tools5 References: 1: Introducing Tooling API 2: Tooling API Examples 3: SOAP API Developer Guide 4: Analytics REST API Developer Guide 5: Metadata API Developer Guide
NEW QUESTION # 78
......
Integration-Architect Dumps PDF and Test Engine Exam Questions: https://realdumps.prep4sures.top/Integration-Architect-real-sheets.html