MENU
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?
Suggested Answer: A
Get Premium Professional Cloud Network Engineer Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
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.
23 comments · newest first
LI
Linsey
10 months ago
Wait, why would we need to add a path rule for *?
CA
Carrol
10 months ago
I think option A is the way to go!
GR
Graciela
10 months ago
Sounds like a default backend issue.
LA
Lavera
11 months ago
I’m surprised this wasn’t caught earlier!
TH
Thaddeus
11 months ago
Definitely not C, that won't fix the 404.
JO
Johanna
11 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.
JU
Justa
11 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.
DE
Desmond
11 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.
JI
Jin
12 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.
DE
Denae
12 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.
ZO
Zoila
1 year 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.
RE
Reita
1 year 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.
SU
Suzi
1 year 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.
FR
Frederick
1 year 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.
FR
Francine
1 year ago
I'm leaning towards option C, it makes more sense to me.
CL
Clemencia
1 year ago
I disagree, I believe the correct answer is B.
BA
Barb
1 year ago
Hmm, this one's a bit of a head-scratcher. Good thing I brought my trusty pocket calculator to help me crunch the numbers. Option B it is!
KA
Katina
1 year ago
Option B is the correct answer. Gotta love those tricky 404 errors, am I right? Time to unleash my inner Kubernetes wizard!
FE
Felix
1 year ago
I'm a bit confused. Why not just update the Service YAML file instead of the Ingress YAML? Wouldn't that be easier?
CH
Chantay
1 year ago
I think the answer is A.
CA
Carma
1 year ago
I agree with Minna. Updating the Ingress YAML to handle the wildcard path is the logical solution here.
MI
Minna
1 year ago
Option B seems like the way to go. Defining a default backend in the Ingress YAML file should resolve the 404 error on the root domain.
EN
Ena
1 year ago
User 1: Option B seems like the way to go.