GOOGLE-WORKSPACE-ADMINISTRATOR practice question 10 of 25
Your company is deploying Chrome devices. You want to make sure the machine assigned to the employee can only be signed in to by that employee and no one else. What two things should you do? (Choose two.)
Full set: 199 questionsDomain Business initiatives
To restrict a ChromeOS device to a single, specific employee, a multi-layered approach is required. First, all non-specific access methods must be disabled; this includes Guest Mode and Public Sessions, which allow users to access the device without a managed account. Second, a device-level policy must be configured to explicitly whitelist only the intended employee's user account. The "Restrict sign-in to a list of users" policy is designed for this purpose. By adding only the assigned employee's email address to this list, all other managed users are prevented from signing in.
B. The "Sign In Screen" policy controls the appearance of the login screen (e.g., showing user photos) but does not restrict who can sign in.
C. A 2-Factor hardware key enhances security for the employee's account but does not prevent other authorized users from signing in to the device with their own credentials.
D. "Multiple Sign In Access" is a user-level policy that controls a user's ability to be signed into multiple Google accounts within their browser session, not device access.
1. Google Workspace Admin Help, Set ChromeOS device policies, Sign-in restriction: This policy is detailed under the "Sign-in settings" section. The documentation states, "Specify which users can sign in to ChromeOS devices... To allow only specific users to sign in, select Restrict sign-in to the list of users below and enter the user names." This directly supports option E.
2. Google Workspace Admin Help, Set ChromeOS device policies, Guest mode: Under "Sign-in settings," the documentation for this policy states, "Specify if users can sign in using Guest mode on ChromeOS devices." To restrict access, an administrator must select Do not allow guest mode. This supports option A.
3. Google Workspace Admin Help, Set ChromeOS device policies, Public Session: The documentation for Public Sessions explains that this feature allows multiple users to share a device without signing in. Disabling this is crucial for restricting the device to a single named user, further supporting option A.
4. Google Workspace Admin Help, Set ChromeOS device policies, Sign-in screen: This policy's description confirms it manages settings like "Show user names and photos on the sign-in screen," which is cosmetic and does not enforce access restrictions, proving option B is incorrect.
Keep practicing
Take the free GOOGLE-WORKSPACE-ADMINISTRATOR practice test
Ten exam-style questions with answers and explanations, plus the exam facts and study guides.
More questions
Other GOOGLE-WORKSPACE-ADMINISTRATOR practice questions
- Question 1You work for an international organization and your CEO frequently travels to other count…
- Question 2In your organization, users have been provisioned with either Google Workspace Enterprise…
- Question 3Your organization has just appointed a new CISO. They have signed up to receive admin ale…
- Question 4In the years prior to your organization moving to Google Workspace, it was relatively com…
- Question 5All Human Resources employees at your company are members of the “HR Department” Team Dri…
- Question 6Your Accounts Payable department is auditing software license contracts companywide and h…
