Question 1

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?

Accepted Answer

C

Explanation: The best way to handle this situation is to create Change 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 the Google 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. Reference: Google Workspace Deployment Guide

Question 2

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?

Accepted Answer

B

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 incorrect because while instructional guides are helpful, they are a secondary concern to device suitability. Option C is incorrect because security patch timing is important but not the initial consideration when choosing devices. Option D is incorrect because while specifications matter, they should align with the chosen form factor and user needs.

Question 3

At a specific location in your organization, users cannot log in to their ChromeOS devices. The
ChromeOS Administrator has also noticed that devices have not synced in the past 24 hours. You
have updated policies In the Admin console for your fleet of ChromeOS devices, but the devices are
not getting the updated policies. What is a probable change in the environment that can cause these
issues?

Accepted Answer

B

Explanation: Blocking all network traffic to Google services would prevent ChromeOS devices from communicating with Google servers. This would lead to several issues: Login failures: ChromeOS devices require access to Google services for user authentication and login. Sync failures: ChromeOS relies on Google services to sync user data, settings, and policies. Policy updates not received: ChromeOS devices fetch policy updates from Google servers, so blocking access would prevent them from getting updates. Why other options are less likely: A . New devices enrolled: While enrolling new devices might cause some temporary network congestion, it wouldn't typically block all communication with Google services. C . Root CA expiration: This would affect secure connections to websites, but not necessarily prevent all communication with Google services. D . Expired licenses: Expired licenses would restrict access to some features but wouldn't prevent basic login and sync functionality.

Question 4

You have been tasked to deploy shared devices using Managed Guest Sessions. Your IT policy
requires blocking access to "google.com" at the parent organization. How would you prevent users
from accessing "google.com" for all Managed Guest Sessions at the parent organization?

Accepted Answer

D

Explanation: To block access to a specific website across all managed guest sessions, you need to add the site to the "list of blocked URLs". This ensures that regardless of the session type, users cannot access the specified site. Verified Answer from Official Source: The correct answer is verified from the Google ChromeOS Managed Guest Session Guide, which explains that adding URLs to the blocked list restricts access across all sessions. "To enforce web filtering policies during Managed Guest Sessions, add the URL to the blocked list in the Admin console under User & Browser Settings." By configuring the blocked URL list, you enforce consistent access policies even when devices are used in guest mode. Objectives: Implement web filtering for Managed Guest Sessions. Enforce consistent security policies across sessions. Reference: Google ChromeOS Managed Guest Session Guide

Question 5

You have Long-term Support enabled for all devices within a particular OU. How often will these devices receive a feature update?

Accepted Answer

B

Explanation: 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. Reference: ChromeOS Long-Term Support (LTS) Policy Documentation

Question 6

What are two methods for signing in to a Chrome OS device? Choose 2 answers

Accepted Answer

B, D

Explanation: Single sign-on (SSO): This allows users to sign in to their Chrome OS device using their organizational credentials. This is particularly useful in enterprise or educational settings where users already have an existing account. Facebook Connect: This allows users to sign in to their Chrome OS device using their Facebook credentials. This can be convenient for users who are already logged into Facebook on another device. Options A and C are incorrect: SMS code sent to mobile phone: This is not a standard sign-in method for Chrome OS devices. Google Friend Connect: This was a social networking service that has been discontinued.

Question 7

You want users to sign in to ChromeOS devices via SAML Single Sign-On and be able to access
websites and cloud services that rely on the same identity provider without having to re-enter
credentials. How should you configure SAML?

Accepted Answer

B

Explanation: To achieve seamless SSO between ChromeOS devices and other web services using the same identity provider, you need to configure SAML SSO in the Google Admin console: Enable SAML-based SSO for ChromeOS devices. In the SSO settings, find the Single Sign-On cookie behavior and set it to "Enable transfer of SAML SSO cookies into user sessions during login." This allows the SAML authentication cookie to be passed between the ChromeOS login and other web services, eliminating the need for re- authentication. Option A is incorrect because it relates to the initial login method, not cookie transfer for subsequent SSO. Options C and D are incorrect because they involve application-specific SSO configurations, not the general SAML SSO setup for the device.

Question 8

Your organization has automatic ChromeOS updates implemented. Your CTO would like to review the
documentation on what changes each new version has. How would you assist your CTO in
accomplishing this goal?

Accepted Answer

D

Explanation: The "Chrome Release Notes Support" page is the official resource for detailed information about new features, security updates, and bug fixes in each ChromeOS version. It's specifically designed to keep administrators and users informed about changes. Why other options are incorrect: A (Support ticket): While Google support can help, it's not the most efficient way to access release notes. B (YouTube): Unofficial sources may not be accurate or complete. C (chrome://updates): This only shows the update status of the browser, not detailed release notes. To assist your CTO in reviewing the documentation on changes each new version of ChromeOS has, you should direct them to the official Chrome Release Notes page. Here’s how you can guide them: Open a web browser and navigate to the official Chrome Releases blog. On this page, you can find detailed release notes for each new version of ChromeOS. These notes include information on new features, security updates, bug fixes, and more. The release notes are categorized by channel (Stable, Beta, Dev) and provide a comprehensive overview of what has changed in each update. For example, the Stable Channel Update for ChromeOS / ChromeOS Flex provides details on the latest stable version updates1. Reference: The Chrome Releases blog is the official source for release notes and update information for ChromeOS1. It is regularly updated by Google and is the best place to find detailed documentation on the changes included in each new version of ChromeOS.

Question 9

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?

Accepted Answer

A

Explanation: Before disposing of ChromeOS devices, it is essential to deprovision them. 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 the Google 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. Reference: Google Admin Console Device Management Guide

Question 10

What format of certificate encoding is incompatible with ChromeOS devices?

Accepted Answer

C

Explanation: ChromeOS primarily uses the PEM format for certificate encoding. While it can handle other formats like CER and CRT, it does not support the DER format. DER is a binary format, while ChromeOS requires certificates in a text-based format.

Question 11

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

Accepted Answer

D, E

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. Reference: Recover your Chromebook: https://support.google.com/chromebook/answer/1080595?hl=en

Question 12

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

Accepted Answer

C

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 13

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?

Accepted Answer

B

Explanation: The best practice for preparing a ChromeOS device for a new user while keeping it managed is to enable forced-reenrollment and then factory 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 the ChromeOS 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. Reference: ChromeOS Device Reassignment Guide

Question 14

You are tasked with reducing the risk of a breach of your organization's identities. What should you do to minimize the risk?

Accepted Answer

C

Explanation: 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. Reference: Google Workspace Security Guide

Question 15

A global organization is deploying ChromeOS devices to all of their users. Corporate policy requires
all web traffic to be filtered using an existing enterprise solution such that employees cannot access 1
million unauthorized websites. What should you configure to meet this requirement?

Accepted Answer

B

Explanation: The most effective way to ensure that all web traffic is filtered is to enforce the use of a web proxy via user policy. By configuring the ChromeOS devices to use a proxy server, all internet traffic will be routed through the proxy, where filtering rules are applied. Verified Answer from Official Source: The correct answer is verified from the Google ChromeOS Network Management Guide, which recommends using a web proxy to manage and filter web traffic efficiently. "To enforce web filtering policies, configure a web proxy through user policies. This ensures that all internet traffic passes through the filtering system." Web proxies allow IT administrators to manage and restrict access to websites centrally, providing consistent and scalable content filtering across the organization. Objectives: Implement web filtering using a proxy. Enforce secure internet access policies. Reference: Google ChromeOS Network Management Guide

Free Google ChromeOS-Administrator Actual Exam Questions