Deal of The Day! 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 Exam B2C Commerce Architect Topic 3 Question 42 Discussion

Actual exam question for Salesforce's B2C Commerce Architect exam
Question #: 42
Topic #: 3
[All B2C Commerce Architect Questions]

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?

Show Suggested Answer Hide Answer
Suggested Answer: B

by Mitsue at Jun 22, 2024, 12:06 AM

Limited Time Offer

25%

Off

Get Premium B2C Commerce Architect Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Tiera
28 days ago
Hey, at least it's not a 'customer locator'! That would be a real headache to implement.
upvoted 0 times
...
Glory
29 days 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?'
upvoted 0 times
Gretchen
6 days ago
B) Jobs Framework parameters
upvoted 0 times
...
Eladia
14 days ago
A) Custom Object with a Site Scope
upvoted 0 times
...
...
Jettie
1 months 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.
upvoted 0 times
Delisa
5 days ago
I think option C could work well for this scenario.
upvoted 0 times
...
...
Shawnna
1 months 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.
upvoted 0 times
...
Margo
1 months 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.
upvoted 0 times
Malcom
2 days ago
D) Custom Object with an Organizational Scope
upvoted 0 times
...
Bettina
6 days ago
C) Category custom attributes
upvoted 0 times
...
Christa
9 days ago
B) Jobs Framework parameters
upvoted 0 times
...
Alecia
15 days ago
A) Custom Object with a Site Scope
upvoted 0 times
...
...
Lashawnda
2 months 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.
upvoted 0 times
...
Princess
2 months ago
I agree with Izetta. Storing the settings in a Custom Object with a Site Scope makes sense for easy access and management.
upvoted 0 times
...
Izetta
2 months ago
I think the Architect should store the custom settings in a Custom Object with a Site Scope.
upvoted 0 times
...

Save Cancel