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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Salesforce Certified B2C Commerce Cloud Developer (Comm-Dev-101) Exam - Topic 1 Question 94 Discussion

Actual exam question for Salesforce's Salesforce Certified B2C Commerce Cloud Developer (Comm-Dev-101) exam
Question #: 94
Topic #: 1
[All Salesforce Certified B2C Commerce Cloud Developer (Comm-Dev-101) Questions]

A developer working on a multi country site is asked to store country specific data that drives the creation of a country selector. Examples of the data stored are:

Pricebook to be used

Image URL for country flag

The data used in staging also applies in production, but only for this site.

Which approach should the developer take to implement these requirements?

Show Suggested Answer Hide Answer
Suggested Answer: B

by Paul at Aug 03, 2025, 03:01 PM

Limited Time Offer

25%

Off

Get Premium Salesforce Certified B2C Commerce Cloud Developer (Comm-Dev-101) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Deeanna
2 months ago
I think B is the most flexible for future changes.
upvoted 0 times
...
Noah
2 months ago
Wait, can we really use staging data in production?
upvoted 0 times
...
Nadine
2 months ago
I disagree, A could be more efficient for localization.
upvoted 0 times
...
Von
2 months ago
Option B seems like the best choice for custom data.
upvoted 0 times
...
Dyan
3 months ago
C is interesting, but not sure if it scales well.
upvoted 0 times
...
Julieta
3 months ago
I feel like using a Custom Object is the safest bet here, but I wonder if there are any limitations I should be aware of when it comes to data retrieval.
upvoted 0 times
...
Sanda
3 months ago
I'm a bit confused about whether content assets would be sufficient for storing this kind of data. It seems like they might not be as structured as needed.
upvoted 0 times
...
Danilo
4 months ago
I remember practicing a question similar to this, and I think creating a site-specific Custom Object might be the right approach since it allows for more flexibility.
upvoted 0 times
...
Shenika
4 months ago
I think extending the Locale System Object could work, but I'm not entirely sure if it’s the best way to handle country-specific data.
upvoted 0 times
...
Maynard
4 months ago
Hmm, I'm leaning towards option B as well. Creating a custom object seems like the most flexible and maintainable way to handle this. I'd want to make sure it's replicable across environments, but that should be doable.
upvoted 0 times
...
Buddy
4 months ago
I think option C might be the simplest solution, creating site-specific content assets to store the data. That way, we don't have to worry about custom objects or extending existing systems. But I'm not sure if that's the most robust approach in the long run.
upvoted 0 times
...
Adrianna
4 months ago
I'm a bit confused on the requirements here. Do we need to store the data in a way that's specific to this site, or should it be more broadly applicable? I'm not sure if extending the Locale System Object is the right call.
upvoted 0 times
...
Derick
5 months ago
Okay, let's see. I'm leaning towards option B - creating a replicable, site-specific Custom Object. That seems like the most flexible and scalable solution for storing the country-specific data.
upvoted 0 times
...
Tegan
5 months ago
Hmm, this looks like a tricky one. I'll need to think through the different options carefully to make sure I pick the best approach.
upvoted 0 times
...
Virgie
5 months ago
If I had a dollar for every time I've seen developers try to shoehorn cusVirgie data into the core system, I'd be a rich man. Option B all the way, folks.
upvoted 0 times
...
Marget
5 months ago
Option A sounds like a recipe for disaster. Who wants to mess with the core system just to store some country flags? I'm with Janet on this one - option B is the way to go.
upvoted 0 times
Josphine
1 month ago
Plus, it keeps everything organized for each site!
upvoted 0 times
...
Beckie
2 months ago
Custom objects are easier to manage too.
upvoted 0 times
...
Cammy
2 months ago
I agree, messing with the core system can lead to issues.
upvoted 0 times
...
Ressie
3 months ago
Option B seems more flexible and safer.
upvoted 0 times
...
...
Christiane
6 months ago
Ha! Extending the Locale System Object? That's like using a sledgehammer to crack a nut. Definitely going with option B for this one.
upvoted 0 times
...
Beata
6 months ago
Option C seems like a good idea to me. Storing the data in site-specific content assets will keep everything organized and separate from the core system.
upvoted 0 times
Levi
5 months ago
I agree, it would make it easier to manage and update the country-specific data without affecting the core functionality.
upvoted 0 times
...
Deeann
5 months ago
Option C seems like a good idea to me. Storing the data in site-specific content assets will keep everything organized and separate from the core system.
upvoted 0 times
...
...
Malika
7 months ago
I disagree, I believe option B is more suitable.
upvoted 0 times
...
Janet
7 months ago
I think option B is the way to go. Creating a custom object specifically for this site will make it easy to manage and update the country-specific data as needed.
upvoted 0 times
...
Polly
7 months ago
I think option A is the best approach.
upvoted 0 times
...

Save Cancel