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

Linux Foundation CKA Exam - Topic 1 Question 72 Discussion

Score: 7%TaskCreate a new nginx Ingress resource as follows:* Name: ping* Namespace: ing-internal* Exposing service hi on path /hi using service port 5678
A) Explanation: Solution: vi ingress.yaml # apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: ping namespace: ing-internal spec: rules: - http: paths: - path: /hi pathType: Prefix backend: service: name: hi port: number: 5678 # kubectl create -f ingress.yaml

Linux Foundation CKA Exam - 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

by Caprice at Sep 18, 2024, 02:30 PM

Limited Time Offer

25%

Off

Get Premium CKA Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Matt
10 months ago
I thought Ingress was more complicated than this. Surprised it’s so straightforward!
upvoted 0 times
...
Veronika
10 months ago
Yup, using pathType: Prefix is the way to go for flexibility!
upvoted 0 times
...
Florinda
10 months ago
Wait, does the path need to be exactly /hi? What if I want to add more paths later?
upvoted 0 times
...
Cristy
10 months ago
Looks good! That’s the right way to expose the service.
upvoted 0 times
...
Ryann
11 months ago
Just created an Ingress resource named 'ping' in the 'ing-internal' namespace.
upvoted 0 times
...
Wava
11 months ago
I practiced creating Ingress resources, but I’m a bit uncertain about the exact syntax for the backend section.
upvoted 0 times
...
Lelia
11 months ago
I feel confident about the service name and port, but I might mix up the namespace if I'm not careful.
upvoted 0 times
...
Hoa
11 months ago
This looks similar to the practice questions we did on Ingress resources, but I can't recall if the pathType is always required.
upvoted 0 times
...
Alberta
11 months ago
I think I remember that we need to specify the apiVersion and kind correctly, but I'm not entirely sure about the indentation in YAML.
upvoted 0 times
...
Nobuko
11 months ago
This is a good opportunity to practice creating Ingress resources. I'll give it a try and see if I can get it right.
upvoted 0 times
...
Yvonne
11 months ago
Wait, do I need to create the `hi` service first before defining it in the Ingress? I better review the steps.
upvoted 0 times
...
Marleen
11 months ago
Okay, I think I've got this. I'll create the Ingress resource in the `ing-internal` namespace and expose the `hi` service on the `/hi` path.
upvoted 0 times
...
Candra
11 months ago
Hmm, not sure about the `pathType` field, I'll need to double-check the documentation on that.
upvoted 0 times
...
Willodean
12 months ago
This looks straightforward, I'll start by creating the YAML file for the Ingress resource.
upvoted 0 times
...
Margot
12 months ago
I'm pretty sure it's vSphere HA, since Fault Tolerance is all about high availability.
upvoted 0 times
...
Melinda
2 years 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
2 years 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 years ago
Definitely! It's always good to have monitoring in place for critical services like 'hi'.
upvoted 0 times
...
Lyndia
2 years ago
I like the creativity in naming it 'ping'. It's clear and to the point.
upvoted 0 times
...
Latosha
2 years ago
Yes, it's a good way to ensure the 'hi' service is up and running smoothly.
upvoted 0 times
...
Izetta
2 years ago
That's a clever idea! Having a 'ping' Ingress resource for a health check endpoint.
upvoted 0 times
...
...
Elsa
2 years 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 years ago
Definitely, creating a new nginx Ingress resource is not too complicated.
upvoted 0 times
...
Una
2 years ago
I agree, the solution is clear and easy to follow.
upvoted 0 times
...
Janessa
2 years ago
Thanks! Yeah, it's pretty straightforward.
upvoted 0 times
...
...
Alyssa
2 years 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
2 years 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 years ago
Good point! It's a key detail to pay attention to when setting up an Ingress resource.
upvoted 0 times
...
Bettyann
2 years ago
Exactly, it's important for ensuring the Ingress resource functions properly with the specified path.
upvoted 0 times
...
Magnolia
2 years ago
I agree, it helps to make sure the traffic is correctly routed to the specified service.
upvoted 0 times
...
Diane
2 years ago
Thanks! Yes, using 'pathType: Prefix' is a great way to define the path for the Ingress resource.
upvoted 0 times
...
...
Malcom
2 years ago
I agree, it requires attention to detail to set it up correctly.
upvoted 0 times
...
Tarra
2 years 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
2 years 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
2 years ago
Once the YAML file is ready, we can create the Ingress resource using kubectl create -f ingress.yaml.
upvoted 0 times
...
Breana
2 years ago
Make sure to check the YAML formatting and indentation before creating the Ingress resource.
upvoted 0 times
...
Cherri
2 years ago
Yes, we need to expose the service hi on path /hi using service port 5678.
upvoted 0 times
...
Michel
2 years ago
Looks simple enough, just need to create a new nginx Ingress resource named ping in the ing-internal namespace.
upvoted 0 times
...
...
Alyssa
2 years ago
I found the question on creating a new nginx Ingress resource challenging.
upvoted 0 times
...

Save Cancel