custom picklist field, Food_Preference__c, exist on a custom object. The picklist contains the following options: 'Vegan','Kosher','No Preference'. The developer must ensure a value is populated every time a record is created or updated. What is the most efficient way to ensure a value is selected every time a record is saved?
Suggested Answer: C
Get Premium DEX-450 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
11 comments · newest first
KR
Kris
12 months ago
Not sure about D, feels like a workaround.
TA
Tammy
12 months ago
Wait, can you really just set it as required on the layout?
ED
Edwin
12 months ago
A won't guarantee a selection, that's risky!
DE
Delmy
1 year ago
I think B could work too, but C is cleaner.
CA
Carey
1 year ago
C is the best option, makes it mandatory.
SH
Sheridan
1 year ago
I think marking it as Required on the page layout might not enforce it during updates, so I’m leaning towards the field definition option.
AN
Anglea
1 year ago
I feel like using the first value as a default could lead to issues if someone doesn't change it.
CA
Cary
1 year ago
I'm not entirely sure, but I think setting a validation rule might be overkill for this scenario.
NE
Nelida
1 year ago
I remember we discussed that marking a field as Required in the field definition is a solid way to ensure a value is always selected.
AL
Alease
1 year ago
Hmm, I'm a bit unsure about this one. The wording of the answers is tripping me up. Let me think this through step-by-step.
KA
Kaycee
1 year ago
Okay, I've got a strategy for this. Since the question mentions Kusto queries, I'm guessing the answer is a Log Analytics workspace. That would allow me to use the powerful Kusto query language to analyze the audit logs. And it should minimize administrative effort compared to setting up something like an event hub.