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

Google PROFESSIONAL-CHROMEOS-ADMINISTRATOR Online Questions & Answers

• Question 91:

  Your team has members that work remotely. Your CTO would like to verify that your fleet of ChromeOS devices remains managed by corporate policy even after a device wipe. What would you configure to complete this objective?

  A. Set the setting "Powerwash" to "Do not allow powerwash to be triggered"
  B. Create strict password rules
  C. Edit the setting "Verified Access" to "Require verified mode for boot for verified access"
  D. Set up the Admin console to force the device to automatically re-enroll after wiping
  D. Set up the Admin console to force the device to automatically re-enroll after wiping

  ---

  Explanation

  To ensure that ChromeOS devices remain managed after a wipe, you need to enable forced re-enrollment. This setting automatically re-enrolls the device into the management domain after it has been wiped (Powerwashed). This feature is

  crucial for organizations that manage devices remotely, as it prevents unauthorized users from removing management settings.

  Verified Answer from Official Source:

  The correct answer is verified from theGoogle ChromeOS Device Management Best Practices Guide, which recommends enabling forced re-enrollment to maintain device management continuity.

  "To ensure devices remain managed after wiping, enable the 'Forced Re-enrollment' policy in the Admin console. This setting ensures automatic re-enrollment upon startup."

  Forced re-enrollment prevents the loss of device management, which is essential for maintaining security and policy compliance, especially in remote or dispersed environments.

  Objectives:

  Enforce device management after Powerwash.

  Maintain compliance in remote work environments.

  References:

  Google ChromeOS Device Management Best Practices Guide

• Question 92:

  Which remote command is required to remove a device from management policy updates?

  A. Deprovision
  B. Reset
  C. Disable
  D. Powerwash
  A. Deprovision

  ---

  Explanation

  The "Deprovision" command is specifically designed to remove a ChromeOS device from management policy updates. This means the device will no longer receive updates, configurations, or restrictions pushed from the Google Admin console. Here's what happens when you deprovision a device: Policy Removal: All enterprise policies and configurations are removed from the device. Management Removal: The device is disassociated from the Google Admin console and no longer considered managed. Data Wipe (Optional): You can choose to wipe the device's data during deprovisioning to ensure no company data remains. Other options like "Reset," "Disable," or "Powerwash" may have different effects: Reset: Resets the device to factory settings but might not remove management if not done through the Admin console. Disable: Prevents the user from signing in but doesn't remove policies or management. Powerwash: Factory resets the device, removing all user data and configurations, including management.

  References: Deprovision a device: https://support.google.com/chrome/a/answer/3523633

• Question 93:

  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?

  A. Google Play Store
  B. Independent software vendor (ISV) or Google Verified Access API
  C. Independent software vendor (ISV) repository
  D. Software API Key store
  B. Independent software vendor (ISV) or Google Verified Access API

  ---

  Explanation

  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 incorrectbecause Google Play Store is for Android apps, not Chrome extensions. Option C is incorrectbecause while ISVs might offer extensions, it's not the sole source. Google's documentation is essential. Option D is incorrectbecause API keys are for authentication, not the extension itself.

