Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Google Exam Professional-Cloud-Network-Engineer Topic 2 Question 95 Discussion

Actual exam question for Google's Professional Cloud Network Engineer exam
Question #: 95
Topic #: 2
[All Professional Cloud Network Engineer Questions]

You ate planning to use Terraform to deploy the Google Cloud infrastructure for your company, The design must meet the following requirements

* Each Google Cloud project must represent an Internal project that your team Will work on

* After an Internal project is finished, the infrastructure must be deleted

* Each Internal project must have Its own Google Cloud project owner to manage the Google Cloud resources.

* You have 10---100 projects deployed at a time

While you are writing the Terraform code, you need to ensure that the deployment is simple and the code is reusable With

centralized management What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: D

The correct answer is D because it meets the following requirements:

Each internal project has its own Google Cloud project, which can be easily created and deleted by Terraform using the google_project resource1.

Each internal project has its own Google Cloud project owner, which can be assigned by Terraform using the google_project_iam_member resource1.

The deployment is simple and the code is reusable with centralized management, because the Shared VPC allows you to connect multiple service projects to a single host project that contains the network resources2.This way, you can use Terraform modules to create and manage the network resources in the host project, and then reference them in the service projects3.

Option A is incorrect because it does not create separate Google Cloud projects for each internal project, which makes it harder to delete the infrastructure and assign project owners.Option B is incorrect because it does not create separate Google Cloud projects for each internal project, and also because it attaches the service projects to a Shared VPC, which is not recommended for short-lived projects2. Option C is incorrect because it does not use a Shared VPC, which means that each internal project has to create and manage its own network resources, which increases complexity and reduces reusability.


google_project - Terraform Registry

Managing infrastructure as code with Terraform, Cloud Build, and GitOps | Google Cloud

Automating your automation by Creating Google Cloud Projects Automatically

Contribute your Thoughts:

France
2 days ago
Option C sounds like a real headache. A single project and VPC for each internal project? That's just asking for trouble!
upvoted 0 times
...
Vince
8 days ago
Hmm, I'm not sure option A is a good idea. Creating a separate VPC for each project could quickly become unwieldy with 10-100 projects.
upvoted 0 times
...
Erasmo
14 days ago
That's a valid point, but I still think option B is more efficient in terms of management and reusability.
upvoted 0 times
...
Elli
16 days ago
I disagree, I believe option C is better as it provides each internal project with its own project and VPC for better isolation.
upvoted 0 times
...
Elouise
21 days ago
Option B sounds good to me. A single Shared VPC with each project as a service project should make it easy to manage the infrastructure.
upvoted 0 times
...
Alyssa
23 days ago
I think option D is the best choice. Creating a Shared VPC and service project for each internal project seems to meet all the requirements while keeping the deployment simple and the code reusable.
upvoted 0 times
...
Erasmo
23 days ago
I think option B is the best choice because it allows for centralized management and easy deletion of projects.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77