Google ChromeOS Administrator Exam Practice Test Instant Access

Question 1

To use Verified Access in your organization, you need to have a Chrome extension that calls Verified Access API on the client devices. Where can you go to get this extension?

AGoogle Play Store

BIndependent software vendor (ISV) or Google Verified Access API

CIndependent software vendor (ISV) repository

DSoftware API Key store

Answer : B

Verified Access requires a Chrome extension to communicate with the Verified Access API. While Google doesn't directly provide this extension, it offers detailed documentation and resources through the Verified Access API. Independent software vendors (ISVs) can use these resources to develop and provide compatible extensions.

Option A is incorrect because Google Play Store is for Android apps, not Chrome extensions.

Option C is incorrect because while ISVs might offer extensions, it's not the sole source. Google's documentation is essential.

Option D is incorrect because API keys are for authentication, not the extension itself.

Question 2

What should an administrator do to view the number and type of ChromeOS upgrades purchased and in use by their domain?

AVerify upgrades on devices page

BCheck subscriptions in billing

CContact partner to verify

DCheck reports page for upgrades

Answer : B

To view the number and type of ChromeOS upgrades purchased and in use, administrators should check the 'Subscriptions' section in the billing area of the Google Admin console. This section provides a clear overview of the organization's ChromeOS upgrade subscriptions and usage.

Other options are incorrect because they don't directly provide information about ChromeOS upgrade subscriptions:

Option A (Verify upgrades on devices page): Shows upgrades on individual devices, not the overall purchase and usage.

Option C (Contact partner to verify): Unnecessary if the information is readily available in the Admin console.

Option D (Check reports page for upgrades): Might provide some usage data, but not the purchase details.

Question 3

You are setting up ChromeOS devices in a public library and need to prevent your ChromeOS devices from sleeping when not in use. How would you set up your policy to achieve this?

AIn 'Power management settings' apply 'Do not allow device to sleep/shut down when idle on the sign-in screen '

BIn 'User & Browser Settings' for Power and shutdown set the policy to 'Do not allow wake locks '

CIn 'Power management settings' set the policy to 'Only allow users to turn off the device using the physical power button '

DIn 'Managed Guest Session settings' set the maximum user session length to 'unlimited '

Answer : A

This setting is specifically designed to prevent Chrome OS devices from sleeping or shutting down when they are not actively being used, but are on the sign-in screen. This is ideal for public environments like libraries where the devices are meant to be accessible at all times.

Other options are incorrect because:

B: This setting controls wake locks, which are used to keep a device awake under certain conditions. It doesn't directly control sleep behavior on the sign-in screen.

C: This setting controls how users can turn off the device, but doesn't prevent the device from sleeping on its own.

D: This setting controls the maximum length of a guest session, but doesn't affect the device's sleep behavior on the sign-in screen.

https://support.google.com/chrome/a/answer/3523633

Question 4

The security team is requiring Wi-Fi connectivity to be disabled on ChromeOS devices. Using the Google Admin console, how would you configure ChromeOS devices to block all WI-FI connectivity and hide the WI-FI Icon?

AConfigure 'Restricted Wi-Fi Networks '

BPrevent WiMax connectivity

CRemove Wi-Fi from 'Enabled network interfaces '

DRestrict 'Auto Connecting' to Wi-Fi

Answer : C

To completely disable Wi-Fi and hide the Wi-Fi icon on ChromeOS devices, you need to modify the 'Network' settings in the Google Admin console:

Go to 'Device Management' > 'Chrome Management' > 'Device Settings'.

Select the organizational unit (OU) containing the devices you want to manage.

Under 'Network', find 'Enabled network interfaces' and remove 'Wi-Fi' from the list.

Save the changes.

This will disable Wi-Fi adapters on the devices and hide the Wi-Fi icon, preventing users from connecting to Wi-Fi networks.

Why other options are incorrect:

A . Restricted Wi-Fi Networks: This setting only limits which networks users can connect to, not disable Wi-Fi entirely.

B . Prevent WiMax connectivity: WiMax is a different wireless technology and not relevant to Wi-Fi.

D . Restrict 'Auto Connecting' to Wi-Fi: This only prevents automatic connection to networks but doesn't disable Wi-Fi entirely.

Question 5

You are using a third-party service for SSO. Users are confused when signing onto a Chrome device because they are asked for Google account details before being redirected to the sign-In screen for your SSO provider Which setting must be changed so managed devices open the SSO provider login page by default?

ASAML single sign-on login frequency

BSAML single sign-on password synchronization flows

CSingle sign-on cookie behavior

DSingle sign-on IdP redirection

Answer : D

The Single sign-on IdP redirection setting controls whether managed devices directly open the login page of the third-party SSO provider (Identity Provider) or first prompt for Google account credentials. By enabling this setting, you streamline the login process for users and eliminate the confusion caused by the extra Google account prompt.

Option A is incorrect because it controls the frequency of re-authentication for SAML SSO, not the initial login page.

Option B is incorrect because it relates to password synchronization between Google and the IdP, not the login page redirection.

Option C is incorrect because it deals with how cookies are handled for SSO, not the login page redirection.

Question 6

How would you deploy your "Terms of Services" page to all managed ChromeOS devices?

ANavigate to 'Chrome Verified Access' and enable the policy for content protection

BGo to 'User & Browser and 'Managed Guest Session' settings to upload your terms of service

Cln 'User & Browser Settings' upload the 'Terms of Service' as a wallpaper

DNavigate to 'User & Browser' and 'Managed Guest Session' settings to upload your custom avatar

Answer : B

Go to the Google Admin console.

Navigate to 'Device Management' > 'Chrome Management' > 'User & browser settings'.

Find the section for 'Managed Guest Session'.

Locate the setting for 'Terms of Service'.

Upload your 'Terms of Service' document in plain text format.

This will present your Terms of Service to users when they log in as a guest on any managed ChromeOS device.

Why other options are incorrect:

A . Chrome Verified Access: This is for controlling access to corporate resources, not displaying terms of service.

C . Wallpaper: Using the wallpaper to display terms of service is not practical or user-friendly.

D . Custom avatar: The avatar is for user personalization and not related to terms of service.

Question 7

An admin is setting up third-party SSO for their organization as the super admin. When they test with their account, they do not see the SSO screen.

What is causing this behavior?

ASSO settings are misconfigured

BThe account is in the wrong OrgUnit

CThird-party SSO is not enabled

DSuper admin bypassed the thud-patty

Answer : D

Super administrators in Google Workspace have special privileges that allow them to bypass certain security features, including third-party SSO. This is to ensure that they can always access the Admin console for troubleshooting or critical changes, even if the SSO system is malfunctioning. Therefore, when a super admin tests third-party SSO, they won't be prompted with the SSO login screen, but will directly access the console using their Google credentials.

Google ChromeOS Administrator Professional ChromeOS Administrator Exam Practice Test