An administrator at Cloud Kicks wants to deactivate a User who has left the company. What are two reasons that would prevent a user from being deactivated? Choose 2 answers

Question

Options

• AThe use is part of a territory hierarchy.
• BThe User is in a Custom hierarchy field.
• CThe User is assigned in workflow email alert.
• DThe User is the highest role in the role hierarchy

• A
  74% (35)
• B
  11% (5)
• D
  15% (7)

Explanation

Deactivating a user in Salesforce is blocked when the system has active dependencies that require a functioning user record. Territory hierarchy (A) prevents deactivation because Salesforce's Enterprise Territory Management requires users to be explicitly removed from territory assignments first - the territory model actively routes records through that user. Workflow email alerts (C) block deactivation because the alert has a hard reference to that user as a named recipient, and Salesforce won't allow the automation to be left pointing at an inactive user.

B is wrong because a Custom Hierarchy field is just a lookup-style field - it doesn't create a system-level dependency that blocks deactivation. D is wrong because role hierarchy position alone carries no deactivation restriction; Salesforce doesn't care if you're CEO of the role tree.

Memory tip: Think "active automation and active org structures block deactivation." Territories and workflow alerts are running processes that depend on the user - Salesforce protects them. Role hierarchy and custom fields are just data references that don't enforce blocking rules.

No community discussion yet for this question.