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

Google PROFESSIONAL-CHROMEOS-ADMINISTRATOR Online Questions & Answers

• Question 61:

  What is a feature of Verified Boot?

  A. Eliminates the need for strict policy controls
  B. Protects anonymous guests from using the device
  C. Prevents the user from accessing unauthorized websites
  D. Makes sure that the firmware and OS have not been tampered with
  D. Makes sure that the firmware and OS have not been tampered with

  ---

  Explanation

  Verified Boot is a security feature in ChromeOS that ensures the integrity of the operating system every time the device starts. It checks the OS for modifications or corruptions, preventing tampered systems from booting and automatically

  repairing them if necessary.

  Verified Answer from Official Source:

  The correct answer is verified from theChromeOS Security Guide, which highlights Verified Boot as a core feature for maintaining the OS's integrity.

  "Verified Boot ensures that the firmware and OS on ChromeOS devices have not been tampered with. If an anomaly is detected, the system reverts to a known good state."

  This feature is crucial for protecting the system from malicious software or unauthorized changes, maintaining the device's security posture.

  Objectives:

  Enhance device security through integrity checks.

  Understand ChromeOS boot protection mechanisms.

  References:

  ChromeOS Security Guide

• Question 62:

  Your administration team is about to deploy a fleet of ChromeOS devices. Your users have their own peripherals, and you would like them to use what they have if possible. You also would like to let your users know what peripherals work and what peripherals do not. What should you do for your users?

  A. Send them all new peripherals and have your users send in their old equipment even if the old equipment works
  B. Tell your users that every peripheral works with ChromeOS
  C. Create Change Management documentation that provides them with information on how to check their current peripherals and instructions on how to get new equipment
  D. Tell your users to try what they have and to start an IT support ticket if something isn't working right
  C. Create Change Management documentation that provides them with information on how to check their current peripherals and instructions on how to get new equipment

  ---

  Explanation

  The best way to handle this situation is to createChange Management documentation that clearly outlines how users can check the compatibility of their peripherals with ChromeOS. This documentation should also include instructions on how

  to obtain new peripherals if needed. This proactive approach reduces confusion and ensures that users know how to verify their existing equipment.

  Verified Answer from Official Source:

  The correct answer is verified from theGoogle Workspace Deployment Guide, which emphasizes proactive user communication through change management documentation during device rollouts.

  "To ensure smooth transitions, provide users with detailed change management documentation, including steps to verify peripheral compatibility and obtain replacements if necessary."

  Creating clear documentation helps reduce support requests and empowers users to verify their own equipment, streamlining the deployment process.

  Objectives:

  Facilitate smooth ChromeOS device rollout.

  Enhance user self-service with comprehensive guidance.

  References:

  Google Workspace Deployment Guide

• Question 63:

  A customer is setting up a new Google tenant. You have been tasked with creating the organization unit structure for the Google Admin console. Following Google best practices, how should you set up the new organization units?

  A. Recreate the same OU structure as the current LDAP implementation
  B. Combine Devices and Users into single OUs to avoid operational overhead
  C. Follow a hierarchical OU structure
  D. Use shortest possible names for OUs to avoid confusion
  C. Follow a hierarchical OU structure

  ---

  Explanation

  Followinga hierarchical OU structureallows for clear and organized management of devices and users. This structure mirrors real-world organizational layouts (such as departments or geographical locations), which makes applying policies

  and managing devices more straightforward.

  Verified Answer from Official Source:

  The correct answer is verified from theGoogle Admin Console Best Practices Guide, which recommends using hierarchical OUs for clarity and ease of management.

  "Using a hierarchical OU structure makes it easier to manage devices and users separately, especially when applying specific policies."

  A well-organized OU structure improves scalability and simplifies policy management, reducing administrative complexity.

  Objectives:

  Implement structured and manageable OU setups.

  Follow best practices for organizational hierarchy in Google Admin Console.

  References:

  Google Admin Console Best Practices Guide

• Question 64:

  Your company's network team reports Wi-Fi issues with certain ChromeOS devices. To troubleshoot, you will reproduce the problem but also need to collect network logs. How are you going to proceed?

  A. From the Chrome Browser, use the "chrome://system" page and check the "wifi_status_no_anonymize" attribute
  B. From chrome://network, use the "Network Logs" tab, select the "Wi-fi debug" mode, then export the "system_logs.txt" file and all log files collected by debugd
  C. From chrome://network, use the "Network Logs" tab, select the "Wi-Fi debug" mode, open a new tab and reproduce the issue. Once completed, go back to the original tab, then export the "system_logs.txt" file and all log files collected by debugd
  D. From chrome://network, use the "Network Logs" tab and select the policies.json, all logs files collected by debugd, and all Chrome log files
  C. From chrome://network, use the "Network Logs" tab, select the "Wi-Fi debug" mode, open a new tab and reproduce the issue. Once completed, go back to the original tab, then export the "system_logs.txt" file and all log files collected by debugd

  ---

  Explanation

  To accurately troubleshoot Wi-Fi issues, it is essential to enableWi-Fi debug mode, reproduce the problem, and then export the logs. This method ensures that the logs contain relevant data about the issue, as capturing logs before

  reproducing the issue might miss critical information.

  Verified Answer from Official Source:

  The correct answer is verified from theChromeOS Network Troubleshooting Guide, which advises collecting logs only after the issue has been replicated.

  "To troubleshoot network issues on ChromeOS, use chrome://network and enable Wi-Fi debug mode. Reproduce the problem before exporting the system_logs.txt file for accurate diagnosis."

  By reproducing the problem before collecting logs, you ensure that the captured data accurately reflects the issue, making it easier to identify root causes.

  Objectives:

  Troubleshoot network connectivity on ChromeOS.

  Collect accurate log data for analysis.

  References:

  ChromeOS Network Troubleshooting Guide

