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

Linux Foundation Exam CKA Topic 1 Question 72 Discussion

Actual exam question for Linux Foundation's CKA exam
Question #: 72
Topic #: 1
[All CKA Questions]

Score: 7%

Task

Create a new nginx Ingress resource as follows:

* Name: ping

* Namespace: ing-internal

* Exposing service hi on path /hi using service port 5678

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

Melinda
3 months ago
I bet the person who came up with this question was feeling a little 'nginx' that day. Get it? *laughs awkwardly*
upvoted 0 times
...
German
3 months ago
I wonder if the 'ping' Ingress resource is for a health check endpoint. You know, just to make sure the 'hi' service is up and running. *winks*
upvoted 0 times
Teddy
2 months ago
Definitely! It's always good to have monitoring in place for critical services like 'hi'.
upvoted 0 times
...
Lyndia
2 months ago
I like the creativity in naming it 'ping'. It's clear and to the point.
upvoted 0 times
...
Latosha
2 months ago
Yes, it's a good way to ensure the 'hi' service is up and running smoothly.
upvoted 0 times
...
Izetta
2 months ago
That's a clever idea! Having a 'ping' Ingress resource for a health check endpoint.
upvoted 0 times
...
...
Elsa
3 months ago
This is a piece of cake! I could probably do this in my sleep. *yawns* But seriously, great job on the solution. It's concise and to the point.
upvoted 0 times
Isabelle
2 months ago
Definitely, creating a new nginx Ingress resource is not too complicated.
upvoted 0 times
...
Una
2 months ago
I agree, the solution is clear and easy to follow.
upvoted 0 times
...
Janessa
3 months ago
Thanks! Yeah, it's pretty straightforward.
upvoted 0 times
...
...
Alyssa
4 months ago
I think the provided solution with creating the Ingress resource in the YAML file is clear and easy to follow.
upvoted 0 times
...
Santos
4 months ago
Nice! I like how the solution uses the 'pathType: Prefix' option to handle the '/hi' path. That's a good way to ensure the Ingress resource works as expected.
upvoted 0 times
Juan
2 months ago
Good point! It's a key detail to pay attention to when setting up an Ingress resource.
upvoted 0 times
...
Bettyann
2 months ago
Exactly, it's important for ensuring the Ingress resource functions properly with the specified path.
upvoted 0 times
...
Magnolia
2 months ago
I agree, it helps to make sure the traffic is correctly routed to the specified service.
upvoted 0 times
...
Diane
3 months ago
Thanks! Yes, using 'pathType: Prefix' is a great way to define the path for the Ingress resource.
upvoted 0 times
...
...
Malcom
4 months ago
I agree, it requires attention to detail to set it up correctly.
upvoted 0 times
...
Tarra
4 months ago
The solution is correct, but I'd recommend adding some comments to the YAML file to explain what each section does. That way, it'll be easier to understand if you come back to it later.
upvoted 0 times
...
Carline
4 months ago
This is a pretty straightforward question. The solution provided looks good, though I'd suggest double-checking the indentation and formatting to ensure the YAML is valid.
upvoted 0 times
Milly
3 months ago
Once the YAML file is ready, we can create the Ingress resource using kubectl create -f ingress.yaml.
upvoted 0 times
...
Breana
3 months ago
Make sure to check the YAML formatting and indentation before creating the Ingress resource.
upvoted 0 times
...
Cherri
3 months ago
Yes, we need to expose the service hi on path /hi using service port 5678.
upvoted 0 times
...
Michel
3 months ago
Looks simple enough, just need to create a new nginx Ingress resource named ping in the ing-internal namespace.
upvoted 0 times
...
...
Alyssa
4 months ago
I found the question on creating a new nginx Ingress resource challenging.
upvoted 0 times
...

Save Cancel