Google PROFESSIONAL-CHROMEOS-ADMINISTRATOR Online Practice Questions and Exam Preparation

Google PROFESSIONAL-CHROMEOS-ADMINISTRATOR Online Questions & Answers

• Question 1:

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

  A. Navigate to "Chrome Verified Access" and enable the policy for content protection
  B. Go to "User and Browser and "Managed Guest Session' settings to upload your terms of service
  C. ln "User and Browser Settings" upload the "Terms of Service" as a wallpaper
  D. Navigate to "User and Browser" and "Managed Guest Session" settings to upload your custom avatar
  B. Go to "User and Browser and "Managed Guest Session' settings to upload your terms of service

  ---

  Explanation

  Go to the Google Admin console.

  Navigate to "Device Management" > "Chrome Management" > "User and 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 2:

  You want to enterprise enroll a device that has existing consumer accounts. What should you do first?

  A. Contact Google support to convert the device into an enterprise device
  B. Delete all consumer accounts, and then follow the same steps for enrolling a brand new device
  C. follow the same steps for enrolling a brand new device
  D. Wipe the device
  B. Delete all consumer accounts, and then follow the same steps for enrolling a brand new device

  ---

  Explanation

  Device State: Before you can enroll a ChromeOS device into an enterprise environment, it's crucial that it's not associated with any personal Google accounts. Existing consumer accounts can interfere with the enrollment process and the

  application of enterprise policies.

  Data Backup (Optional): If the existing consumer accounts on the device contain important data, advise the users to back up their information before proceeding. Account Removal: Sign in to the device with each consumer account and

  remove the account from the device. This ensures a clean slate for the enterprise enrollment process.

  Powerwash (Optional): While not strictly necessary after removing accounts, performing a powerwash (factory reset) is a recommended step. It further erases any remaining data or configurations linked to the consumer accounts, ensuring a

  completely fresh start for the device. Enrollment: Once the consumer accounts are removed (and optionally, after powerwashing), follow the standard enterprise enrollment steps for your organization. This typically involves entering enterprise

  credentials at the login screen, or using a unique enrollment token, depending on your company's setup.

  References:

  Enroll ChromeOS devices: https://support.google.com/chrome/a/answer/1360534?hl=en

  This guide provides step-by-step instructions on enrolling ChromeOS devices into an enterprise environment, including details on prerequisites and different enrollment methods.

• Question 3:

  A school wants all new Chromebooks to be enrolled through zero-touch enrollment (ZTE) in their parent organization unit. An admin needs to create tokens. Where will the admin go to generate the enrollment tokens for Chromebooks?

  A. Devices > Chrome > Enroll
  B. Devices > Chrome > Connectors
  C. Devices > Chrome > Settings
  D. Devices > Chrome > Devices > Enroll
  A. Devices > Chrome > Enroll

  ---

  Explanation

  To set upZero-Touch Enrollment (ZTE), an administrator must go toDevices > Chrome > Enrollwithin the Admin console. This is where they can generate the necessary enrollment tokens for automatic enrollment of devices when they first

  connect to the Internet.

  Verified Answer from Official Source:

  The correct answer is verified from theGoogle ChromeOS Zero-Touch Enrollment Guide , which specifies the steps to generate enrollment tokens.

  "To create Zero-Touch Enrollment tokens, go to Devices > Chrome > Enroll in the Admin console."

  Zero-Touch Enrollment simplifies the setup process for educational institutions by automatically enrolling devices into management without manual intervention.

  Objectives:

  Automate device enrollment using Zero-Touch.

  Simplify ChromeOS deployment in educational environments.

  References:

  Google ChromeOS Zero-Touch Enrollment Guide

