QUESTION: 25

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?

Tag the ChromeOS device as stolen
Disable the ChromeOS device
Powerwash the ChromeOS device
Deprovision the ChromeOS device

Answer(s): B

Explanation:

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.

Reveal Solution Next Question

QUESTION: 26

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?

Enable the 'User and Browser Settings" and update 'Maximum user session length* to any time up to 24 hours
Create a corporate policy stating (he users are to manually sign out after the end of every shift
You can remotely access each device and sign out of the user account using Chrome Remote Desktop
Force-install a custom app to each device in question that notifies the user that they need to sign out of their device after 24 hours

Answer(s): A

Explanation:

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.

Reference:

Set up Chrome browser on managed devices:
https://support.google.com/chrome/a/answer/3523633?hl=en

Reveal Solution Next Question

QUESTION: 27

Which setting is required to restrict Chrome Remote Desktop use to only accounts on your domain?

Firewall traversal
URL Blocking
Remote access clients
Chrome Remote Denton review

Answer(s): C

Explanation:

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.

Reveal Solution Next Question

QUESTION: 28

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?

A different location enrolled a large number of new devices
Your network administrator has blocked all network traffic to Google services
Your root Certificate Authority expired
Your organization's licenses have recently expired

Answer(s): 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.

Reveal Solution Next Question

Free ChromeOS-Administrator Exam Braindumps (page: 7)

QUESTION: 25

Explanation:

QUESTION: 26

Explanation:

Reference:

QUESTION: 27

Explanation:

QUESTION: 28

Explanation: