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

Google PROFESSIONAL-CHROMEOS-ADMINISTRATOR Online Questions & Answers

• Question 1:

  Which management policy is missing within ChromeOS Flex vs ChromeOS?

  A. Do Not Allow Powerwash
  B. SCEP
  C. Remote Desktop
  D. Forced Re-enrollment
  A. Do Not Allow Powerwash

  ---

  explanation:

  Explanation

  ChromeOS Flex does not support the"Do Not Allow Powerwash"policy, which is available in standard ChromeOS. This limitation means that users can perform a factory reset, potentially losing management and security settings.

  Verified Answer from Official Source:

  The correct answer is verified from theChromeOS Flex Management Guide, which explicitly mentions the lack of this policy feature.

  "ChromeOS Flex does not support certain management features like disabling Powerwash, which can impact security settings."

  Without the ability to block Powerwash, devices may be reset, resulting in the loss of enterprise settings and requiring re-enrollment.

  Objectives:

  Understand the limitations of ChromeOS Flex.

  Maintain device security through management policies.

  References:

  ChromeOS Flex Management Guide

• Question 2:

  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:

  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 3:

  In line with Google's best practice recommendations, you need to configure an OU of devices to run on an early release of ChromeOS so that users can test new features and verify functionality. Which policy option should you choose?

  A. LTS
  B. Canary
  C. Beta
  D. Stable
  C. Beta

  ---

  explanation:

  Explanation

  ChromeOS offers different release channels with varying levels of stability and feature availability: Stable:The most stable and widely used channel, suitable for general deployment. Beta:Contains newer features and improvements, but with some potential for instability. Ideal for testing in a controlled environment. Dev:More frequent updates with experimental features, less stable than Beta. Canary:The least stable channel, updated daily with bleeding-edge features. To test new features while maintaining reasonable stability, the Beta channel is the recommended choice.

• Question 4:

  To allow remote users to securely connect to an internal network, the organization you're supporting is using a VPN. The organization would like you to configure the ChromeOS devices so that the Android VPN clients deployed are automatically configured with the correct hostname. How should you configure this in the Admin Console according to Google best practice?

  A. Download the Android app on a ChromeOS device, add the hostname manually then re- upload the app in the organization's private Google Play Store and deploy it lo all ChromeOS devices
  B. Contact the VPN provider and ask them to provide you with a custom installable client with the correct configuration pre-configured Then deploy that installable
  C. Add a managed configuration using JSON to the Android app
  D. Upload a JSON file with the configuration into the Google Play Store
  C. Add a managed configuration using JSON to the Android app

  ---

  explanation:

  Explanation

  This is the most efficient and scalable way to automatically configure Android VPN clients on ChromeOS devices with the correct hostname: Obtain Configuration: Get the required VPN configuration details (hostname, authentication methods, etc.) from the VPN provider or your organization's network administrator. This configuration is typically in JSON format. Create Managed Configuration: In the Google Admin console, navigate to Devices > Chrome > Settings > Android Apps > Managed Configurations. Select the VPN App: Choose the specific Android VPN app you want to configure. Add JSON Configuration: Paste the JSON configuration into the provided field. Ensure the configuration is valid and accurate. Save and Deploy: Save the managed configuration and apply it to the desired organizational units (OUs) containing the ChromeOS devices. This method allows you to centrally manage VPN configurations for Android apps on ChromeOS devices, ensuring consistency and reducing the manual effort required from users.

