Google ChromeOS Administrator Practice Test - Questions Answers, Page 4

List of questions
Question 31

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?
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.
https://support.google.com/chrome/a/answer/3523633
Question 32

The security department has been informed that a ChromeOS device was stolen out of an employee's car. What should you do in the Admin console to ensure the device Is rendered Inoperable while still maintaining management of the device?
Disabling a ChromeOS device in the Admin console prevents it from booting up or being used, effectively rendering it inoperable. However, it retains the device's association with the organization, allowing administrators to track its location and manage it remotely if recovered.
The other options are not as suitable:
Tagging as stolen: Doesn't prevent device usage.
Powerwash: Removes all data and enrollment, making management impossible.
Deprovision: Removes device association, making management impossible.
Question 33

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?
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.
Set up Chrome browser on managed devices: https://support.google.com/chrome/a/answer/3523633?hl=en
Question 34

Which setting is required to restrict Chrome Remote Desktop use to only accounts on your domain?
Within the 'Chrome Remote Desktop' settings in the Google Admin console, the option 'Remote access clients' allows you to restrict access to Chrome Remote Desktop based on the domain of the user accounts. By configuring this setting, you can ensure that only users with accounts on your specific domain can access Chrome Remote Desktop on the managed devices.
Why other options are incorrect:
A . Firewall traversal: This setting controls whether Chrome Remote Desktop can bypass firewalls to establish connections, but it does not restrict access based on domain.
B . URL Blocking: This setting controls which websites users can access but does not specifically apply to Chrome Remote Desktop access based on domain.
D . Chrome Remote Desktop review: This setting allows administrators to review Chrome Remote Desktop sessions but does not restrict access based on domain.
Question 35

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?
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 36

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

You have a number of applications that you rely upon. You want to ensure that your applications continue to run smoothly with each new version of Chrome. What should you do?
Question 38

You want to enterprise enroll a device that has existing consumer accounts. What should you do first?
Question 39

You have been tasked with selecting a 3rd party IdP to allow logging into ChromeOS devices. Your ChromeOS devices are displaying an 'Unable to sign in to Google' message. How should you troubleshoot this?
Question 40

As an administrator, you would like the ability to see and test upcoming changes to the Google Admin console. How would an admin get access to pre-release features and upcoming ChromeOS device management changes to the Admin console?
Question