Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam B2C Commerce Architect Topic 3 Question 39 Discussion

Actual exam question for Salesforce's B2C Commerce Architect exam
Question #: 39
Topic #: 3
[All B2C Commerce Architect 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:

Harrison
5 months ago
I'd say both A and B are the way to go. Gotta watch out for those rate limiters and flaky web services. Wouldn't want the site to crash and burn like a lit match in a hurricane!
upvoted 0 times
...
Leatha
6 months ago
Option D is a classic. Keeping the daily inventory job on top of the real-time updates? Talk about overkill. Might as well just have the website run on a hamster wheel!
upvoted 0 times
Melynda
4 months ago
Yeah, having both daily updates and real-time updates seems excessive. It could cause some serious performance issues.
upvoted 0 times
...
Alona
5 months ago
Option D is definitely a concern. It could really slow things down.
upvoted 0 times
...
...
Christiane
6 months ago
C is a good one too. Triggering the web service too often could really slow things down. Might as well just have a turtle-paced website during the flash sales.
upvoted 0 times
Gladys
5 months ago
User 2
upvoted 0 times
...
Caitlin
5 months ago
User 1
upvoted 0 times
...
...
Xochitl
6 months ago
B is the one I'm going with. An unreliable external web service is a recipe for disaster. Don't want my customers' orders getting stuck in limbo!
upvoted 0 times
Anthony
5 months ago
It's crucial to communicate this risk to the Client so they understand the potential impact on their customers' orders.
upvoted 0 times
...
Delfina
5 months ago
Definitely, we need to make sure the external web service is dependable before implementing this solution.
upvoted 0 times
...
Louisa
5 months ago
A) The default rate limiter configuration for the web-service could cause the web-service to return an exception during high traffic.
upvoted 0 times
...
Eleonore
6 months ago
B) If the external hosted web-service is unreliable. It could be a point of failure in the site's order placement flow.
upvoted 0 times
...
Andrew
6 months ago
I agree, B is a big risk. We can't afford to have orders stuck because of an unreliable web service.
upvoted 0 times
...
...
Meaghan
7 months ago
Option A looks legit. The web service could buckle under high traffic and cause issues during flash sales. Gotta watch out for those rate limiters!
upvoted 0 times
Zita
5 months ago
A: Agreed, better to be proactive and address any potential issues upfront.
upvoted 0 times
...
Yan
5 months ago
B: We should definitely communicate these risks to the Client before implementing the solution.
upvoted 0 times
...
Soledad
5 months ago
A: Good point, that could be a potential point of failure for the whole system.
upvoted 0 times
...
Mariko
6 months ago
B: And we also need to consider if the external web-service is reliable enough.
upvoted 0 times
...
Alysa
6 months ago
A: Totally, we don't want any exceptions causing issues for the clients.
upvoted 0 times
...
James
6 months ago
B: Yeah, we need to make sure the web-service can handle the traffic during flash sales.
upvoted 0 times
...
Sharika
6 months ago
A: Option A is definitely a valid concern. Those rate limiters can really impact performance.
upvoted 0 times
...
...

Save Cancel