Google Professional Chrome Enterprise Administrator Exam - Topic 3 Question 2 Discussion

Actual exam question for Google's Professional Chrome Enterprise Administrator exam

Question #: 2
Topic #: 3

[All Professional Chrome Enterprise Administrator Questions]

[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?

AAdd `*.acme.com` to runtime blocked hosts; Disable storage permission; Disable history permission

BAdd `*.acme.com` to runtime blocked hosts; Enable storage permission; Enable history permission

CAdd `internal.acme.com` to runtime blocked hosts; Disable storage permission; Disable history permission

DAdd `internal.acme.com` to runtime blocked hosts; Enable storage permission; Enable history permission

Show Suggested Answer

Suggested Answer: A

by Trina at May 04, 2025, 01:26 AM

Limited Time Offer

25%

Off

Get Premium Professional Chrome Enterprise Administrator Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Emerson

5 months ago

Wait, why would we enable storage or history permissions? That sounds risky!

upvoted 0 times

...

Virgie

5 months ago

I think option C is better, we should block `internal.acme.com` specifically.

upvoted 0 times

...

Latosha

6 months ago

Totally agree with option A, no need for those permissions at all.

upvoted 0 times

...

Jacquelyne

6 months ago

Are we sure blocking `*.acme.com` is enough? What if there are other risks?

upvoted 0 times

...

Cruz

6 months ago

Option A seems right, we need to block `*.acme.com` for sure.

upvoted 0 times

...

Madelyn

6 months ago

I’m pretty certain that we need to disable both storage and history permissions, but I’m confused about the host settings.

upvoted 0 times

...

Arthur

7 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.

upvoted 0 times

...

Paul

7 months ago

I remember practicing a question about permissions, and I think disabling both storage and history permissions is definitely the right move here.

upvoted 0 times

...

Gearldine

7 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.

upvoted 0 times

...

Alberto

7 months 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?

upvoted 0 times

...

Jaclyn

7 months 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!

upvoted 0 times

...

India

8 months 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.

upvoted 0 times

...

Laurel

8 months ago

This seems straightforward. I'll focus on disabling the specific permissions mentioned in the requirements.

upvoted 0 times

...

Jeff

11 months 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!

upvoted 0 times

Dalene

10 months ago

Absolutely, we have to protect our company's data. Option C is the best choice.

upvoted 0 times

...

Kristofer

10 months ago

I think it's important to prioritize security over convenience. Option C it is.

upvoted 0 times

...

Lai

10 months ago

Yeah, the security team is just doing their job. We should follow their recommendations.

upvoted 0 times

...

Lenora

10 months ago

I agree, better safe than sorry. Option C seems like the way to go.

upvoted 0 times

...

Linn

11 months ago

That's true, but option D includes enabling permissions that the security team wants disabled.

upvoted 0 times

...

Deja

1 year ago

But wouldn't option D also work since it enables storage and history permissions?

upvoted 0 times

...

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.

upvoted 0 times

Tayna

11 months ago

Let's make sure to implement these changes as soon as possible.

upvoted 0 times

...

Brianne

11 months ago

I think the security team will appreciate the precautions taken with option C.

upvoted 0 times

...

Alpha

12 months ago

It's important to prioritize security when it comes to extensions.

upvoted 0 times

...

Devorah

12 months ago

I agree, option C is the safest choice for the company.

upvoted 0 times

...

Dulce

1 year ago

I agree with Linn, option C seems to meet the security team's requirements.

upvoted 0 times

...

Linn

1 year ago

I think the company should go with option C.

upvoted 0 times

...

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.

upvoted 0 times

Antonio

12 months ago

I think option C is the best choice too. It's important to protect sensitive information.

upvoted 0 times

...

Agustin

1 year ago

Yeah, security should always be a top priority. Option C seems like the most secure choice.

upvoted 0 times

...

Tiara

1 year ago

I agree, better safe than sorry. Blocking the internal page and disabling permissions is the way to go.

upvoted 0 times

...

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!

upvoted 0 times