ADM-201 - Configuration and Setup (15% of the exam) - Section 1.2

Manage users, including creating and deactivating users, resetting passwords, assigning roles and profiles, and using login history to troubleshoot access.

Create, edit, freeze, and deactivate users, recognising that users are never deleted because they own records, and assign the correct user license, role, and profile at creation. Use login history, login hours, and login IP ranges to troubleshoot access issues and enforce when and where a user can sign in.

User managementUser licenseLogin historyFreeze vs deactivate

Practice question for this objective

Free sampleConfiguration and Setupmedium

At Yallingup Media, the administrator has built a new profile intended for a group of operations staff, but when editing one of those users the new profile does not appear in the Profile picklist. The user currently holds a Salesforce Platform user licence. What most likely explains why the profile cannot be selected?

AThe new profile has no permission set linked to it, so it cannot be chosen until one is associated.
BThe new profile has been marked inactive and must be cloned to an active copy before assignment.
CThe administrator is missing the Manage Users permission required to view any custom profile.
DThe profile is tied to a user licence that differs from the Salesforce Platform licence assigned to the user. Correct

Each profile is bound to one user licence, so only profiles matching a user's licence appear when assigning that user's profile. A profile is created against a specific user licence and inherits the features and object access that licence permits; when editing a user, Salesforce filters the Profile picklist to profiles sharing that user's licence, so a profile built for a different licence is not offered.

Why A is wrong: This sounds plausible because permission sets extend profiles, but a profile is fully assignable on its own and never depends on a linked permission set to appear in the picklist.

Why B is wrong: It is tempting to treat profiles like records that can be deactivated, but profiles have no active or inactive state, so this is not why the profile is hidden.

Why C is wrong: This seems reasonable, yet the administrator was able to create the profile, which itself needs that permission, so a lack of it cannot be the cause here.

Why D is correct: Every profile is bound to exactly one user licence type, and the Profile picklist for a given user only shows profiles that match that user's licence, so a licence mismatch hides the profile.

See more ADM-201 practice questions, answers explained.

Exam traps in Configuration and Setup

Answers that look right on this material and are not. Each one is a distractor from a different question in the ADM-201 bank for this domain.

Edit each of the three profiles to add Read and Edit object access plus field-level Edit access, since profiles are where object and field permissions are defined.
Why it is wrong: Tempting because profiles genuinely control object and field access, but editing the profiles would grant the access to every user assigned to them, not just the eight team members, violating the no-side-effects requirement.
The email address entered is already used by another active user, which suppresses the profile list.
Why it is wrong: A duplicate email is a real problem, but it produces a validation error when saving rather than filtering which profiles appear in the picklist.
Delete the user record from Setup so that the assigned licence is released back to the available pool.
Why it is wrong: It is tempting because deleting a record usually frees whatever it consumed, but Salesforce does not allow user records to be deleted at all, so this action cannot be performed.

Examworthy is not affiliated with or endorsed by Salesforce. Original, blueprint-aligned practice material only.