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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Google Professional Cloud Network Engineer Exam - Topic 9 Question 99 Discussion

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?
A) Associate the private zone to 'vpc-a.' Create an outbound forwarding policy and associate the policy to 'vpc-a.' Configure the on-premises DNS servers to forward queries for the private zone to the entry point addresses created when the policy was attached to 'vpc-a.'
B) Configure a DNS proxy service inside one of the GKE clusters. Expose the DNS proxy service in GKE as an internal load balancer. Configure the on-premises DNS servers to forward queries for the private zone to the IP address of the internal load balancer.
C) Use custom route advertisements to announce 169.254.169.254 via BGP to the on-premises environment. Configure the on-premises DNS servers to forward DNS requests to 169.254.169.254.
D) Associate the private zone to 'vpc-a.' Create an inbound forwarding policy and associate the policy to 'vpc-a.' Configure the on-premises DNS servers to forward queries for the private zone to the entry point addresses created when the policy was attached to 'vpc-a.'

Google Professional Cloud Network Engineer Exam - 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.


by Rosalind at Dec 10, 2024, 04:58 AM

Limited Time Offer

25%

Off

Get Premium Professional Cloud Network Engineer Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Paulina
9 months ago
A is definitely the Google-recommended way to go!
upvoted 0 times
...
Eleonora
9 months ago
Wait, 169.254.169.254? That seems sketchy, is that really a good idea?
upvoted 0 times
...
Cyril
10 months ago
I disagree, C is not a standard practice for DNS resolution.
upvoted 0 times
...
Kenda
10 months ago
I think B could work too, but it feels a bit more complex.
upvoted 0 times
...
Felix
10 months ago
Option A seems like the best fit for this setup.
upvoted 0 times
...
Alexia
10 months ago
I vaguely recall something about inbound forwarding policies, but I’m not confident if that’s the right approach for this scenario.
upvoted 0 times
...
Rosita
11 months ago
I feel like using a DNS proxy in GKE could work, but I’m not clear on how to set up the internal load balancer properly.
upvoted 0 times
...
Velda
11 months ago
I think option A sounds familiar from our practice questions, but I’m a bit confused about the entry point addresses.
upvoted 0 times
...
Elise
11 months ago
I remember we discussed the importance of associating the private zone with the correct VPC, but I'm not sure if it's outbound or inbound forwarding we need.
upvoted 0 times
...
Dorthy
11 months ago
Option B with the DNS proxy service in the GKE cluster could also work, but it seems a bit more complex than the approach in Option A. I'd want to make sure I fully understand how to set up and configure the internal load balancer for the DNS proxy service.
upvoted 0 times
...
Melita
11 months ago
I'm pretty confident that Option A is the correct answer here. Associating the private zone to the VPC, creating the outbound forwarding policy, and configuring the on-premises DNS servers to forward queries seems like the cleanest and most straightforward way to implement the solution based on the information provided.
upvoted 0 times
...
Diane
11 months ago
Hmm, I'm a bit confused about the difference between an outbound forwarding policy and an inbound forwarding policy. Option D mentions an inbound policy, but the question specifically says to use Google-recommended practices, which I think points to Option A.
upvoted 0 times
...
Arlette
11 months ago
I think the key here is to use the Google-recommended practices to allow on-premises users to resolve records in the Cloud DNS private zone. Option A looks like the right approach - associate the private zone to the VPC, create an outbound forwarding policy, and configure the on-premises DNS servers to forward queries to the entry point addresses.
upvoted 0 times
...
Veronika
2 years 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
2 years 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
2 years 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
2 years 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
2 years ago
User2
upvoted 0 times
...
Leonor
2 years ago
User1
upvoted 0 times
...
...
Evelynn
2 years 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
2 years ago
I think we should associate the private zone to 'vpc-a' and create an outbound forwarding policy.
upvoted 0 times
...
Carri
2 years 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
2 years 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
2 years 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
2 years 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
2 years 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
2 years 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