nerdexam
CompTIA

CV0-002 · Question #264

Which of the following is the BEST way to ensure accounts in a cloud environment are disabled as soon as they no longer need to be active?

The correct answer is A. Have the user contact the cloud systems administrator to disable the account when it is no longer. The best way to ensure accounts are disabled immediately when no longer needed is for the user to proactively notify the cloud systems administrator.

Security

Question

Which of the following is the BEST way to ensure accounts in a cloud environment are disabled as soon as they no longer need to be active?

Options

  • AHave the user contact the cloud systems administrator to disable the account when it is no longer
  • BWhen users leave the company, ensure an account disablement request is initiated and will be
  • CHave accounts checked by the cloud systems administrator once per day to ensure active
  • DReboot directory services servers once a day to ensure all account disablement requests are

How the community answered

(50 responses)
  • A
    82% (41)
  • B
    12% (6)
  • C
    4% (2)
  • D
    2% (1)

Why each option

The best way to ensure accounts are disabled immediately when no longer needed is for the user to proactively notify the cloud systems administrator.

AHave the user contact the cloud systems administrator to disable the account when it is no longerCorrect

Having the user, who is often the first to know when their access or an account is no longer needed, directly contact the cloud systems administrator enables immediate disablement. This method ensures that the deactivation request originates at the earliest possible moment, aligning with the goal of disabling accounts 'as soon as they no longer need to be active,' without waiting for an HR event or a scheduled review.

BWhen users leave the company, ensure an account disablement request is initiated and will be

While crucial for employee departures, this option does not cover scenarios where an account is no longer needed for a specific task or project while the user is still employed, thus not capturing all 'no longer active' situations.

CHave accounts checked by the cloud systems administrator once per day to ensure active

Daily manual checks are reactive and introduce a delay of up to 24 hours between an account becoming inactive and its potential disablement, failing to meet the 'as soon as' requirement.

DReboot directory services servers once a day to ensure all account disablement requests are

Rebooting directory services servers daily is an extremely disruptive and inappropriate action for managing account disablement requests; these systems process changes continuously.

Concept tested: Identity and Access Management (IAM) lifecycle - de-provisioning

Topics

#account lifecycle management#IAM#user offboarding#cloud security

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full CV0-002 Practice