Your organization is developing a landing zone architecture with the following requirements: - There should be no communication possible between production and non- production environments…

Question

Options

• ACreate a design that has one Shared VPC host project for the production environment, and
• BCreate a design that has a Shared VPC for each project. Implement hierarchical firewall policies
• CCreate a design that implements a single Shared VPC. Use VPC firewall rules with secure tags to
• DCreate a design where each project in each environment has its own VPC with its own subnets,

• A
  61% (28)
• B
  7% (3)
• C
  9% (4)
• D
  24% (11)

Explanation

Separation Between Production and Non-Production Environments: By creating separate Shared VPC host projects for production and non-production environments, you ensure complete isolation between the two environments, meeting the requirement of no communication between them. Application Communication Within an Environment: Within each Shared VPC, applications can communicate as needed using VPC-level routing and Centralized Network Management: Shared VPC allows network administrators to centrally manage networking resources, such as subnets, routes, and firewall rules, while developers retain control over their compute resources within their service projects. Separate Billing for Applications: Each application is associated with a separate service project, enabling separate billing and resource allocation. Developer Autonomy with Networking Restrictions: Developers in service projects can manage their compute resources but cannot create or modify networking resources, aligning with organizational control and autonomy requirements. Shared VPC can scale to support multiple service projects, making it suitable for the expected 1000 applications per environment.

No community discussion yet for this question.