You are implementing a Shared VPC network for your organization, which has distributed teams. One of the application developers works across several teams and notices that they can deploy…

Question

Options

• ASpecify which Shared VPC subnets each application's service projects can access by using the
• BGrant the compute.NetworkViewer role to the developer in the Shared VPC host project.
• CRestrict another application's project from accessing specific subnets in the host project by using
• DGrant the compute.NetworkUser role to the developer in the specific Shared VPC service project.

• A
  71% (24)
• B
  18% (6)
• C
  3% (1)
• D
  9% (3)

Explanation

Use the constraints/compute.restrictSharedVpcSubnetworks organizational constraint: This constraint allows you to define which Shared VPC subnets are accessible to specific service projects. By applying this constraint, you can limit a service project's access to only the subnets designated for its applications. Apply the constraint to each service project: This ensures that developers working in a specific service project can deploy resources only in the allowed subnets and not in subnets reserved for other service projects.

No community discussion yet for this question.