Salesforce Certified Platform Administrator II Practice Questions

Salesforce Certified Platform Administrator II exam preparation

Salesforce Certified Platform Administrator II practice questions in English: 180 questions with explanations. The mock exam has 60 questions and 105 minutes.

Salesforce Certified Platform Administrator II free question 7 / 10 · Domain 5: Data and Analytics Management

An administrator creates the custom picklist field Work Location Type on the User object. Values should be present regardless of how the user record is saved, including through the UI, Just-in-Time user creation for SSO, and API updates. The plan is to select Required in the field definition. Which statement matches Salesforce Help?

  1. The field can be made required in its definition, but on the User object a default value must be specified rather than left blank
  2. The field can be made required in its definition, but picklist fields aren't eligible, so change it to a text field
  3. The field can be made required in its definition, which enforces a value when saving in the UI but not when saving through the API
  4. A User field can't be made required in its definition, so make it required on the page layout instead
Show the answer and explanation

Answer: A

Why this is correct
"Require Field Input to Ensure Data Quality" says a field made required in its definition (a universally required field) must be a custom field, and requires a value wherever the record is saved: in the Salesforce UI, through the Lightning Platform API, or in automated processes such as Web-to-Lead. A note adds that when you make a User field universally required, you must specify a default value for it. Picklist is one of the field types that can be universally required.

Why the other options are wrong
"A User field can't be made required in its definition, so make it required on the page layout instead" … Help gives a condition for making a User field universally required (a default value) rather than saying it can't be done. A page layout requirement works only at the UI level and does not apply to the API or automated processes.
"The field can be made required in its definition, which enforces a value when saving in the UI but not when saving through the API" … That is closer to how a page layout or field-level security requirement behaves. A universally required field requires a value on API saves and automated saves too.
"The field can be made required in its definition, but picklist fields aren't eligible, so change it to a text field" … Help's list of types that can be universally required includes picklist. You don't need to change the type.

Key point
The types that can be universally required are currency, date, date/time, email, master-detail (always required), number, percent, phone, picklist, text, text area, and URL. A custom field on campaign members also needs a default value when made universally required, and members of relationship groups do not support universally required fields.

Go to the Salesforce Certified Platform Administrator II practice app (10 free questions; purchase unlocks all questions)

See the full practice set