New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Certified B2C Commerce Architect (Arch-303) Exam - Topic 4 Question 70 Discussion

Actual exam question for Salesforce's Salesforce Certified B2C Commerce Architect (Arch-303) exam
Question #: 70
Topic #: 4
[All Salesforce Certified B2C Commerce Architect (Arch-303) Questions]

The Client wants to have a flashsate on a few products every day. These products are sold through B2C Commerce as well as an in store Point of Sale system that it tied to the same inventory.

An Architect analyzes the following proposed solution:

Inventory feed w*l continue to run dailybut add a web-service call to compare and update B2C Commerce inventory in real time during checkout after a flash product's inventory reaches a threshold.

Which two risks should the Architect communicate to the Client about this solution?

Choose 2 answers

Show Suggested Answer Hide Answer
Suggested Answer: A, B

The risks associated with the proposed real-time inventory update solution during flash sales are:

Option A (The default rate limiter configuration for the web-service could cause the web-service to return an exception during high traffic): This is a critical risk because high traffic during flash sales could exceed the rate limits set for the web-service, leading to exceptions and potentially failing to update inventory in real-time.

Option B (If the external hosted web-service is unreliable, it could be a point of failure in the site's order placement flow): Reliance on an external web-service for crucial operations like inventory updates introduces a risk of downtime or performance issues if the service is unreliable, directly impacting the ability to complete orders during peak sales periods.

Both risks could severely disrupt operations during critical sales events, suggesting a need for robust contingency plans and potentially reevaluating the solution architecture to ensure reliability.


Contribute your Thoughts:

0/2000 characters
William
1 day ago
Totally agree with A) and B), those could really mess things up!
upvoted 0 times
...
Rolande
7 days ago
C) makes sense, too many calls could slow everything down.
upvoted 0 times
...
Sabra
12 days ago
I think B) is a big concern too, unreliable services can ruin sales.
upvoted 0 times
...
Loreen
17 days ago
A) is definitely a risk, high traffic can break things.
upvoted 0 times
...
Crista
22 days ago
Haha, this sounds like a disaster waiting to happen. I'd be worried about all of them - the web service, the performance hits, the whole nine yards. Good luck to whoever has to deal with this!
upvoted 0 times
...
Dusti
27 days ago
C and D are the ones I'm worried about. If the threshold is too low, it'll be calling the web service constantly, and the daily inventory job could really tank performance.
upvoted 0 times
...
Kathryn
1 month ago
A and B for sure. The rate limiter and an unreliable web service could both cause major issues during high traffic. Gotta watch out for those.
upvoted 0 times
...
Rolland
1 month ago
I feel like option D might not be as critical since the daily job runs regardless, but it could still affect performance during regular sales.
upvoted 0 times
...
Nobuko
1 month ago
I practiced a similar question, and I think option C is important too. If the threshold is hit too often, it could slow down the site, right?
upvoted 0 times
...
Joye
2 months ago
I'm not entirely sure, but I think if the external web-service fails, it could really mess up the checkout process. That makes option B a risk we should highlight.
upvoted 0 times
...
Martin
2 months ago
I remember we discussed the potential issues with web-service calls during high traffic. Option A seems like a valid concern.
upvoted 0 times
...
Carmelina
2 months ago
I'm a little confused by this one. The daily inventory job running even during non-flash sale periods - is that really a risk? I mean, it's just running the job, right? And the inventory threshold triggering too many web service calls, how would that impact performance? I feel like I'm missing something here, I'll have to think it through more.
upvoted 0 times
...
Andree
2 months ago
B and C seem like the most obvious risks to me. The web service could be a point of failure, and if the threshold is reached too often, it could really slow things down.
upvoted 0 times
...
Mirta
2 months ago
I think option A is a major risk. High traffic could break the service.
upvoted 0 times
...
Son
2 months ago
Okay, let's see. The default rate limiter on the web service could definitely be an issue during high traffic, that's a good catch. And if the external service is unreliable, that's a single point of failure that could really cause problems. I think I'd focus on those two risks and try to come up with some mitigation strategies.
upvoted 0 times
...
Sean
3 months ago
D) really? Daily jobs affecting performance even when not in flash sales?
upvoted 0 times
...
Genevive
3 months ago
Hmm, this is a tricky one. I'm a bit concerned about the reliability of the external web service - if that goes down, it could really disrupt the whole order flow. And if the inventory threshold triggers the web service calls too often, that could definitely slow things down. I'd want to do some load testing to see how it holds up.
upvoted 0 times
...
Candra
3 months ago
I think the key risks here are the potential performance issues, like the web service call causing problems during high traffic or the daily inventory job impacting performance even when there's no flash sale. I'd want to dig into the details of the web service and the inventory job to understand how they could be optimized.
upvoted 0 times
Kristel
3 months ago
True, especially during non-flash sales.
upvoted 0 times
...
...

Save Cancel