最新のChromeOS-Administrator試験問題集でGoogle試験にはトレーニングを提供しています
合格できるGoogle Professional ChromeOS Administrator ExamのPDF問題集は最近更新された62問あります
Google ChromeOS-Administrator 認定試験の出題範囲：
| トピック | 出題範囲 |
|---|---|
| トピック 1 |
|
| トピック 2 |
|
| トピック 3 |
|
| トピック 4 |
|
| トピック 5 |
|
質問 # 25
What is needed for an admin to remote desktop to a user or managed guest session devices with the Admin console?
- A. The user must share the session pin with the admin
- B. The user must accept the connection request
- C. The admin must be in the same OU as the remote device
- D. Both the admin and the remote device must be on the same network
正解：B
解説：
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.
質問 # 26
When setting up a Chrome Enterprise trial, what is a benefit of choosing to verify the domain?
- A. Identity management
- B. Application management
- C. Network management
- D. Device management
正解：A
解説：
When you verify your domain during a Chrome Enterprise trial setup, you establish ownership and control over the domain within Google's systems. This is a crucial step in identity management as it allows you to:
* Manage user accounts: Create, edit, and delete user accounts within the domain, ensuring control over who can access company resources.
* Apply security policies: Enforce security policies like password requirements, two-factor authentication, and access controls for users within the domain.
* Single Sign-On (SSO): Enable seamless and secure single sign-on for users across various Google services and other integrated applications.
By verifying the domain, you essentially gain centralized control over user identities and their access to resources, which is a core aspect of identity management.
質問 # 27
An organization has created organization units within the Google Admin console for additional management structure. What is the most effective way to manage each OU while not affecting the top-level OU policy?
- A. Disable auto updates
- B. Override the inheritance for a given policy
- C. Force inheritance from top level OU to all OUs
- D. Delete sublevel OUs and only work from the top level OU
正解：B
解説：
Overriding inheritance allows you to apply specific policies to individual OUs without affecting the policies of the parent OU or other sibling OUs. This gives you granular control over different groups of users or devices.
Other options are incorrect because:
* A: Deleting sub-level OUs would remove the management structure and negate the purpose of having OUs.
* B: Disabling auto-updates would prevent devices from receiving important security and feature updates.
* D: Forcing inheritance would apply the top-level OU policy to all sub-OUs, preventing customization.
References:
* https://support.google.com/chrome/a/answer/187202
質問 # 28
You are using a third-party service for SSO. Users are confused when signing onto a Chrome device because they are asked for Google account details before being redirected to the sign-In screen for your SSO provider Which setting must be changed so managed devices open the SSO provider login page by default?
- A. Single sign-on IdP redirection
- B. SAML single sign-on password synchronization flows
- C. SAML single sign-on login frequency
- D. Single sign-on cookie behavior
正解：A
解説：
The Single sign-on IdP redirection setting controls whether managed devices directly open the login page of the third-party SSO provider (Identity Provider) or first prompt for Google account credentials. By enabling this setting, you streamline the login process for users and eliminate the confusion caused by the extra Google account prompt.
Option A is incorrect because it controls the frequency of re-authentication for SAML SSO, not the initial login page.
Option B is incorrect because it relates to password synchronization between Google and the IdP, not the login page redirection.
Option C is incorrect because it deals with how cookies are handled for SSO, not the login page redirection.
質問 # 29
How would you deploy a Progressive Web Application to all managed user accounts?
- A. Go to "User & Browser Settings" and add the Progressive Web Application URL in the "Legacy Browser Support" site list
- B. Open "Additional Google services" to force-install the Progressive Web Application URL
- C. Force-install the Progressive Web Application URL in the "Chrome Apps & extensions" page
- D. Set up Chrome Imprivata shared apps & extensions to force-install the Progressive Web Application URL
正解：C
質問 # 30
You need to get to the enterprise enrollment screen. What should you do?
- A. Press Ctrl-Alt-F on the initial welcome screen to set initial settings
- B. Press Ctrl-Alt-E during the Chrome bootup sequence (Chrome logo animation)
- C. Sign in with enterprise enrollment credentials provided by the customer at the user sign-in screen
- D. Press Ctrl-Alt-E at the user login screen before any user has signed in to the device
正解：B
解説：
* Power on or reboot the Chromebook.
* Watch for the Chrome logo animation. This is the key moment to trigger enterprise enrollment.
* Press Ctrl+Alt+E simultaneously. This keyboard shortcut interrupts the normal boot process and redirects the Chromebook to the enterprise enrollment screen.
* Follow the on-screen instructions. You'll be prompted to enter information such as the domain name of the organization and enrollment credentials.
Why this is the correct method:
* Enterprise Enrollment Timing: The Ctrl+Alt+E shortcut is specifically designed to be used during the bootup sequence, before any user profile is loaded. This ensures the device is enrolled in the organization's management system from the start.
* Alternative Options: The other options mentioned are incorrect:
* B (Sign in with credentials): This assumes the device is already enrolled and is used for regular user login.
* C (Ctrl+Alt+F): This shortcut is used for accessing the ChromeOS developer shell (Crosh) and is
* not related to enrollment.
* D (Ctrl+Alt+E at login): While technically possible to enroll at the login screen, it's not the recommended method as it might not apply settings correctly to all user profiles.
References:
* Enroll a Chrome device: https://support.google.com/chrome/a/answer/1360534?hl=en
質問 # 31
You want to restrict who can sign in to a managed device during working hours. Which two settings do you need to use?
Choose 2 answers
- A. Device oft hours
- B. Single sign-on IdP redirection
- C. User Data (Ephemera))
- D. Family Link accounts
正解：A、D
解説：
* Device off hours: This setting allows you to specify times when the device cannot be used, effectively restricting access to certain hours.
* Family Link accounts: Family Link is a parental control app that allows you to manage a child's account and device usage. By requiring Family Link accounts, you can enforce sign-in restrictions for younger users.
Other options are incorrect because:
* A: Single sign-on (SSO) redirection simplifies sign-in for authorized users, but doesn't inherently restrict access.
* C: User Data (Ephemeral) controls whether user data is saved locally, but doesn't restrict sign-in.
References:
* https://support.google.com/chrome/a/answer/3523633
* https://families.google.com/familylink/
質問 # 32
You are a ChromeOS Administrator of a school district While working with a teacher in one of the schools, they mention they are having issues downloading files on their ChromeOS device. What are some ways you can help troubleshoot with the least amount of disruption to the user?
- A. Reset the user's ChromeOS device to its original factory settings
- B. Run Diagnostics from the ChromeOS device to troubleshoot
- C. Check how much storage Is being used on the device then delete or move files that aren't needed anymore
- D. Check for system updates If any updates are available install them
正解：C
解説：
When a teacher is having issues downloading files on their ChromeOS device, it's important to troubleshoot with minimal disruption. Here are steps to address the issue:
* Check Storage: Start by checking the available storage on the device. If the storage is full or nearly full, it could prevent new files from being downloaded.
* Manage Files: Guide the teacher to delete or move files that are no longer needed. This can be done through the Files app on the ChromeOS device.
* Clear Cache: If storage isn't the issue, clearing the browser cache can sometimes resolve download problems.
* Check Network: Ensure that the device has a stable internet connection, as an unstable connection can
* interrupt downloads.
References:The troubleshooting steps are based on common practices for resolving download issues on ChromeOS devices and Google's support documentation on fixing file download errors1. These steps are designed to resolve issues without causing significant disruption to the user's experience.
* Insufficient Storage: A common reason for download failures on ChromeOS devices is insufficient storage space. Checking the available storage is a simple first step:
* Click on the system tray (bottom right corner) and select the Settings gear icon.
* In the Settings menu, navigate to the "Device" section and select "Storage Management."
* Review the storage usage. If it's nearly full, identify large files or unused apps that can be removed.
* Guide the teacher on how to delete files or move them to Google Drive.
* System Updates: Outdated software can sometimes lead to bugs or glitches. Ensuring the ChromeOS device is up-to-date is important:
* In the Settings menu, navigate to the "About ChromeOS" section.
* Click on "Check for updates." If any updates are found, install them.
* If updates are pending, ask the teacher to restart the device after the installation.
* Additional Troubleshooting (If necessary):
* Check Network Connectivity: Ensure the device is connected to a stable Wi-Fi network. Have the teacher try accessing a different website to verify internet access.
* Clear Browser Cache: In the Chrome browser, open the Settings menu, navigate to "Privacy and security," and select "Clear browsing data." Clear the cache for the past hour or day.
Why Other Options Are Less Ideal:
* A. Run Diagnostics: While diagnostics can be helpful, they are a more time-consuming step and might not be necessary if the issue is simply related to storage or updates.
* C. Reset the Device: This is a drastic measure that should only be considered if other troubleshooting steps fail. It involves wiping the user's data and settings, which is disruptive.
質問 # 33
Your network administrator wants to block Google services traffic. What is the result?
- A. Chrome devices will crash
- B. Google Search will not work
- C. Nothing This isn't an issue
- D. Chrome devices will not be able to reach Google
正解：B
解説：
Blocking Google services traffic will prevent Chrome devices from accessing any Google-owned domains, including google.com. This will directly impact Google Search, as it relies on communication with Google servers to provide results.
Other Google services like Gmail, YouTube, Google Drive, etc., will also be inaccessible. However, the Chrome device itself will not crash, as it can still function with other websites and applications.
質問 # 34
You are enrolling several devices to send to a remote location. How can you ensure that these devices will automatically connect to the wireless network at the remote location when powered on for the first time?
- A. During the enrollment process add the wireless credentials manually to each device in the Admin console ensuring that they are applied to ChromeOS devices By User
- B. Use the Google Zero-Touch Enrollment (ZTE) process and generate the provisioning token by clicking on the 'Enroll device' button in the Admin console ''Devices'' page
- C. Add the wireless network credentials to the 'Networks" section in the Admin console ensuring that they are applied to the ChromeOS devices By User
- D. Add the wireless network credentials to the "Networks" section in the Admin console ensuring that they are applied to the ChromeOS devices By Device
正解：D
解説：
To ensure ChromeOS devices automatically connect to a specific wireless network upon initial power-on at a remote location, follow these steps in the Google Admin console:
* Navigate to Device Management > Chrome Management > Networks.
* Add the Wi-Fi network credentials (SSID and password) to the list of networks.
* Set the network configuration to apply By Device. This ensures that the credentials are pushed to the device itself, not tied to a specific user.
When the devices are powered on at the remote location, they will automatically detect and connect to the configured Wi-Fi network without requiring any manual intervention from the user.
Option B (Zero-Touch Enrollment) simplifies the initial setup process but doesn't automatically configure Wi-Fi.
Options C and D are incorrect because applying network settings by user won't ensure automatic connection on first boot before any user logs in.
質問 # 35
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?
- A. Disable the ChromeOS device
- B. Powerwash the ChromeOS device
- C. Tag the ChromeOS device as stolen
- D. Deprovision the ChromeOS device
正解：A
解説：
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.
質問 # 36
An admin is setting up third-party SSO for their organization as the super admin. When they test with their account, they do not see the SSO screen.
What is causing this behavior?
- A. SSO settings are misconfigured
- B. Third-party SSO is not enabled
- C. Super admin bypassed the thud-patty
- D. The account is in the wrong OrgUnit
正解：C
解説：
Super administrators in Google Workspace have special privileges that allow them to bypass certain security features, including third-party SSO. This is to ensure that they can always access the Admin console for troubleshooting or critical changes, even if the SSO system is malfunctioning. Therefore, when a super admin tests third-party SSO, they won't be prompted with the SSO login screen, but will directly access the console using their Google credentials.
質問 # 37
You need to create a recovery image on a USB stick. Which two steps should you take?
Choose 2 answers
- A. Go to Device Settings
- B. Go to Google Play store
- C. Go to Chrome Web Store on a Chrome device
- D. Install Chrome Recovery Utility and download the image for the coned device model to a USB stick
- E. Go lo google com/chromebooks
正解：C、D
解説：
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.
References:
* Recover your Chromebook: https://support.google.com/chromebook/answer/1080595?hl=en
質問 # 38
When setting up a Chrome Enterprise trial, what is a benefit of choosing to verify the domain?
- A. Identity management
- B. Application management
- C. Network management
- D. Device management
正解：A
質問 # 39
How should you use Chrome Remote Desktop from the Google Admin console to connect a user?
- A. Open Chrome Remote Desktop and type the user's user name
- B. Find the device and click remote desktop
- C. Find the user account and click remote desktop
- D. Open Chrome Remote Desktop and type the device serial number
正解：B
解説：
To initiate a remote desktop session to a ChromeOS device using the Google Admin console, follow these steps:
* Sign in to Google Admin console: Use your administrator credentials.
* Navigate to Devices: Go to Devices > Chrome > Devices.
* Locate the Device: Find the device you want to connect to using its serial number or other identifying information.
* Start Remote Desktop Session: Click on the device and select "Remote desktop." This will send a connection request to the user, who must accept it before the session can start.
質問 # 40
An organization was recently hacked through an admin's choice of an operating system. Leadership decides to move to Chromebooks for their security.
While the organization waits for Chromebooks to be delivered, what will allow them to continue using their existing devices securely?
- A. ChromeOS Managed Browser
- B. ChromeOS Flex
- C. ChromeOS Readiness Guide
- D. ChromeOS Bytes
正解：B
解説：
ChromeOS Flex allows the organization to repurpose existing devices by installing a lightweight version of ChromeOS on them. This provides a secure and familiar environment while they await the delivery of new Chromebooks. Here's why it's the best choice:
* Security: ChromeOS Flex inherits the security features of ChromeOS, such as sandboxing, verified boot, and automatic updates, mitigating the risks associated with the previous operating system.
* Quick Deployment: ChromeOS Flex can be easily installed on existing hardware using a USB drive, minimizing downtime and allowing employees to continue working.
* Familiar Interface: The user interface of ChromeOS Flex is similar to ChromeOS, ensuring a smooth transition for employees.
Option A is incorrect because the ChromeOS Readiness Guide is a resource for planning migration, not an immediate security solution.
Option B is incorrect because while ChromeOS Managed Browser enhances security within a browser, it doesn't address vulnerabilities in the underlying operating system.
Option C is incorrect because ChromeOS Bytes is a blog, not a software solution.
References:
* ChromeOS Flex: https://chromeenterprise.google/os/chromeosflex/
質問 # 41
You're the lead for the technology department and you're working with your teammate on a hardware refresh in the upcoming year A major part of the refresh Is to consider ChromeOS devices for the majority of the users in the company. What are some organization level objectives you should consider during this hardware refresh in regard to ChromeOS?
- A. Verifying If all the terms and conditions in the Chrome Online Agreement are applicable to ChromeOS
- B. ChromeOS will need a rollout and execution plan commensurate with hardware supply availability
- C. ChromeOS integration with current technological standards and practices can be worked on with trusted Google partners
- D. ChromeOS allows for advanced security flexible access, and simplified orchestration within the business
正解：D
解説：
When considering a hardware refresh with ChromeOS devices, organizational-level objectives should focus on the strategic advantages that ChromeOS brings to the business:
* Advanced Security: ChromeOS is known for its robust security features, including sandboxing, verified boot, automatic updates, and data encryption. These can significantly reduce the risk of malware infections and data breaches.
* Flexible Access: ChromeOS devices support cloud-based applications and services, enabling employees to work from anywhere with an internet connection. This flexibility enhances productivity and collaboration.
* Simplified Orchestration: ChromeOS devices are centrally managed through the Google Admin console, simplifying device deployment, configuration, and updates. This reduces IT overhead and streamlines device management processes.
Option A is relevant but not a primary organizational objective. While partner collaboration can be beneficial, the focus should be on how ChromeOS directly improves the organization's operations.
Option B is incorrect because verifying the terms of the Chrome Online Agreement is a legal requirement, not a strategic objective.
Option D is relevant but not as impactful as the other objectives. While a rollout plan is necessary, the focus should be on the long-term benefits of ChromeOS for the organization.
References:
* Chrome Enterprise overview: https://chromeenterprise.google/
質問 # 42
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?
- A. Configure "Restricted Wi-Fi Networks "
- B. Prevent WiMax connectivity
- C. Restrict 'Auto Connecting" to Wi-Fi
- D. Remove Wi-Fi from "Enabled network interfaces "
正解：D
解説：
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.
質問 # 43
What should an administrator do to view the number and type of ChromeOS upgrades purchased and in use by their domain?
- A. Contact partner to verify
- B. Check reports page for upgrades
- C. Verify upgrades on devices page
- D. Check subscriptions in billing
正解：D
解説：
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.
References:
* Sign in to your Admin console: https://support.google.com/chrome/a/answer/182076?hl=en
質問 # 44
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?
- A. In "User & Browser Settings" for Power and shutdown set the policy to "Do not allow wake locks "
- B. In "Managed Guest Session settings" set the maximum user session length to "unlimited "
- C. In "Power management settings" set the policy to "Only allow users to turn off the device using the physical power button "
- D. In "Power management settings" apply 'Do not allow device to sleep/shut down when idle on the sign-in screen "
正解：D
解説：
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.
References:
* https://support.google.com/chrome/a/answer/3523633
質問 # 45
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?
- A. Enable the 'User and Browser Settings" and update 'Maximum user session length* to any time up to 24 hours
- B. You can remotely access each device and sign out of the user account using Chrome Remote Desktop
- C. 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
- D. Create a corporate policy stating (he users are to manually sign out after the end of every shift
正解：A
解説：
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.
References:
* Set up Chrome browser on managed devices:
https://support.google.com/chrome/a/answer/3523633?hl=en
質問 # 46
......
更新されたテストエンジン練習ChromeOS-Administrator問題集と練習試験で使おう：https://jp.fast2test.com/ChromeOS-Administrator-premium-file.html