MENU
[Chrome Extensions]
A company is reviewing the permissions of extensions that are popular among employees The security team wants to make sure all extensions in the environment have these capabilities disabled:
* Modify to internal home page: `internal.acme.com`
* Access to the storage
* Access to history
Which actions should be taken in the company default extension Permissions and URLs fields to meet the security team's requirements?
Suggested Answer: A
Get Premium Professional Chrome Enterprise Administrator Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
35 comments · newest first
EM
Emerson
10 months ago
Wait, why would we enable storage or history permissions? That sounds risky!
VI
Virgie
10 months ago
I think option C is better, we should block `internal.acme.com` specifically.
LA
Latosha
11 months ago
Totally agree with option A, no need for those permissions at all.
JA
Jacquelyne
11 months ago
Are we sure blocking `*.acme.com` is enough? What if there are other risks?
CR
Cruz
11 months ago
Option A seems right, we need to block `*.acme.com` for sure.
MA
Madelyn
11 months ago
I’m pretty certain that we need to disable both storage and history permissions, but I’m confused about the host settings.
AR
Arthur
11 months ago
I feel like we should add `internal.acme.com` to the blocked hosts, but I can't recall if we should enable or disable the storage permission.
PA
Paul
12 months ago
I remember practicing a question about permissions, and I think disabling both storage and history permissions is definitely the right move here.
GE
Gearldine
12 months ago
I think we need to block access to `internal.acme.com`, but I'm not sure if it should be `*.acme.com` instead.
AL
Alberto
1 year ago
Wait, I'm a bit confused. Should we be blocking `*.acme.com` or just `internal.acme.com`? And do we need to disable or enable the storage and history permissions?
JA
Jaclyn
1 year ago
Okay, I've got this. I just need to add `internal.acme.com` to the runtime blocked hosts and disable the storage and history permissions. Simple!
IN
India
1 year ago
Hmm, I need to think through this carefully. Blocking the internal homepage and disabling storage and history access are key, but I'm not sure about the exact syntax for the runtime blocked hosts.
LA
Laurel
1 year ago
This seems straightforward. I'll focus on disabling the specific permissions mentioned in the requirements.
JE
Jeff
1 year ago
Haha, these security teams always want to ruin our fun, don't they? But hey, I'd rather have a few extra hoops to jump through than have my company's data compromised. Option C it is!
DA
Dalene
1 year ago
Absolutely, we have to protect our company's data. Option C is the best choice.
KR
Kristofer
1 year ago
I think it's important to prioritize security over convenience. Option C it is.
LA
Lai
1 year ago
Yeah, the security team is just doing their job. We should follow their recommendations.
LE
Lenora
1 year ago
I agree, better safe than sorry. Option C seems like the way to go.
LI
Linn
1 year ago
That's true, but option D includes enabling permissions that the security team wants disabled.
DE
Deja
1 year ago
But wouldn't option D also work since it enables storage and history permissions?
DA
Dallas
1 year ago
Really, the choice is clear. C is the only answer that meets all the security team's requirements. Anything else would just be asking for trouble down the line.
TA
Tayna
1 year ago
Let's make sure to implement these changes as soon as possible.
BR
Brianne
1 year ago
I think the security team will appreciate the precautions taken with option C.
AL
Alpha
1 year ago
It's important to prioritize security when it comes to extensions.
DE
Devorah
1 year ago
I agree, option C is the safest choice for the company.
DU
Dulce
1 year ago
I agree with Linn, option C seems to meet the security team's requirements.
LI
Linn
1 year ago
I think the company should go with option C.
CL
Clemencia
1 year ago
Ah, the classic security vs. convenience dilemma. I'd go with option C - block the internal page and disable those permissions. Better to play it safe, even if it means a few grumpy employees.
AN
Antonio
1 year ago
I think option C is the best choice too. It's important to protect sensitive information.
AG
Agustin
1 year ago
Yeah, security should always be a top priority. Option C seems like the most secure choice.
TI
Tiara
1 year ago
I agree, better safe than sorry. Blocking the internal page and disabling permissions is the way to go.
IS
Isreal
1 year ago
Hmm, this one's tricky. I think blocking the internal home page and disabling storage and history permissions is the way to go. Gotta keep those extensions on a tight leash!
GA
Galen
1 year ago
Exactly! Blocking the internal home page and disabling storage and history permissions is crucial for security.
BA
Bambi
1 year ago
C) Add `internal.acme.com` to runtime blocked hosts; Disable storage permission; Disable history permission
TA
Tamekia
1 year ago
A) Add `*.acme.com` to runtime blocked hosts; Disable storage permission; Disable history permission