Exam Integration-Architect Topic 6 Question 8 Discussion
Actual exam question for Salesforce's Integration-Architect exam
Question #: 8
Topic #: 6
Question #: 8
Topic #: 6
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?
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?
Suggested Answer: C Vote an answer
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]
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]
by Hugh at Aug 07, 2024, 11:27 PM
0
0
0
10
Comments
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Report Comment
Commenting
You can sign-up / login (it's free).