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 Certified Platform Developer II (Plat-Dev-301) Exam - Topic 2 Question 120 Discussion

Actual exam question for Salesforce's Salesforce Certified Platform Developer II (Plat-Dev-301) exam
Question #: 120
Topic #: 2
[All Salesforce Certified Platform Developer II (Plat-Dev-301) Questions]

A developer is asked to develop a new AppFxchange application. A feature of the program creates Survey records when a Case reaches a certain stage and is of a certain Record Type. This feature needs to be configurable, as different Salesforce instances require Surveys at different times. Additionally, the out-of-the-box AppExchange app needs to come with a set of best practice settings that apply to

most customers.

What should the developer use to store and package the custom configuration settings for the app?

Show Suggested Answer Hide Answer
Suggested Answer: C

Custom metadata is best for storing configurable settings. It's deployable, packageable, and upgradeable. Allows different configurations for different instances.


by Virgie at Nov 19, 2025, 09:21 PM

Limited Time Offer

25%

Off

Get Premium Salesforce Certified Platform Developer II (Plat-Dev-301) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Doyle
5 days ago
Best practice settings need to be reusable, so Custom metadata fits perfectly.
upvoted 0 times
...
Ivan
10 days ago
Custom metadata allows for packaging and deployment easily.
upvoted 0 times
...
Bulah
15 days ago
Custom labels? No way, they’re for translations, not settings.
upvoted 0 times
...
Ethan
20 days ago
Custom objects would be overkill for just configuration.
upvoted 0 times
...
Whitley
25 days ago
Agreed! Custom settings seem too limited for this.
upvoted 0 times
...
Karina
1 month ago
Surprised this isn't just using Custom labels for simplicity!
upvoted 0 times
...
Brandon
1 month ago
Custom objects seem too heavy for just config settings.
upvoted 0 times
...
Deonna
2 months ago
Wait, can Custom settings even handle this?
upvoted 0 times
...
Roxane
2 months ago
Totally agree, it’s perfect for packaging settings!
upvoted 0 times
...
Jackie
2 months ago
B) Custom settings is the classic choice. Can't go wrong with the tried and true.
upvoted 0 times
...
Nathan
2 months ago
D) Custom labels? Haha, that's like using a screwdriver to hammer a nail.
upvoted 0 times
...
Reta
3 months ago
A) Custom objects? Really? That's overkill for just configuration settings.
upvoted 0 times
...
Mabel
3 months ago
C) Custom metadata is the best option. It's more robust and scalable than custom settings.
upvoted 0 times
...
Quentin
3 months ago
I feel like custom objects might be too heavy for this purpose. It seems like we need something lighter and more flexible.
upvoted 0 times
...
Paola
3 months ago
I’m not entirely sure, but I remember we discussed custom settings and how they can be used for configuration. Could that be an option too?
upvoted 0 times
...
Allene
3 months ago
I think we might have covered something similar in class about storing configuration settings. Custom metadata could be the right choice since it’s meant for packaging.
upvoted 0 times
...
Herman
3 months ago
Custom labels might be a good option too, especially for storing the default "best practice" settings. That keeps the configuration data separate from the core app logic.
upvoted 0 times
...
Pearly
4 months ago
I'm leaning towards custom objects. That way the configuration data can be stored and managed more flexibly, even if it's not as tightly integrated as custom settings.
upvoted 0 times
...
Isabella
4 months ago
Custom metadata sounds like it could work well here. It's designed for packaging up configuration data, and it seems like that's what this feature needs.
upvoted 0 times
...
Shaquana
4 months ago
I think Custom metadata is the way to go for this.
upvoted 0 times
...
Misty
4 months ago
B) Custom settings is the way to go. It's flexible and easy to configure.
upvoted 0 times
...
Tayna
5 months ago
I vaguely recall a practice question where custom metadata was highlighted for its ability to be deployed easily. That might be the best fit here.
upvoted 0 times
...
Orville
5 months ago
I think Custom metadata is the way to go. It's flexible.
upvoted 0 times
...
Felix
5 months ago
Hmm, I'm a bit confused on the difference between custom settings and custom metadata. I'll need to review those options more closely.
upvoted 0 times
...
Helene
5 months ago
I think I'd go with custom settings for this one. It seems like the best way to make the app configurable for different Salesforce instances.
upvoted 0 times
Matthew
4 months ago
I believe custom metadata would be a better choice. It's more flexible.
upvoted 0 times
...
...

Save Cancel