MENU
An Architect has been approached by the Business with a request to create a custom product finder. The finder would initially be available ononly one site, and would eventually be extended to be available on all sites the Business maintains. There is a requirement that these wrings art also available to be used in a Job context for export to other systems.
Each site will have a differentcategory avertable for use by the product finder.
Where should the Architect store the custom settings for use on both the storefront and in a job context?
Suggested Answer: B
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
37 comments · newest first
MA
Macy
11 months ago
I didn't realize there were so many options!
DE
Delpha
11 months ago
Wait, why not just use D for a broader scope?
TI
Timothy
12 months ago
C seems too limited for what they need.
LI
Lizbeth
12 months ago
I disagree, B could be more flexible for job contexts.
EL
Elke
1 year ago
I think option A makes the most sense for site-specific settings.
BE
Berry
1 year ago
Category custom attributes seem like they could be useful, but I’m not sure if they’re flexible enough for both storefront and job contexts. I might lean towards a Custom Object instead.
LO
Loreta
1 year ago
I feel like we had a practice question about storing settings, and I think it was about using Custom Objects. But I can’t recall if it was site-specific or organizational.
JO
Johnetta
1 year ago
I’m not entirely sure, but I think Jobs Framework parameters could work too. They seem relevant for job contexts, but I’m worried about how they integrate with storefronts.
IV
Ivan
1 year ago
I remember we discussed the importance of scope in our last class. I think a Custom Object with a Site Scope might be the right choice since it’s specific to each site.
AD
Adelina
1 year ago
I'm leaning towards Option D, the Custom Object with an Organizational Scope. That seems like it would allow the settings to be accessed across the different sites and in the job context.
FL
Floyd
1 year ago
Option A looks promising since it mentions a Site Scope, which could work for the different categories on each site. But I'm not sure if that would also support the job context requirement.
SH
Sheron
1 year ago
Hmm, I'm a bit confused by the different scopes mentioned in the options. I'll need to think carefully about which one would best support the use cases described in the question.
EV
Eveline
1 year ago
This seems like a straightforward question about where to store custom settings for a product finder. I think the key is to consider the requirement that the settings need to be used in both the storefront and a job context.
ME
Melissa
1 year ago
Okay, let me see here. I remember learning about stateless autoconfiguration and DHCPv6, so I think I have a good handle on this. I'll double-check my understanding before selecting the answers.
BE
Bette
1 year ago
Alright, I've got a strategy. I'll read through the options and try to visualize what each one would do to the system.
TI
Tiera
1 year ago
Hey, at least it's not a 'customer locator'! That would be a real headache to implement.
GL
Glory
1 year ago
Hold up, did someone say 'product finder'? I'm just imagining a lost shopper wandering around the store, asking the ceiling: 'Where can I find the widgets?'
DE
Desmond
1 year ago
D) Custom Object with an Organizational Scope
LE
Leanna
1 year ago
C) Category custom attributes
GR
Gretchen
1 year ago
B) Jobs Framework parameters
EL
Eladia
1 year ago
A) Custom Object with a Site Scope
JE
Jettie
1 year ago
Hmm, I'm not sure. I'm leaning towards option C - using Category custom attributes might be a simpler solution that still meets the requirements.
PE
Pearly
1 year ago
It's definitely worth considering as a simpler solution.
AD
Adaline
1 year ago
I agree, using Category custom attributes seems like a good choice.
DE
Delisa
1 year ago
I think option C could work well for this scenario.
SH
Shawnna
1 year ago
Option B seems like the obvious choice here. The Job Framework is designed for this kind of use case, where we need to share settings across different contexts.
MA
Margo
2 years ago
I think option D is the way to go. Storing the custom settings in a Custom Object with an Organizational Scope ensures that they can be accessed across multiple sites and in a job context.
CO
Cordelia
1 year ago
Definitely, storing the settings in an Organizational Scope Custom Object makes it easier to manage and use them in different contexts.
DE
Denny
1 year ago
Yes, option D provides the flexibility needed for accessing the settings across multiple sites and in a job context.
MI
Milly
1 year ago
I agree, option D seems like the best choice for storing the custom settings.
MA
Malcom
1 year ago
D) Custom Object with an Organizational Scope
BE
Bettina
1 year ago
C) Category custom attributes
CH
Christa
1 year ago
B) Jobs Framework parameters
AL
Alecia
1 year ago
A) Custom Object with a Site Scope
LA
Lashawnda
2 years ago
I disagree. I believe storing the settings in a Custom Object with an Organizational Scope would be better for scalability and consistency across all sites.
PR
Princess
2 years ago
I agree with Izetta. Storing the settings in a Custom Object with a Site Scope makes sense for easy access and management.
IZ
Izetta
2 years ago
I think the Architect should store the custom settings in a Custom Object with a Site Scope.