Your hardware OEM issues a recall for a safety issue. You need to deprovision devices from management before returning to the OEM. They will replace your existing ChromeOS devices with a different model. Which option should you choose when deprovisioning to make sure you can reuse your Chrome Education/Enterprise Upgrade and remain compliant?
Answer : B
When deprovisioning ChromeOS devices for a hardware recall and replacement with different models, choosing the 'Different model replacement' option is crucial to retain the Chrome Education/Enterprise Upgrade license compliance. This option ensures that the license is transferred to the new device correctly, avoiding any compliance issues or the need to repurchase licenses.
Here's why this option is important:
License Transfer:It specifically designates the deprovisioning as being due to a hardware replacement with a different model.This triggers the system to transfer the license to the new device upon enrollment.
Compliance:It maintains the compliance of your Chrome Education/Enterprise Upgrade licenses,ensuring you don't violate any licensing terms.
Cost Savings:It avoids the need to purchase new licenses for the replacement devices,saving your organization money.
A user reports that their Chrome device has been stolen. What should the administrator do?
Answer : C
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.
What is needed for an admin to remote desktop to a user or managed guest session devices with the Admin console?
Answer : A
To initiate a remote desktop session to a ChromeOS device using the Admin console, the administrator needs the user's consent. The remote desktop feature works by sending a connection request to the user's device, which they must explicitly accept before the session can start. This ensures user privacy and prevents unauthorized access.
Your security team asks you to deploy on ChromeOS only a specific Android app for your security department. As a ChromeOS Administrator, you need to find a way to block all other Android apps except the one that you need. How are you going to proceed?
Answer : B
Access Google Admin Console:Sign in to your Google Admin console.
Navigate to Device Management:Go to Devices > Chrome > Settings > Users & browsers.
Locate Play Store Settings:Find the section related to the Play Store.
Enable Allowlist Policy:Activate the policy 'Block all apps,admin manages allowlist.'
Add the Security App:Go to the 'Apps & extensions' section and add the specific Android app that you want to allow for the security team's organizational unit (OU).
This configuration ensures that all other Android apps are blocked from installation on ChromeOS devices, except the specified security app. This provides granular control over app deployment and enhances security by preventing unauthorized app usage.
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?
Answer : A
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.
A large marketing company hires interns in the IT department. The interns should see only info from ChromeOS devices but should not be able to manage or update any device.
How should an admin assign this role to Interns?
How should an admin assign this role to interns?
Answer : B
To grant interns read-only access to ChromeOS device information without management or update capabilities, you should:
Create Custom Role: In the Google Admin console, navigate to 'Device management' -> 'Chrome management' -> 'User settings' -> 'Roles.'
Assign Telemetry API Role: Within the custom role, assign the 'Telemetry API' role. This allows interns to view device information collected through the API but not make changes.
Exclude Other Roles: Ensure no other roles are assigned that grant management or update permissions.
Option A is incorrect because it involves service admin roles, which typically have broader administrative access.
Option C is incorrect because the 'Settings' role might grant more permissions than intended.
Option D is incorrect because the 'Manage ChromeOS devices' role grants full management capabilities, which is not suitable for interns.
Chrome Browser Cloud Management API: https://developers.google.com/chrome/policy
In regular user mode, how does an admin open the crosh shell on a ChromeOS device to run a ping command?
Answer : B
In regular user mode on a ChromeOS device, pressing Ctrl + Alt + t opens the crosh shell (Chrome OS developer shell), a command-line interface. From there, you can execute various commands, including ping to test network connectivity.
Other options are incorrect because they either have no assigned function or trigger different actions in ChromeOS.