ASSOCIATE-GOOGLE-WORKSPACE-ADMINISTRATOR · Question #85
You are configuring Chrome browser security policies for your organization. These policies must restrict certain Chrome apps and extensions. You need to ensure that these policies are applied on the…
The correct answer is A. Configure the allowed list of apps in the Devices page in the apps and extensions settings. Chrome policies configured at the device level (under the Devices section in Apps and Extensions settings) apply to the physical device regardless of which Google account signs in. This is the key distinction: device-level policies enforce restrictions on the machine itself…
Question
You are configuring Chrome browser security policies for your organization. These policies must restrict certain Chrome apps and extensions. You need to ensure that these policies are applied on the devices regardless of which user logs into the device. What should you do?
Options
- AConfigure the allowed list of apps in the Devices page in the apps and extensions settings.
- BConfigure the Chrome user setting to require users to sign in to use Chrome apps and extensions.
- CConfigure the Policy Precedence to override the domain-wide policy applied for apps and
- DRequire 2SV for user logins.
How the community answered
(42 responses)- A71% (30)
- B5% (2)
- C7% (3)
- D17% (7)
Explanation
Chrome policies configured at the device level (under the Devices section in Apps and Extensions settings) apply to the physical device regardless of which Google account signs in. This is the key distinction: device-level policies enforce restrictions on the machine itself, while user-level policies follow the user's account. Since the requirement is device-agnostic enforcement, configuring policies in the Devices page is correct. User-level settings (B, C) would only apply to specific signed-in users. Requiring 2SV (D) is an authentication control, not a Chrome app restriction.
Topics
Community Discussion
No community discussion yet for this question.