Your team sets up a Shared VPC Network where project co-vpc-prod is the host project. Your team has configured the firewall rules, subnets, and VPN gateway on the host project. They need to enable…

Question

Options

• ACompute Network User Role at the host project level.
• BCompute Network User Role at the subnet level.
• CCompute Shared VPC Admin Role at the host project level.
• DCompute Shared VPC Admin Role at the service project level.

• A
  4% (1)
• B
  82% (23)
• C
  4% (1)
• D
  11% (3)

Explanation

In a Shared VPC setup, the Compute Network User role allows service project users to attach VM instances to subnets in the host project's VPC. Granting this role at the subnet level (10.1.1.0/24 specifically) restricts Engineering Group A to only that subnet - they cannot attach instances to any other subnets. Option A (Compute Network User at the host project level) would grant access to ALL subnets in the host VPC, violating the requirement to restrict to only 10.1.1.0/24. Options C and D involve the Compute Shared VPC Admin role, which is an administrative role for configuring the Shared VPC itself (associating/disassociating service projects) - not for granting subnet attachment rights to engineering teams.

No community discussion yet for this question.