What is the best practice to ensure cloud accounts are disabled as soon as they are no longer needed?

What is the best practice to ensure cloud accounts are disabled as soon as they are no longer needed?

• A. Have the user contact the cloud systems administrator to disable the account when it is no longer needed.
• B. When users leave the company, ensure a disablement request is initiated and fulfilled within four hours.
• C. Have account checks performed by the cloud systems administrator once per day.
• D. Reboot directory services servers daily to commit all disablement requests.

Answer: (A)

Prompt deprovisioning hinges on a clear, immediate trigger to revoke access. When a user who actually no longer needs a cloud account requests its disablement, action can be taken right away, reducing the risk of lingering access and creating a clear, auditable record of the change. This direct user-to-admin signal minimizes delays and avoids relying on someone else to notice or act, which helps ensure the account is disabled as soon as it’s no longer needed. The other options either introduce potential delays or fail to actually disable the account (for example, simple daily checks don’t guarantee immediacy, and rebooting directory services doesn’t revoke access).

Prompt deprovisioning hinges on a clear, immediate trigger to revoke access. When a user who actually no longer needs a cloud account requests its disablement, action can be taken right away, reducing the risk of lingering access and creating a clear, auditable record of the change. This direct user-to-admin signal minimizes delays and avoids relying on someone else to notice or act, which helps ensure the account is disabled as soon as it’s no longer needed. The other options either introduce potential delays or fail to actually disable the account (for example, simple daily checks don’t guarantee immediacy, and rebooting directory services doesn’t revoke access).