BlackFriday 2024! 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 Development Lifecycle and Deployment Architect Topic 3 Question 48 Discussion

Actual exam question for Salesforce's Development Lifecycle and Deployment Architect exam
Question #: 48
Topic #: 3
[All Development Lifecycle and Deployment Architect Questions]

Universal Containers (UC) had added a Service team to the Salesforce Platform. The

Service team would like to have a few dozen of the service centers entered into the system as

technical reference dat

a. The service centers are made searchable in many different web forms

and rather independent from all other business entities. In the past, they had to manually add any

new service centers in each sandbox in the code migration path, they would like to eliminate the

manual work if it is possible.

What is an optimal way to accomplish this requirement?

Show Suggested Answer Hide Answer
Suggested Answer: D

by Shonda at Sep 18, 2024, 04:38 AM

Limited Time Offer

25%

Off

Get Premium Development Lifecycle and Deployment Architect Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Gabriele
20 days ago
I'm partial to Option D. Custom metadata types are like the Rolls-Royce of Salesforce metadata, and they're perfect for this use case. Plus, they're super elegant, like a well-tailored suit.
upvoted 0 times
...
Corazon
21 days ago
Option A is the answer. Hierarchical custom settings are the go-to for this kind of static reference data. Plus, they're super easy to use and maintain.
upvoted 0 times
...
Lino
22 days ago
Option B is the way to go. List custom settings are perfect for this kind of data, and they're super easy to manage.
upvoted 0 times
Mariann
3 days ago
A) Add the service centers to a hierarchical custom settings.
upvoted 0 times
...
Marguerita
11 days ago
B) Add the service centers to a list custom settings.
upvoted 0 times
...
...
Lamar
1 months ago
That's a good point, Nana. I see the benefits of hierarchical custom settings as well. It seems like both options A and D could work well for this requirement.
upvoted 0 times
...
Stefania
2 months ago
I'd probably go with Option C. Creating a custom object gives you more flexibility in terms of managing the service centers, and it's a straightforward solution.
upvoted 0 times
...
Nana
2 months ago
I disagree, I believe option A is more suitable as hierarchical custom settings can be accessed easily by different components and are also customizable.
upvoted 0 times
...
Merilyn
2 months ago
Option D seems like the way to go. Custom metadata types are designed for this kind of use case, and they allow for easy deployment across sandboxes.
upvoted 0 times
Shantell
11 days ago
D) Add all of the service centers to a custom metadata type.
upvoted 0 times
...
Charlie
11 days ago
It sounds like custom metadata types will save a lot of time and effort for the Service team at Universal Containers.
upvoted 0 times
...
Roslyn
12 days ago
C) Define a brand-new custom object with a picklist field to host all of the service centers.
upvoted 0 times
...
Maurine
12 days ago
I agree, custom metadata types are definitely the best option for managing data like service centers.
upvoted 0 times
...
Venita
29 days ago
B) Add the service centers to a list custom settings.
upvoted 0 times
...
Leonie
1 months ago
A) Add the service centers to a hierarchical custom settings.
upvoted 0 times
...
Tamekia
1 months ago
Option D seems like the way to go. Custom metadata types are designed for this kind of use case, and they allow for easy deployment across sandboxes.
upvoted 0 times
...
...
Lamar
2 months ago
I think option D is the best choice because custom metadata types can be easily deployed across different environments without manual work.
upvoted 0 times
...

Save Cancel