• Question 5:

  Your organization's security protocols require you to ensure that any unattended devices log the user out after 24 hours. You have 1000 ChromeOS devices to manage. How would you Implement this with the least amount of admin effort?

  A. Enable the 'User and Browser Settings" and update 'Maximum user session length* to any time up to 24 hours
  B. Create a corporate policy stating (he users are to manually sign out after the end of every shift
  C. You can remotely access each device and sign out of the user account using Chrome Remote Desktop
  D. Force-install a custom app to each device in question that notifies the user that they need to sign out of their device after 24 hours
  A. Enable the 'User and Browser Settings" and update 'Maximum user session length* to any time up to 24 hours

  ---

  explanation:

  Explanation

  This is the most efficient method as it applies the setting to all devices within the organizational unit (OU) through a single policy change in the Admin console. The other options are less efficient: Corporate policy:Relies on user compliance

  and is difficult to enforce. Chrome Remote Desktop:Requires manual intervention for each device. Custom app:Adds complexity and potential security risks.

  References:

  Set up Chrome browser on managed devices: https://support.google.com/chrome/a/answer/3523633?hl=en

• Question 6:

  How would you deploy a Progressive Web Application to all managed user accounts?

  A. Force-install the Progressive Web Application URL in the "Chrome Apps and extensions" page
  B. Set up Chrome Imprivata shared apps and extensions to force-install the Progressive Web Application URL
  C. Go to "User and Browser Settings" and add the Progressive Web Application URL in the "Legacy Browser Support" site list
  D. Open "Additional Google services" to force-install the Progressive Web Application URL
  A. Force-install the Progressive Web Application URL in the "Chrome Apps and extensions" page

  ---

  explanation:

  Explanation

  To deploy a Progressive Web Application (PWA) to all managed user accounts, follow these steps in the Google Admin console: Sign in to Google Admin console: Use your administrator credentials to access the console. Navigate to Device Management: Go to Devices > Chrome > Settings > Apps and extensions. Select User or Group: Choose the top-level organizational unit or a specific group to apply the PWA deployment. Add by URL: Click on the yellow "+" icon and select "Add by URL." Enter PWA URL: Paste the URL of the PWA you want to deploy. Configure Installation Policy: Select "Force install" to ensure the PWA is automatically installed for all users within the selected scope. This method allows you to centrally manage and deploy PWAs across your organization, making them easily accessible to users on their ChromeOS devices.

• Question 7:

  Your customer is deploying ChromeOS devices in their environment and requires those ChromeOS devices to adhere to web filtering via TLS (or SSL) Inspection. What recommendations should you make to your customer in setting up the requirements for ChromeOS devices?

  A. Configure a hostname allowlist, set up a TLS (or SSL) certificate, then verify TLS (or SSL) inspection is working
  B. Reach out lo Google Workspace Security and Compliance for tailored configurations for your customer
  C. Configure a transparent proxy, set up your allowlist to use * google com. then verify TLS (or SSL) inspection is working
  D. ChromeOS devices are preconfigured to adhere to company TLS (or SSL) inspection by default and can therefore be deployed with no additional configuration
  A. Configure a hostname allowlist, set up a TLS (or SSL) certificate, then verify TLS (or SSL) inspection is working

  ---

  explanation:

  Explanation

  To set up TLS (or SSL) inspection for web filtering on ChromeOS devices, you need to follow these steps: Configure Hostname Allowlist: Create an allowlist of hostnames (e.g., *.google.com, *[invalid URL removed]) that should bypass TLS inspection. This ensures that essential services like Google services and your own domain can function properly. Set up TLS Certificate: Obtain the required TLS/SSL certificate from your web filter provider and install it on your web filter. ChromeOS devices need this certificate to establish a secure connection with the web filter for TLS inspection. Verify TLS Inspection: Once the configuration is in place, test and verify that TLS inspection is working as expected. This involves checking if the web filter can correctly intercept and decrypt HTTPS traffic for websites not on the allowlist. Why other options are not correct: Option B: While reaching out to Google Workspace Security and Compliance can be helpful, it's not the primary step in setting up TLS inspection. The configuration needs to be done on the web filter and ChromeOS devices. Option C: Transparent proxies are generally not recommended for ChromeOS devices as they can interfere with certain functionalities. While it might work with an allowlist for Google domains, it's not the best practice. Option D: ChromeOS devices do not come preconfigured to adhere to company TLS inspection. This configuration needs to be set up explicitly by the administrator.

  References: About TLS (or SSL) inspection on ChromeOS devices: https://support.google.com/chrome/a/answer/3504942 Verify TLS (or SSL) inspection works: https://support.google.com/chrome/a/answer/3504943

• Question 8:

  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:

  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 9:

  You need to create a recovery image on a USB stick. Which two steps should you take? Choose 2 answers

  A. Go to Device Settings
  B. Go lo google com/chromebooks
  C. Go to Google Play store
  D. Go to Chrome Web Store on a Chrome device
  E. Install Chrome Recovery Utility and download the image for the coned device model to a USB stick
  D. Go to Chrome Web Store on a Chrome device
  E. Install Chrome Recovery Utility and download the image for the coned device model to a USB stick

  ---

  explanation:

  Explanation

  To create a recovery image on a USB stick, you need to: Access Chrome Web Store: Open the Chrome Web Store on a Chrome device (either a Chromebook or a computer with the Chrome browser installed). Install Chromebook Recovery Utility: Search for and install the "Chromebook Recovery Utility" extension. Launch the Utility: Open the installed extension. Identify Device: Enter the model number of the ChromeOS device for which you want to create the recovery image. Insert USB Stick: Insert a USB stick with sufficient storage capacity (at least 4GB). Download and Create: Follow the on-screen instructions in the utility to download the correct recovery image and create the bootable USB stick. This process will prepare a USB stick that can be used to recover or reinstall ChromeOS on a device that is not functioning properly.

  References: Recover your Chromebook: https://support.google.com/chromebook/answer/1080595?hl=en

• Question 10:

  Which feature of the Google Admin console allows you to restrict devices from remembering user passwords?

  A. Password Manager
  B. Security Token Removal
  C. Enrollment Permissions
  D. WebAuthn
  A. Password Manager

  ---

  explanation:

  Explanation

  ThePassword Managerfeature in the Google Admin console allows administrators to manage whether users can save and auto-fill passwords on ChromeOS devices. Disabling Password Manager prevents Chrome from remembering

  passwords, thus enhancing security by requiring users to enter credentials manually.

  Verified Answer from Official Source:

  The correct answer is verified from theGoogle Admin Console Password Policy Guide, which outlines how to manage password saving and auto-fill settings.

  "Admins can disable the Chrome Password Manager through the Admin console to ensure that user passwords are not saved locally on the device."

  This setting is crucial in high-security environments where saving passwords locally might pose a risk. Disabling Password Manager helps maintain stricter security protocols.

  Objectives:

  Enforce secure password management on ChromeOS devices.

  Disable auto-fill and password saving.

  References:

  Google Admin Console Password Policy Guide