• Question 94:

  One of the employees of the organization you're managing is leaving, and you want to prepare the device they've been using for adoption by a new user. What is the recommended action you need to take through the Admin console to remove any previous user data from the machine?

  A. Deprovision the device, reset it, and then finally re-enroll it
  B. Enable forced-reenrollment on the device OU and then factory reset the device
  C. Delete the user from the Admin console and powerwash the machine
  D. Select "Reset" on the devices overview page, and then `Clear User Profiles."
  B. Enable forced-reenrollment on the device OU and then factory reset the device

  ---

  Explanation

  The best practice for preparing a ChromeOS device for a new user while keeping it managed is toenable forced-reenrollmentand thenfactory reset (Powerwash)the device. This ensures that any user-specific data is removed while the device

  remains enrolled and under enterprise control.

  Verified Answer from Official Source:

  The correct answer is verified from theChromeOS Device Reassignment Guide, which states that enabling forced-reenrollment ensures the device remains managed even after a factory reset.

  "To maintain management after a user leaves, enable forced-reenrollment on the OU and then perform a factory reset (Powerwash) on the device."

  This approach removes all user-specific data, including files and settings, while ensuring that the device automatically re-enrolls upon reboot, maintaining management and security.

  Objectives:

  Securely reassign ChromeOS devices.

  Maintain enterprise management and policies.

  References:

  ChromeOS Device Reassignment Guide

• Question 95:

  A large pharmaceutical company signs up for a Chrome trial and wants to order Chrome licenses. An admin needs to verify the domain. How can an admin verify the domain in the Admin console?

  A. Contact Google support and give them the MX record
  B. Call the DNS provider and give them an NS record
  C. Add the TXT record to the DNS setting at their domain registrar
  D. Ask the network administrator to approve the DNS record
  C. Add the TXT record to the DNS setting at their domain registrar

  ---

  Explanation

  To verify a domain in the Google Admin console, you mustadd a TXT recordto theDNS settingsat the domain registrar. This method confirms domain ownership by allowing Google to check for the specific TXT entry.

  Verified Answer from Official Source:

  The correct answer is verified from theGoogle Workspace Setup Guide, which outlines the domain verification process via DNS TXT records.

  "To verify your domain, sign in to your domain registrar and add a TXT record to the DNS settings. This confirms ownership for Google services."

  Adding a TXT record is the standard method for proving domain ownership, which is essential when setting up Google services for a new domain.

  Objectives:

  Verify domain ownership for Google services.

  Configure DNS settings appropriately.

  References:

  Google Workspace Setup Guide

• Question 96:

  Which management feature makes ChromeOS devices a popular choice for IT administrators in educational organizations and enterprises?

  A. Inability to remotely control and monitor devices
  B. Centralized management through Admin console
  C. Remote BIOS controls and firmware update
  D. Secure management through on-prem infrastructure
  B. Centralized management through Admin console

  ---

  Explanation

  ChromeOS devices are favored in educational and enterprise settings due to their centralized management via the Google Admin console. This tool allows IT administrators to manage thousands of devices from a single interface, applying

  policies, updates, and monitoring remotely.

  Verified Answer from Official Source:

  The correct answer is verified from theChromeOS Enterprise Management Guide, which emphasizes the use of the Admin console for device and user management.

  "The Admin console provides a centralized platform to manage ChromeOS devices, including policy application, device monitoring, and updates."

  This feature streamlines management tasks, saving time and ensuring consistent policy enforcement across an organization.

  Objectives:

  Efficient device management in enterprise environments. Utilize the Admin console for centralized control.

  References:

  ChromeOS Enterprise Management Guide

• Question 97:

  In regular user mode, how does an admin open the crosh shell on a ChromeOS device to run a ping command?

  A. Ctrl + Alt + V
  B. Ctrl + Alt + t
  C. Ctrl + Alt + Tab +W
  D. Ctrl + Alt + i
  B. Ctrl + Alt + t

  ---

  Explanation

  In regular user mode on a ChromeOS device, pressingCtrl + Alt + topens the crosh shell (Chrome OS developer shell), a command-line interface. From there, you can execute various commands, includingpingto test network connectivity. Other options are incorrectbecause they either have no assigned function or trigger different actions in ChromeOS.

• Question 98:

  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?

  A. SSO settings are misconfigured
  B. The account is in the wrong OrgUnit
  C. Third-party SSO is not enabled
  D. Super admin bypassed the thud-patty
  D. Super admin bypassed the thud-patty

  ---

  Explanation

  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.

• Question 99:

  A user reports that their Chrome device has been stolen. What should the administrator do?

  A. Use the Google Admin console to turn on the stolen Chromebook's webcam
  B. Use the Google Android Device Manager to locate the Chromebook
  C. Set the stolen Chromebook lo disabled mode to prevent user sign-ins
  D. Remotely wipe user data from the Chromebook
  C. Set the stolen Chromebook lo disabled mode to prevent user sign-ins

  ---

  Explanation

  When a Chrome device is reported stolen, the administrator should immediately take action to protect the data and prevent unauthorized access. The most effective step is to disable the device through the Google Admin console. This will prevent anyone from signing in to the device, rendering it unusable. Here's how to disable a stolen Chrome device: Sign in to Google Admin console: Use your administrator credentials. Navigate to Devices: Go to Devices > Chrome > Devices. Locate the Device: Find the stolen device using its serial number or other identifying information. Disable the Device: Click on the device and select "Disable." This will disable the device and prevent anyone from signing in, even if they try to reset the device.

• Question 100:

  Which management feature makes ChromeOS devices a popular choice for IT administrators in educational organizations and enterprises? Which management feature makes ChromeOS devices enterprises?

  A. Secure management through on prem infrastructure
  B. Remote BIOS controls and firmware update
  C. Centralized management through Admin console
  D. Inability to remotely control and monitor devices
  C. Centralized management through Admin console

  ---

  Explanation

  The ChromeOS Admin console provides centralized management, making it a popular choice for IT administrators. It allows them to manage policies, apps, extensions, and device settings from a single interface, streamlining administration and ensuring consistency across devices. Option A is incorrectbecause ChromeOS management is primarily cloud-based, not on- premises. Option B is incorrectbecause while BIOS control might be available, it's not the primary management feature. Option D is incorrectbecause ChromeOS devices can be remotely controlled and monitored through the Admin console.

  References: About ChromeOS device management: https://support.google.com/chrome/a/answer/1289314?hl=en