Google Professional ChromeOS Administrator Exam Questions

Answer : B

To enroll a previously used device, it must first be wiped to remove any prior user data or configuration. The device must then go through the out-of-box experience (OOBE) as if it were new. During the initial setup screen, pressing CTRL+ALT+E will start the enterprise enrollment process.

Verified Answer from Official Source:

The correct answer is verified from the Google Admin Console Guide, which details the steps required for re-enrolling previously used ChromeOS devices.

'To re-enroll a device, perform a factory reset (Powerwash), and during the initial login screen, press CTRL+ALT+E to initiate the enrollment process.'

This method ensures that any residual configuration or data from the previous user is completely removed before re-enrollment, ensuring a clean setup.

Objectives:

Enroll used ChromeOS devices.

Maintain consistent device management.

Google Admin Console Guide - Device Enrollment

Answer : A

To set up Zero-Touch Enrollment (ZTE), an administrator must go to Devices > Chrome > Enroll within 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 the Google 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.

Google ChromeOS Zero-Touch Enrollment Guide

Answer : A

To ensure that all web traffic is filtered according to organizational policy, configure the ChromeOS devices to 'Always use the proxy specified below' and provide the URL to the PAC (Proxy Auto-Config) file. The PAC file contains logic to determine which proxy server to use for specific URLs, allowing dynamic and flexible proxy configurations.

Verified Answer from Official Source:

The correct answer is verified from the Google ChromeOS Proxy Configuration Guide, which outlines using a PAC file to configure web filtering for large-scale deployments.

'Use the 'Always use the proxy specified below' setting and specify the URL to the PAC file to enforce consistent web filtering across all ChromeOS devices.'

PAC files are commonly used to direct traffic through specific proxies based on URL patterns, which is ideal for managing large lists of restricted websites efficiently.

Objectives:

Configure ChromeOS devices to use web proxies.

Enforce consistent web filtering through proxy settings.

Google ChromeOS Proxy Configuration Guide

Answer : D

If a ChromeOS device has previously been signed in to, you must wipe the device (Powerwash) before enrolling it into the enterprise. This ensures that any existing user data and previous configurations are removed, allowing the device to start the enrollment process as new.

Verified Answer from Official Source:

The correct answer is verified from the Google ChromeOS Device Enrollment Guide, which specifies that devices must be wiped to remove any previous user associations before enterprise enrollment.

'To enroll a previously used device, perform a factory reset (Powerwash) to ensure it is in a clean state, ready for enterprise enrollment.'

Wiping the device ensures that it is free from personal settings or residual user data, which might conflict with enterprise policies.

Objectives:

Enroll ChromeOS devices in an enterprise environment.

Maintain compliance with managed device policies.

Google ChromeOS Device Enrollment Guide

Answer : B

ChromeOS devices configured for Long-term Support (LTS) receive feature updates every 6 months. LTS is designed for organizations that require stability and predictability in their device environment, minimizing disruptions caused by frequent updates.

Verified Answer from Official Source:

The correct answer is verified from the ChromeOS Long-Term Support (LTS) Policy Documentation, which clearly states that updates under LTS are delivered every 6 months.

'LTS updates are released approximately every 6 months, providing stability and minimizing changes while maintaining security updates.'

LTS is ideal for educational institutions and enterprises that prioritize stability over cutting-edge features, as it reduces the frequency of significant changes.

Objectives:

Manage ChromeOS updates efficiently.

Implement Long-term Support policies.

ChromeOS Long-Term Support (LTS) Policy Documentation

Answer : A

The SitePerProcess policy enables site isolation for the entire organization. This means that each website opened in Chrome will run in its own dedicated process, improving security and stability by isolating potential vulnerabilities and preventing one compromised site from affecting others.

Option B (IsolateOrigins) and Option D (SiteOrigins) are not valid policy names.

Option C (IsolatePerProcess) is close but not the exact name of the policy.

Site Isolation in Google Chrome: https://www.chromium.org/Home/chromium-security/site-isolation/

Answer : C

Setting up Single Sign-On (SSO) significantly reduces identity risks by centralizing authentication through a secure, verified identity provider (IdP). This method helps ensure consistent password policies, multi-factor authentication (MFA), and robust security practices. It also minimizes the risk of password reuse and phishing.

Verified Answer from Official Source:

The correct answer is verified from the Google Workspace Security Guide, which recommends implementing SSO to manage authentication securely.

'Single Sign-On (SSO) allows users to access multiple applications with a single set of credentials, reducing the risk of identity breaches by centralizing authentication.'

SSO enhances security by integrating with trusted IdPs, implementing MFA, and reducing credential exposure across multiple applications.

Objectives:

Strengthen identity and access management (IAM).

Implement secure authentication practices with SSO.

Google Workspace Security Guide