• Question 65:

  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

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

  Your network administrator wants to block Google services traffic. What is the result?

  A. Google Search will not work
  B. Chrome devices will crash
  C. Chrome devices will not be able to reach Google
  D. Nothing This isn't an issue
  A. Google Search will not work

  ---

  Explanation

  Blocking Google services traffic will prevent Chrome devices from accessing any Google- owned domains, includinggoogle.com. This will directly impact Google Search, as it relies on communication with Google servers to provide results. Other Google services like Gmail, YouTube, Google Drive, etc., will also be inaccessible. However, the Chrome device itself will not crash, as it can still function with other websites and applications.

• Question 67:

  You need to set a policy that prevents the device from shutting down while idling on the sign-in screen. Where should you navigate to?

  A. User Settings > Idle settings
  B. User Settings > User Experience
  C. Device Settings > Allow shutdown
  D. Device Settings > Power management
  D. Device Settings > Power management

  ---

  Explanation

  To prevent a ChromeOS device from shutting down while idling on the sign- in screen, you need to adjust the power management settings. This can be done through the following steps: Go to the Google Admin console. Navigate toDevice Management>Chrome Management>Device Settings. Find thePower managementsection and locate the setting that controls idle behavior on the sign-in screen. Adjust the setting to prevent shutdown during idle periods. Option A is incorrect because idle settings primarily control screen dimming and sleep behavior. Option B is incorrect because user experience settings generally focus on visual and interaction aspects, not power management. Option C is incorrect because there isn't a specific "Allow shutdown" setting in ChromeOS device settings.

• Question 68:

  Your organization is buying new ChromeOS devices to replace older devices. You are receiving these devices and need to dispose of them responsibly. What should you do to each of these devices before disposing of them?

  A. Deprovision the devices
  B. Factory reset the devices
  C. Suspend the devices
  D. Disable the devices
  A. Deprovision the devices

  ---

  Explanation

  Before disposing of ChromeOS devices, it is essential todeprovisionthem. Deprovisioning removes the device from the enterprise management console and ensures that it is no longer associated with the organization. This step protects

  organizational data and licenses.

  Verified Answer from Official Source:

  The correct answer is verified from theGoogle Admin Console Device Management Guide, which advises deprovisioning before device disposal.

  "Deprovisioning a device ensures it is no longer managed and releases any associated licenses. This is essential before disposing of the device." Deprovisioning is crucial for both security and compliance, as it guarantees that no residual

  management settings remain on the device.

  Objectives:

  Securely retire ChromeOS devices.

  Protect organizational data during device disposal.

  References:

  Google Admin Console Device Management Guide

• Question 69:

  What are two ways customers can open a support case for ChromeOS? Choose 2 answers

  A. Chat support via the Admin console
  B. Contact the device manufacturer
  C. File feedback on the device with Alt + Shift +1
  D. File case through Customer Care Portal
  E. Send an email to ChromeOS support
  B. Contact the device manufacturer
  D. File case through Customer Care Portal

  ---

  Explanation

  B. Contact the device manufacturer: ChromeOS devices are manufactured by various companies like Acer, HP, Lenovo, etc. Each manufacturer provides its own support channels, including phone, email, or chat support. Customers can

  contact the manufacturer for hardware-related issues or specific device configurations.

  D. File a case through the Customer Care Portal: Google provides a customer care portal where customers can submit support cases online. This portal

  allows users to describe their issues, attach relevant files, and track the progress of their case.

  Why other options are incorrect:

  A. Chat support via the Admin console: Chat support is usually available for enterprise customers with Chrome Enterprise Upgrade or Google Workspace, not individual ChromeOS users.

  C. File feedback on the device with Alt + Shift + 1: This keyboard shortcut is used to capture screenshots and send feedback to Google, but it doesn't directly open a support case.

  E. Send an email to ChromeOS support: While Google has support channels, sending a general email might not be the most efficient way to open a case and get a timely response.

  References:

  Get support - Chrome Enterprise and Education Help: https://support.google.com/chrome/a/answer/4594885?hl=en

• Question 70:

  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?

  A. In "Power management settings" apply 'Do not allow device to sleep/shut down when idle on the sign-in screen "
  B. In "User and Browser Settings" for Power and shutdown set the policy to "Do not allow wake locks "
  C. In "Power management settings" set the policy to "Only allow users to turn off the device using the physical power button "
  D. In "Managed Guest Session settings" set the maximum user session length to "unlimited "
  A. In "Power management settings" apply 'Do not allow device to sleep/shut down when idle on the sign-in screen "

  ---

  Explanation

  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.

  References:

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