• Question 4:

  As a ChromeOS Administrator, you are tasked with blocking incognito mode in the ChromeOS Browser. How would you prevent users from using incognito mode?

  A. Navigate to "Users and Browser Security Settings' and set the "Disallow incognito mode" policy
  B. Go ,0 "User and Browser Settings' to restrict sign-in to pattern and "Disallow incognito mode "
  C. From "Device Settings' change Kiosk settings to "Disallow incognito mode "
  D. ln "Enrollment Settings" disable vended access and incognito mode (or content protection
  A. Navigate to "Users and Browser Security Settings' and set the "Disallow incognito mode" policy

  ---

  Explanation

  Access the Google Admin Console:Sign in to the Admin console using your ChromeOS administrator credentials.

  Locate User Settings:Navigate to "Device Management" > "Chrome Management" > "User and browser settings".

  Find Incognito Mode Policy:Within the settings, search for "Incognito mode". Disable Incognito Mode:Select the option to "Disallow incognito mode". Save Changes:Click "Save" to apply the policy to the designated users or organizational

  units.

  References:

  Set up Chrome browser on managed devices:

  https://support.google.com/chrome/a/answer/3523633?hl=en

• Question 5:

  As a ChromeOS Administrator, you have been asked to enroll all of your devices into a specific device OU using Zero-Touch Enrollment (ZTE). What are the next steps?

  A. Generate a ZTE pre-provision enrollment token for your specified device OU
  B. Give the company domain name to your Chrome Partner to enable ZTF
  C. Generate a ZTE pre-provision enrollment token directly for your domain root OU
  D. Generate a ZTE pre-provision enrollment token for your specified user OU
  E. Use a dedicated ZTE Admin account for device enrollment
  A. Generate a ZTE pre-provision enrollment token for your specified device OU
  B. Give the company domain name to your Chrome Partner to enable ZTF

  ---

  Explanation

  Generate a ZTE pre-provision enrollment token for your specified device OU:This token associates devices with the specific organizational unit (OU) during enrollment, allowing for easier management and policy application. Give the company

  domain name to your Chrome Partner to enable ZTF:This enables the Zero-Touch Framework, allowing devices to be automatically enrolled as soon as they connect to the internet.

  Why other options are incorrect:

  C (Generate token for root OU):While possible, it's not ideal as it doesn't allow for granular control over different device groups.

  D (Generate token for user OU):Zero-Touch Enrollment is specifically for devices, not users.

  E (Use dedicated admin account):While recommended for security, it's not a mandatory step for ZTE.

• Question 6:

  The security department has been informed that a ChromeOS device was stolen out of an employee's car. What should you do in the Admin console to ensure the device Is rendered Inoperable while still maintaining management of the device?

  A. Tag the ChromeOS device as stolen
  B. Disable the ChromeOS device
  C. Powerwash the ChromeOS device
  D. Deprovision the ChromeOS device
  B. Disable the ChromeOS device

  ---

  Explanation

  Disabling a ChromeOS device in the Admin console prevents it from booting up or being used, effectively rendering it inoperable. However, it retains the device's association with the organization, allowing administrators to track its location and manage it remotely if recovered. The other options are not as suitable: Tagging as stolen:Doesn't prevent device usage. Powerwash:Removes all data and enrollment, making management impossible. Deprovision:Removes device association, making management impossible.

• Question 7:

  You are enrolling several devices to send to a remote location. How can you ensure that these devices will automatically connect to the wireless network at the remote location when powered on for the first time?

  A. Add the wireless network credentials to the "Networks" section in the Admin console ensuring that they are applied to the ChromeOS devices By Device
  B. Use the Google Zero-Touch Enrollment (ZTE) process and generate the provisioning token by clicking on the 'Enroll device' button in the Admin console `'Devices'' page
  C. During the enrollment process add the wireless credentials manually to each device in the Admin console ensuring that they are applied to ChromeOS devices By User
  D. Add the wireless network credentials to the 'Networks" section in the Admin console ensuring that they are applied to the ChromeOS devices By User
  A. Add the wireless network credentials to the "Networks" section in the Admin console ensuring that they are applied to the ChromeOS devices By Device

  ---

  Explanation

  To ensure ChromeOS devices automatically connect to a specific wireless network upon initial power-on at a remote location, follow these steps in the Google Admin console: Navigate toDevice Management>Chrome Management>Networks. Add the Wi-Fi network credentials (SSID and password) to the list of networks. Set the network configuration to applyBy Device. This ensures that the credentials are pushed to the device itself, not tied to a specific user. When the devices are powered on at the remote location, they will automatically detect and connect to the configured Wi-Fi network without requiring any manual intervention from the user. Option B (Zero-Touch Enrollment) simplifies the initial setup process but doesn't automatically configure Wi-Fi. Options C and D are incorrect because applying network settings by user won't ensure automatic connection on first boot before any user logs in.

• Question 8:

  You're in charge of deploying video conferencing equipment and it has been decided that you will leverage ChromeOS devices. What initial considerations should you make when deciding on devices?

  A. Deploying instructional guides to all users on setup configuration, and use of new equipment
  B. A form factor compatible for both remote and site workers is required
  C. A precise time window on how to apply security patches and updates to all devices
  D. Devices must have 8GB of RAM and obey supported processor models
  B. A form factor compatible for both remote and site workers is required

  ---

  Explanation

  When deploying video conferencing equipment using ChromeOS devices, the primary consideration is choosing a form factor (device type) that caters to both remote and on-site workers. This ensures flexibility and consistent user experience regardless of location. Option A is incorrectbecause while instructional guides are helpful, they are a secondary concern to device suitability. Option C is incorrectbecause security patch timing is important but not the initial consideration when choosing devices. Option D is incorrectbecause while specifications matter, they should align with the chosen form factor and user needs.

• Question 9:

  A user who is having trouble seeing the cursor on their screen due to a visual impairment contacts a help desk. What is the best option an admin can use to explore this issue?

  A. Update User personalization
  B. Review using remote desktop
  C. Change the device resolution
  D. Change the device policy
  B. Review using remote desktop

  ---

  Explanation

  The most effective way to assist a user who has difficulty seeing the cursor is to remotely access their device and examine the issue firsthand. ChromeOS allows administrators to remotely access managed devices using tools such as

  Chrome Remote Desktop. This way, the admin can see exactly what the user sees and directly troubleshoot or make necessary adjustments.

  Verified Answer from Official Source:

  The correct answer has been verified based on theGoogle ChromeOS Administrator Guide, which highlights that remote desktop access is the most effective way to understand and troubleshoot user-specific display and cursor issues.

  "To help users who encounter visual or interface issues, admins can utilize Chrome Remote Desktop to gain direct access to the device and make necessary adjustments remotely."

  Reviewing using remote desktop allows the admin to see the problem in real time and assess whether it is a settings issue or requires further technical adjustments. This approach is more efficient than guessing or changing policies without

  direct insight.

  Objectives:

  Troubleshoot device accessibility issues.

  Use Chrome Remote Desktop for device management.

  References:

  Google ChromeOS Administrator Guide - Troubleshooting Accessibility

• Question 10:

  A customer deploys a large number of ChromeOS devices and would like to start the process of turning on Zero-Touch Enrollment (ZTE) to streamline their deployment process. As an administrator, what would be required to enable ZTE?

  A. Identify OU to place devices during enrollment
  B. Grant partner admin access
  C. Create a pre-provisioning token
  D. Create a zero-touch token
  C. Create a pre-provisioning token

  ---

  Explanation

  To enableZero-Touch Enrollment (ZTE)for ChromeOS devices, an administrator must firstcreate a pre-provisioning token. This token allows devices to automatically enroll when they are first powered on and connected to the internet. The

  pre-provisioning token links the device to the correct organization and management policies.

  Verified Answer from Official Source:

  The correct answer is verified from theGoogle Zero-Touch Enrollment Guide, which outlines the process of setting up pre-provisioning tokens for automated enrollment. "To set up Zero-Touch Enrollment, generate a pre-provisioning token in

  the Admin console and configure it with the device provider."

  Creating the token ensures that new devices are automatically configured and enrolled without manual intervention, saving time during mass deployments.

  Objectives:

  Automate ChromeOS device enrollment.

  Simplify large-scale deployments.

  References:

  Google Zero-Touch Enrollment Guide