Halloween Special 2026! Get Up to 25% OFF Practice Questions! Limited Time - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Certified B2C Commerce Architect (Arch-303) Exam - Topic 3 Question 26 Discussion

Posted by Vincenza on Sep 02, 2023 at 07:13 AM

A third party survey provider offers both an API endpoint for individual survey data and an SFTP server endpoint that can accept batch survey dat

a. The initial implementation of the integration includes

1.Marking the order as requiring a survey before order placement

2. On the order confirmation pace, the survey form is displayed for the customer to fill

3. The data is sent to the survey provider API, and the order it marked as not requiring a survey

Later it was identified that this solution is not fit for purpose as the following issues and additional requirements were identified:

1. If the API call fails, the corresponding survey data is lost. The Business requires to avoid data loss.

2. Some customers skipped the form. The Business require sending a survey email to such customers.

3. The Order Management System (OMS) uses a non-standard XML parser it did not manage to parse orders with the survey, until the survey attribute was manually removedfrom the xml.

How should the Architect address the issues and requirements described above?

Suggested Answer: D, E

Get Premium Salesforce Certified B2C Commerce Architect (Arch-303) Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
36 comments · newest first
MO
Mozell 11 months ago
I like option A, but I'm worried about the session data getting lost if there's a crash.
JA
Jacquline 11 months ago
Wait, why not just fix the XML parser instead of all these workarounds?
MA
Malissa 12 months ago
I disagree, option D sounds risky, relying on real-time data could lead to more issues.
CO
Cordelia 12 months ago
I think option C is better, capturing data in a custom object gives more flexibility.
ED
Edison 1 year ago
Option B seems solid, using a custom object for data storage is smart.
GA
Gayla 1 year ago
I recall that we talked about the need for batch processing in some scenarios. Option B sounds like it could handle that well, but I’m not confident about the custom object management.
LA
Lavonda 1 year ago
I think we practiced a similar question where we had to handle data loss. Option A seems to address that, but I'm worried about the complexity of managing session attributes.
HO
Hoa 1 year ago
I'm not entirely sure, but I feel like capturing the survey data in a session could lead to issues if the session expires. Maybe option C is safer?
CA
Camellia 1 year ago
I remember we discussed the importance of data persistence in case of API failures. I think option B might be the best choice for that reason.
MA
Maira 1 year ago
I think Option C looks the most promising. Storing the survey data in a custom object and using a job to reprocess it on failure seems like a solid approach. And we can use that same object to trigger the email for skipped surveys.
RO
Rosalyn 1 year ago
The key here is to ensure we don't lose any survey data, even if the API call fails. I like the idea of using a custom object to store the data and reprocess it later.
TE
Telma 1 year ago
This seems like a complex problem with a lot of moving parts. I'd want to carefully review the requirements and think through the different options before deciding on a solution.
FR
Franchesca 1 year ago
Hmm, the XML parsing issue is tricky. I'm not sure I'd want to rely on the OMS team to update their parser - that could take a while. Maybe we can find a way to work around that in our own integration.
JA
Jame 1 year ago
Detention seems like the most logical answer here, since it's about merchants detaining or holding onto shoplifters or stolen assets. I'll go with that.
PE
Pearlie 1 year ago
I think I've got a good handle on the differences. I'll make sure to highlight the three most important distinctions in my answer.
MA
Malcolm 1 year ago
This seems straightforward to me. The underlined text doesn't accurately capture the benefit of using a transaction, so I'll select option B.
RA
Raymon 1 year ago
The OMS team must be using the 'Vogon Poetry Parser' - no wonder they can't handle the survey data!
BR
Brock 1 year ago
↳ replying to Raymon
D) Send the survey data to the API endpoint in real-time until the survey data is successfully captured. Instruct the OMS development team to update their XML parser, use the Order survey attribute to send emails for the cases when the survey was skipped.
KE
Kent 1 year ago
↳ replying to Raymon
B) Create a custom object to store the survey data. Send to the API endpoint using a job. On success, remove the custom object. On failure, send the survey data with API from the next execution of the same job. Use the custom object to send emails for the cases when the survey was skipped.
CH
Chaya 1 year ago
↳ replying to Raymon
A) Create a custom session attribute when the survey is required. Send to the API endpoint in real-time. On failure, capture the survey data in the session and reprocess, use the session attribute to send emails for the cases when the survey was skipped.
DA
Dana 1 year ago
Option A is pretty clever, using the session to handle the skipped surveys. I wonder if that could lead to any session management issues, though.
LE
Leonida 1 year ago
↳ replying to Dana
User 3: Maybe there could be some session management issues to consider, but it's worth exploring further.
AV
Avery 1 year ago
↳ replying to Dana
User 2: I agree, it seems like a practical approach to avoid data loss.
RO
Rodrigo 1 year ago
↳ replying to Dana
User 1: Option A is a good solution for handling the skipped surveys.
FL
Flo 2 years ago
Option D is interesting, but relying on the OMS team to update their parser seems risky. I'd prefer a more self-contained solution.
KR
Kristofer 1 year ago
↳ replying to Flo
D: Option A does provide a comprehensive solution to the issues and requirements mentioned.
HI
Hillary 1 year ago
↳ replying to Flo
C: Option A does seem to cover all the bases and avoid relying on external teams for updates.
RE
Reena 1 year ago
↳ replying to Flo
B: I agree, Option A seems like a reliable and self-contained approach to address the issues.
OR
Oren 1 year ago
↳ replying to Flo
A: Option A sounds like a good solution. It captures survey data in case of failure and sends emails for skipped surveys.
AL
Alonzo 2 years ago
Option B looks good, but I'm worried about the performance impact of a job-based approach. What if the survey data volume is high?
GE
Gennie 1 year ago
↳ replying to Alonzo
True, if the survey data volume is high, it might affect the system. We should discuss this with the team.
GE
Gerald 1 year ago
↳ replying to Alonzo
I think option B is a good choice, but we need to consider the performance impact.
JE
Jesse 2 years ago
That's a good point, but option C also seems viable as it sends data in real-time and reprocesses it later if needed.
NA
Nadine 2 years ago
This is a complex problem, but I think Option C is the way to go. Creating a custom object to store the survey data and then reprocessing it on failure seems like the most robust solution.
ME
Meaghan 2 years ago
I disagree, I believe option B is more efficient as it uses a custom object to store survey data and sends it using a job.
JE
Jesse 2 years ago
I think option A is the best choice because it captures survey data in real-time and reprocesses it if the API call fails.
0/2000 characters

Save Cancel