nerdexam
Google

PROFESSIONAL-CLOUD-SECURITY-ENGINEER · Question #333

Your Google Cloud organization is subdivided into three folders: production, development, and networking, Networking resources for the organization are centrally managed in the networking folder…

The correct answer is A. Enable the Restrict Shared VPC Host Projects organization policy on the production folder. To prevent projects in the production folder from attaching to unauthorized Shared VPCs without affecting the development folder, enable the "Restrict Shared VPC Host Projects" organization policy on the production folder.

Submitted by hans_de· Apr 18, 2026Configuring network security

Question

Your Google Cloud organization is subdivided into three folders: production, development, and networking, Networking resources for the organization are centrally managed in the networking folder. You discovered that projects in the production folder are attaching to Shared VPCs that are outside of the networking folder which could become a data exfiltration risk. You must resolve the production folder issue without impacting the development folder. You need to use the most efficient and least disruptive approach. What should you do?

Options

  • AEnable the Restrict Shared VPC Host Projects organization policy on the production folder.
  • BEnable the Restrict Shared VPC Host Projects organization policy on the networking folder only.
  • CEnable the Restrict Shared VPC Host Projects organization policy at the project level for each of
  • DEnable the Restrict Shared VPC Host Projects organization policy at the organization level.

How the community answered

(57 responses)
  • A
    65% (37)
  • B
    12% (7)
  • C
    5% (3)
  • D
    18% (10)

Why each option

To prevent projects in the production folder from attaching to unauthorized Shared VPCs without affecting the development folder, enable the "Restrict Shared VPC Host Projects" organization policy on the production folder.

AEnable the Restrict Shared VPC Host Projects organization policy on the production folder.Correct

Enabling the `Restrict Shared VPC Host Projects` organization policy directly on the production folder allows you to precisely control which Shared VPC host projects are permissible for service projects within that folder. This provides a targeted solution that resolves the security risk in production while leaving the development folder unaffected, aligning with the requirements for efficiency and minimal disruption.

BEnable the Restrict Shared VPC Host Projects organization policy on the networking folder only.

Enabling the policy on the networking folder would only restrict Shared VPCs within that folder, not prevent projects in the production folder from attaching to host projects located outside the networking folder.

CEnable the Restrict Shared VPC Host Projects organization policy at the project level for each of

Applying the policy at the project level for each project in the production folder would be less efficient and more cumbersome to manage than applying it once at the folder level, especially for multiple projects.

DEnable the Restrict Shared VPC Host Projects organization policy at the organization level.

Enabling the policy at the organization level would apply the restriction to all folders, including the development folder, which violates the requirement to not impact the development folder.

Concept tested: Organization Policy for Shared VPC restrictions

Source: https://cloud.google.com/vpc/docs/troubleshooting-shared-vpc#restrict-host-projects

Topics

#Organization Policy#Shared VPC#Data Exfiltration Prevention#Network Controls

Community Discussion

No community discussion yet for this question.

Full PROFESSIONAL-CLOUD-SECURITY-ENGINEER Practice