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 Cloud Developer (Comm-Dev-101) Exam - Topic 13 Question 76 Discussion

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

Universal Containers wants to associate a region code value with an order to indicate the general area of its destination. This region code must be accessible whenever the order history is displayed.

What is required to accomplish this?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

0/2000 characters
Shawna
3 months ago
D could work, but it might not be the best option for tracking.
upvoted 0 times
...
Lilli
3 months ago
Wait, can you really store it in a session variable? That seems risky.
upvoted 0 times
...
Sharika
3 months ago
C sounds unnecessary, why complicate it?
upvoted 0 times
...
Tuyet
4 months ago
I disagree, A seems more efficient for quick access.
upvoted 0 times
...
Gretchen
4 months ago
B is the way to go! Custom attributes are perfect for this.
upvoted 0 times
...
Mitzie
4 months ago
I’m leaning towards option B, but I’m a bit confused about whether a custom object type is necessary for this scenario.
upvoted 0 times
...
Denise
4 months ago
Storing the region code in the geolocation attribute sounds familiar, but I wonder if that would actually allow us to display it in the order history.
upvoted 0 times
...
Nohemi
4 months ago
I remember a similar question where we had to store additional information with an order. I feel like using a session variable might not be persistent enough for this case.
upvoted 0 times
...
Ciara
5 months ago
I think we need to define a custom attribute on the Order object for the region code, but I'm not entirely sure if that's the best approach.
upvoted 0 times
...
Leeann
5 months ago
I think the custom attribute is the way to go here. It'll keep the region code directly associated with the order, which is exactly what the question is asking for.
upvoted 0 times
...
Micaela
5 months ago
The geolocation system attribute might work, but I'm not sure if that's the intended use case. I'll double-check the details on that one.
upvoted 0 times
...
Talia
5 months ago
Storing the region code in a session variable doesn't seem like the right approach since we need it to be accessible in the order history. I'm leaning towards the custom attribute solution.
upvoted 0 times
...
Judy
5 months ago
Hmm, I'm not sure about this one. I'm debating between the custom attribute and the custom object type options. I'll need to think it through a bit more.
upvoted 0 times
...
Alline
5 months ago
This seems pretty straightforward. I think the best approach would be to define a custom attribute on the Order object to store the region code.
upvoted 0 times
...
Pauline
5 months ago
Okay, I think I've got this. The question is asking for two possible solutions, so I'll need to choose two of the options provided. Let me take another look and see which ones make the most sense.
upvoted 0 times
...
Daniela
10 months ago
B is the clear winner here. Anything else would just be a convoluted way to achieve the same result. Though I do wonder if the folks at Universal Containers ever considered just using carrier pigeons instead of orders...
upvoted 0 times
...
Loreta
10 months ago
Option B is definitely the most straightforward and logical solution. Can't go wrong with that one. Now, where's the coffee break?
upvoted 0 times
...
Rana
10 months ago
Haha, storing the region code in the geolocation attribute? That's about as useful as trying to find Waldo in a haystack!
upvoted 0 times
Yolande
8 months ago
C) Define a custom object type to store the username with the region code.
upvoted 0 times
...
Bronwyn
8 months ago
B) Define a custom attribute on the Order system object type to store the region code value.
upvoted 0 times
...
Roxanne
8 months ago
A) Store the region code value in a session variable.
upvoted 0 times
...
...
Paz
10 months ago
I agree, B is the way to go. Storing it in a session variable or a separate custom object would be overkill and not the best approach.
upvoted 0 times
Freida
8 months ago
B is definitely the right choice. It keeps the region code value easily accessible when viewing order history.
upvoted 0 times
...
Helga
9 months ago
Definitely, using a custom attribute on the Order system object type is the way to go. It keeps things organized.
upvoted 0 times
...
Miesha
9 months ago
I agree, storing it in a session variable would not be ideal. B seems like the most efficient choice.
upvoted 0 times
...
Barney
10 months ago
I think B is the best option. It makes sense to define a custom attribute on the Order system object type.
upvoted 0 times
...
...
Paulina
10 months ago
Option B seems to be the right choice here. Storing the region code as a custom attribute on the Order object makes the most sense since it needs to be accessible in the order history.
upvoted 0 times
...
Olive
10 months ago
I believe option B is the best choice because it allows easy access to the region code value when needed.
upvoted 0 times
...
Ashton
11 months ago
I agree with Charolette. Storing the region code value in a session variable might not be accessible when the order history is displayed.
upvoted 0 times
...
Charolette
11 months ago
I think we should define a custom attribute on the Order system object type to store the region code value.
upvoted 0 times
...

Save Cancel