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-Database-Engineer Topic 1 Question 43 Discussion

Actual exam question for Google's Professional Cloud Database Engineer exam
Question #: 43
Topic #: 1
[All Professional Cloud Database Engineer Questions]

You are migrating an on-premises application to Compute Engine and Cloud SQL. The application VMs will live in their own project, separate from the Cloud SQL instances which have their own project. What should you do to configure the networks?

Show Suggested Answer Hide Answer

Contribute your Thoughts:

Kimbery
14 days ago
I see both points, but I think option D might be simpler and easier to manage in the long run.
upvoted 0 times
...
Rosendo
23 days ago
I disagree, I believe option B is more efficient as it allows for a Shared VPC for both the application VMs and Cloud SQL instances.
upvoted 0 times
...
Steffanie
26 days ago
Hmm, I'd say B as well. Shared VPC just makes the most sense here. Unless you're a fan of galactic-scale network peering, that is.
upvoted 0 times
...
Cora
26 days ago
I think option A is the best choice because it allows for separate VPC networks while still connecting them.
upvoted 0 times
...
Christoper
26 days ago
Option B, the clear choice it is. Shared VPC, the simplest and most elegant solution, it is.
upvoted 0 times
...
Curtis
27 days ago
For sure, option B is the way to go. Shared VPC is the simplest and most secure way to connect the two projects.
upvoted 0 times
Rebeca
7 days ago
B) Create a Shared VPC that both the application VMs and Cloud SQL instances will use.
upvoted 0 times
...
Jill
8 days ago
A) Create a new VPC network in each project, and use VPC Network Peering to connect the two together.
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