nerdexam
Salesforce

ADM-201 · Question #226

An administrator gets a rush request from Human Resources to remove a user's access to Saiesforce Immediately. The user is part of a hierarchy field called Direct Manager. What should the administrato

The correct answer is B. Freeze the user to prevent them from logging m while removing them from being referenced in. To immediately revoke a user's access while they are referenced in hierarchy fields, the administrator should first freeze the user's account and then address any necessary field cleanups.

Submitted by wei.xz· Apr 18, 2026Configuration and Setup

Question

An administrator gets a rush request from Human Resources to remove a user's access to Saiesforce Immediately. The user is part of a hierarchy field called Direct Manager. What should the administrator do to fulfill the request?

Options

  • AChange the user's profile to read-only while removing them from being referenced in the Direct
  • BFreeze the user to prevent them from logging m while removing them from being referenced in
  • CDelete the user and leave all records where they are referenced in the Direct Manager field
  • DDeactivate the user and delete any records where they are referenced in the Direct Manager field.

How the community answered

(47 responses)
  • A
    17% (8)
  • B
    70% (33)
  • C
    9% (4)
  • D
    4% (2)

Why each option

To immediately revoke a user's access while they are referenced in hierarchy fields, the administrator should first freeze the user's account and then address any necessary field cleanups.

AChange the user's profile to read-only while removing them from being referenced in the Direct

Changing a user's profile to read-only does not immediately prevent login and still allows the user to access data, failing to meet the 'immediately remove access' requirement.

BFreeze the user to prevent them from logging m while removing them from being referenced inCorrect

Freezing a user immediately prevents them from logging in without deactivating the user record, which is critical when a user is referenced in hierarchy fields like Direct Manager. This allows the administrator time to update fields safely before deactivation, preventing potential errors or issues with related records.

CDelete the user and leave all records where they are referenced in the Direct Manager field

Deleting a user is generally not possible in Salesforce if the user has associated records or is referenced in fields, making it an impractical solution.

DDeactivate the user and delete any records where they are referenced in the Direct Manager field.

Deactivating a user immediately revokes access but can prevent saving changes to records where the user is referenced in specific lookup or hierarchy fields, making freezing a better immediate first step for complex user dependencies.

Concept tested: User deactivation and freezing

Source: https://help.salesforce.com/s/articleView?id=sf.user_freeze.htm&type=5

Topics

#User Management#User Freeze#User Deactivation#Hierarchy Fields

Community Discussion

No community discussion yet for this question.

Full ADM-201 Practice