GOOGLE-WORKSPACE-ADMINISTRATOR practice question 12 of 25

Your organization has decided to enforce 2-Step Verification for a subset of users. Some of these users are now locked out of their accounts because they did not set up 2-Step Verification by the enforcement date. What corrective action should you take to allow the users to sign in again?

Full set: 199 questions

Domain Data access and security

Answer options
A: Disable 2-Step Verification per organizational unit so the affected users can sign in.
B: Move the affected users into the exception group temporarily so they can set up 2-Step Verification, and then remove them from the exception group after successful sign-in is confirmed. Correct answer
C: Disable 2-Step Verification organization-wide so all users can successfully sign in.
D: Move the affected users into the exception group permanently so they do not have to use 2-Step Verification going forward.
Correct Answer:
B. Move the affected users into the exception group temporarily so they can set up 2-Step Verification, and then remove them from the exception group after successful sign-in is confirmed.
Explanation

When 2-Step Verification (2SV) is enforced, users who have not enrolled by the specified date are locked out. The correct administrative procedure is to use an exception group. By temporarily moving the locked-out users into a designated group where 2SV enforcement is turned off, they can sign in with just their password. This allows them to complete the 2SV enrollment. Once enrollment is confirmed, the administrator must move them back to their original organizational unit (OU) or group where 2SV is enforced, thereby ensuring compliance with the security policy. This method is targeted, temporary, and maintains the integrity of the security policy.

Why Incorrect

A. Disabling 2SV for an entire organizational unit is an overly broad action that unnecessarily weakens security for all users within that unit.
C. Disabling 2SV organization-wide is a severe security risk that completely undermines the intended security posture for the entire domain.
D. Permanently moving users to an exception group circumvents the security policy, failing the primary objective of enforcing 2SV for those users. ---

References

1. Google Workspace Admin Help, "Deploy 2-Step Verification." In the section "Handle locked-out users," the official documentation states: "To give a locked-out user access to their account, you can temporarily move them to a group or organizational unit where 2-Step Verification isn't enforced. This allows the user to sign in and enroll in 2-Step Verification. After they enroll, you can move them back to their original group or organizational unit." This directly supports the procedure described in the correct answer.

2. Google Workspace Admin Help, "Protect your business with 2-Step Verification." Under the section "Set up 2-Step Verification enforcement," the documentation advises on using groups for deployment: "We recommend you turn on enforcement for a group of pilot users first. You can also create an exception group of users for whom you don't want to enforce 2-Step Verification." This establishes the concept of an "exception group" as a standard administrative tool for managing 2SV rollouts and handling edge cases like lockouts.

Scroll to Top