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

Actual exam question for Google's Professional Cloud Network Engineer exam

Question #: 110
Topic #: 9

[All Professional Cloud Network Engineer Questions]

Your team deployed two applications in GKE that are exposed through an external Application Load Balancer. When queries are sent to www.mountkirkgames.com/sales and www.mountkirkgames.com/get-an-analysis, the correct pages are displayed. However, you have received complaints that www.mountkirkgames.com yields a 404 error. You need to resolve this error. What should you do?

AReview the Ingress YAML file. Define the default backend. Reapply the YAML.

BReview the Ingress YAML file. Add a new path rule for the * character that directs to the base service. Reapply the YAML.

CReview the Service YAML file. Define a default backend. Reapply the YAML.

DReview the Service YAML file. Add a new path rule for the * character that directs to the base service. Reapply the YAML.

Show Suggested Answer

Suggested Answer: A

The 404 error is occurring because there is no default backend defined for requests to the root URL. Defining the default backend in the Ingress YAML file ensures that requests to www.mountkirkgames.com are routed to the correct service.

by Earleen at Jul 31, 2025, 05:25 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Linsey

2 months ago

Wait, why would we need to add a path rule for *?

upvoted 0 times

...

Carrol

3 months ago

I think option A is the way to go!

upvoted 0 times

...

Graciela

3 months ago

Sounds like a default backend issue.

upvoted 0 times

...

Lavera

3 months ago

I’m surprised this wasn’t caught earlier!

upvoted 0 times

...

Thaddeus

3 months ago

Definitely not C, that won't fix the 404.

upvoted 0 times

...

Johanna

3 months ago

I recall that the Service YAML file usually handles traffic routing, but I think the Ingress is more relevant here. I might lean towards option A or B, but I'm not completely confident.

upvoted 0 times

...

Justa

4 months ago

I practiced a similar question where we had to set up path rules in the Ingress. I wonder if option B is the right choice since it mentions directing to the base service.

upvoted 0 times

...

Desmond

4 months ago

I'm not entirely sure, but I feel like adding a new path rule for the wildcard character could help. It seems like a common solution for handling 404 errors.

upvoted 0 times

...

Jin

4 months ago

I think we might need to check the Ingress YAML file first. I remember something about defining a default backend to handle requests that don't match any specific path.

upvoted 0 times

...

Denae

4 months ago

This seems like a pretty straightforward problem. I think I'll just go with option A and review the Ingress YAML file, define the default backend, and reapply the YAML. That should do the trick.

upvoted 0 times

...

Zoila

4 months ago

I've got a strategy for this. First, I'll review the Ingress YAML and make sure the default backend is properly defined. If that doesn't work, I'll try adding the new path rule for the * character to the Ingress YAML.

upvoted 0 times

...

Reita

5 months ago

I'm a bit confused here. Should I be looking at the Service YAML file instead? I'm not sure if the issue is with the Ingress or the Service configuration.

upvoted 0 times

...

Suzi

5 months ago

Okay, this seems straightforward. I'll review the Ingress YAML and add a new path rule for the * character to direct it to the base service. That should resolve the 404 error.

upvoted 0 times

...

Frederick

5 months ago

Hmm, this looks like a tricky one. I think I'll start by reviewing the Ingress YAML file and see if I can find the issue with the default backend configuration.

upvoted 0 times

...