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 9 Question 99 Discussion

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

There are two established Partner Interconnect connections between your on-premises network and Google Cloud. The VPC that hosts the Partner Interconnect connections is named "vpc-a" and contains three VPC subnets across three regions, Compute Engine instances, and a GKE cluster. Your on-premises users would like to resolve records hosted in a Cloud DNS private zone following Google-recommended practices. You need to implement a solution that allows your on-premises users to resolve records that are hosted in Google Cloud. What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: A

Associating the private zone to 'vpc-a' and creating an outbound forwarding policy allows DNS queries to be forwarded from on-premises to Google Cloud DNS. The on-premises DNS servers will forward queries to the entry points created when the forwarding policy was applied to 'vpc-a,' enabling proper name resolution.


Contribute your Thoughts:

Veronika
18 days ago
I think option A is the best choice as it follows Google-recommended practices for resolving records hosted in Cloud DNS private zones.
upvoted 0 times
...
Gilma
25 days ago
Alternatively, we could use custom route advertisements to announce 169.254.169.254 via BGP to the on-premises environment.
upvoted 0 times
...
Raelene
1 months ago
Option D looks a bit sketchy to me. Inbound forwarding policies don't sound like they'd work well for this use case.
upvoted 0 times
...
Theron
1 months ago
Haha, using 169.254.169.254 for DNS? That's like a blast from the past! I'll pass on that one.
upvoted 0 times
Kris
7 days ago
User2
upvoted 0 times
...
Leonor
22 days ago
User1
upvoted 0 times
...
...
Evelynn
1 months ago
I agree. We can then configure the on-premises DNS servers to forward queries for the private zone to the entry point addresses.
upvoted 0 times
...
Laurene
1 months ago
I think we should associate the private zone to 'vpc-a' and create an outbound forwarding policy.
upvoted 0 times
...
Carri
1 months ago
I'm not sure about using a DNS proxy service in GKE. That seems like it might add unnecessary complexity to the setup.
upvoted 0 times
...
Salena
1 months ago
Option A seems like the way to go. Forwarding the queries through an outbound policy is a clean and straightforward solution.
upvoted 0 times
Tequila
8 days ago
User 4: Yeah, configuring the on-premises DNS servers to forward queries to the entry point addresses created with the policy attached to 'vpc-a' makes sense.
upvoted 0 times
...
Gerri
9 days ago
User 3: It definitely seems like the most efficient way to allow on-premises users to resolve records hosted in Google Cloud.
upvoted 0 times
...
Margarita
12 days ago
User 2: I agree, associating the private zone to 'vpc-a' and creating an outbound forwarding policy sounds like the best approach.
upvoted 0 times
...
Antione
16 days ago
User 1: Option A seems like the way to go. Forwarding the queries through an outbound policy is a clean and straightforward solution.
upvoted 0 times
...
...

Save Cancel