Your organization is using a Shared VPC model. Service project owners want to independently manage their DNS zones in service projects. All service project workloads must be able to resolve all…

The correct answer is D. Create a Cloud DNS private zone in each service project. Use cross-project binding to associate. Shared VPC and DNS resolution: In a Shared VPC model, the host project manages the network resources (e.g., VPCs), while the service projects contain workloads that use the Shared VPC. For private DNS resolution, DNS zones in service projects must be associated with the Shared…

Submitted by weili_xi· Apr 18, 2026Designing, planning, and prototyping a Google Cloud network

Question

Your organization is using a Shared VPC model. Service project owners want to independently manage their DNS zones in service projects. All service project workloads must be able to resolve all private zones that are defined in other service projects. You need to create a solution that meets these goals. What should you do?

Options

ACreate a Cloud DNS private zone in each service project. Use a Cloud DNS forwarding zone to
BCreate a Cloud DNS private zone in each service project. Use Cloud DNS peering zones that
CCreate a Cloud DNS response policy zone in each service project. Use Cloud DNS peering zones
DCreate a Cloud DNS private zone in each service project. Use cross-project binding to associate

How the community answered

(29 responses)

A
14% (4)
B
3% (1)
C
7% (2)
D
76% (22)

Explanation

Shared VPC and DNS resolution: In a Shared VPC model, the host project manages the network resources (e.g., VPCs), while the service projects contain workloads that use the Shared VPC. For private DNS resolution, DNS zones in service projects must be associated with the Shared VPC. Cross-project binding: - Cloud DNS cross-project binding allows private DNS zones created in service projects to be associated with the Shared VPC in the host project. This enables workloads in service projects to resolve private DNS zones independently while sharing the same network. - Cross-project binding simplifies DNS management by allowing service project owners to manage their own private DNS zones without requiring direct access to the host project. Workloads resolving all private zones: - Using cross-project binding, all workloads in the Shared VPC (across service projects) can resolve private DNS zones defined in other service projects. - This ensures full DNS resolution across the organization while maintaining independent DNS management for service project owners. This solution meets the requirements of enabling service project owners to independently manage DNS zones while ensuring that all workloads can resolve private zones across the Shared VPC. It aligns with Google Cloud's best practices for Shared VPC and DNS management.

Topics

#Cloud DNS#Shared VPC#Private DNS Zone#Cross-project binding

Community Discussion

No community discussion yet for this question.

Full PROFESSIONAL-CLOUD-NETWORK-ENGINEER Practice