You need to set a policy that prevents the device from shutting down while idling on the sign-in screen. Where should you navigate to?
To prevent a ChromeOS device from shutting down while idling on the sign-in screen, you need to adjust the power management settings. This can be done through the following steps:
Go to the Google Admin console.
Navigate to Device Management > Chrome Management > Device Settings.
Find the Power management section and locate the setting that controls idle behavior on the sign-in screen.
Adjust the setting to prevent shutdown during idle periods.
Option A is incorrect because idle settings primarily control screen dimming and sleep behavior.
Option B is incorrect because user experience settings generally focus on visual and interaction aspects, not power management.
Option C is incorrect because there isn't a specific 'Allow shutdown' setting in ChromeOS device settings.
What should an administrator do to view the number and type of ChromeOS upgrades purchased and in use by their domain?
To view the number and type of ChromeOS upgrades purchased and in use, administrators should check the 'Subscriptions' section in the billing area of the Google Admin console. This section provides a clear overview of the organization's ChromeOS upgrade subscriptions and usage.
Other options are incorrect because they don't directly provide information about ChromeOS upgrade subscriptions:
Option A (Verify upgrades on devices page): Shows upgrades on individual devices, not the overall purchase and usage.
Option C (Contact partner to verify): Unnecessary if the information is readily available in the Admin console.
Option D (Check reports page for upgrades): Might provide some usage data, but not the purchase details.
Sign in to your Admin console: https://support.google.com/chrome/a/answer/182076?hl=en
Which site isolation policy will enable site isolation for your entire organization?
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/
The security team is requiring Wi-Fi connectivity to be disabled on ChromeOS devices. Using the Google Admin console, how would you configure ChromeOS devices to block all WI-FI connectivity and hide the WI-FI Icon?
To completely disable Wi-Fi and hide the Wi-Fi icon on ChromeOS devices, you need to modify the 'Network' settings in the Google Admin console:
Go to 'Device Management' > 'Chrome Management' > 'Device Settings'.
Select the organizational unit (OU) containing the devices you want to manage.
Under 'Network', find 'Enabled network interfaces' and remove 'Wi-Fi' from the list.
Save the changes.
This will disable Wi-Fi adapters on the devices and hide the Wi-Fi icon, preventing users from connecting to Wi-Fi networks.
Why other options are incorrect:
A . Restricted Wi-Fi Networks: This setting only limits which networks users can connect to, not disable Wi-Fi entirely.
B . Prevent WiMax connectivity: WiMax is a different wireless technology and not relevant to Wi-Fi.
D . Restrict 'Auto Connecting' to Wi-Fi: This only prevents automatic connection to networks but doesn't disable Wi-Fi entirely.
A customer has a mission-critical workload running on ChromeOS and needs devices configured to reduce ChromeOS changes. How can an admin reduce the risk of an unexpected change in an OS update affecting the customer's entire ChromeOS device domain while maintaining security and minimizing admin workload?
Update rollout plans in the Google Admin console allow administrators to gradually roll out ChromeOS updates to a subset of devices first. This allows for testing in a controlled environment before deploying to the entire fleet, reducing the risk of unexpected issues impacting all devices.
Steps to add an update rollout plan:
Access Google Admin Console:Sign in with your administrator credentials.
Navigate to Device Management:Go to Devices > Chrome > Settings > Updates.
Create Rollout Plan:Click on 'Add an update rollout plan.'
Select Devices:Choose the specific devices or organizational units (OUs) to include in the initial rollout.
Set Timeline:Define the start and end dates for the rollout.
Save and Apply:Save the plan and apply it to the selected devices.
