Salesforce Exam B2C Commerce Architect Topic 3 Question 42 Discussion

Actual exam question for Salesforce's B2C Commerce Architect exam

Question #: 42
Topic #: 3

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?

ACustom Object with a Site Scope

BJobs Framework parameters

CCategory custom attributes

DCustom Object with an Organizational Scope

Show Suggested 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

1 months ago

Hey, at least it's not a 'customer locator'! That would be a real headache to implement.

upvoted 0 times

...

Glory

1 months 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

11 days ago

B) Jobs Framework parameters

upvoted 0 times

...

Eladia

19 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

Pearly

4 days ago

It's definitely worth considering as a simpler solution.

upvoted 0 times

...

Adaline

5 days ago

I agree, using Category custom attributes seems like a good choice.

upvoted 0 times

...

Delisa

10 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

2 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

Cordelia

2 days ago

Definitely, storing the settings in an Organizational Scope Custom Object makes it easier to manage and use them in different contexts.

upvoted 0 times

...

Denny

3 days ago

Yes, option D provides the flexibility needed for accessing the settings across multiple sites and in a job context.

upvoted 0 times

...

Milly

4 days ago

I agree, option D seems like the best choice for storing the custom settings.

upvoted 0 times

...

Malcom

8 days ago

D) Custom Object with an Organizational Scope

upvoted 0 times

...

Bettina

12 days ago

C) Category custom attributes

upvoted 0 times

...

Christa

14 days ago

B) Jobs Framework parameters

upvoted 0 times

...

Alecia

21 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

3 months ago

I think the Architect should store the custom settings in a Custom Object with a Site Scope.

upvoted 0 times

...