A Workspace ONE UEM administrator is working on a special project where they have to grant access to their environment for a limited time. What is the best method for achieving this goal?

Question

Options

• ACreate an Admin Group with custom group assignments.
• BCreate an Admin Account and remove permissions.
• CCreate a limited Admin Account.
• DCreate a Temporary Admin Account.

• A
  3% (1)
• B
  8% (3)
• C
  3% (1)
• D
  87% (33)

Explanation

Temporary Admin Accounts (D) are purpose-built for time-limited access scenarios - they can be configured with an expiration date/time, automatically revoking access when the project ends without any manual follow-up required. This is the cleanest, most secure solution for the described use case.

Why the distractors fail:

• A (Admin Group with custom assignments) - Groups manage role scope, not access duration; there's no built-in expiration mechanism.
• B (Create an account then remove permissions) - This relies on a manual removal step that can be forgotten, creating a security gap; it's operationally risky.
• C (Limited Admin Account) - "Limited" refers to role/permission scope, not time. The account persists indefinitely unless manually deleted.

Memory tip: Think "temp job = temp badge." Just as a contractor gets a badge that expires on their last day, a Temporary Admin Account has a built-in end date - no one has to remember to take it away.

No community discussion yet for this question.