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

Oracle Exam 1Z0-1084-25 Topic 1 Question 1 Discussion

Actual exam question for Oracle's 1Z0-1084-25 exam
Question #: 1
Topic #: 1
[All 1Z0-1084-25 Questions]

What can you use to dynamically make Kubernetes resources discoverable to public DNS servers? (Choose the best answer.)

Show Suggested Answer Hide Answer
Suggested Answer: D

To dynamically make Kubernetes resources discoverable to public DNS servers, you can use ExternalDNS. ExternalDNS is a Kubernetes add-on that automates the management of DNS records for your Kubernetes services and ingresses. It can be configured to monitor the changes in your Kubernetes resources and automatically update DNS records in a supported DNS provider. By integrating ExternalDNS with your Kubernetes cluster, you can ensure that the DNS records for your services and ingresses are automatically created, updated, or deleted based on changes in your Kubernetes resources. This allows your Kubernetes resources to be discoverable by external systems through public DNS servers.


Contribute your Thoughts:

Polly
5 days ago
D) ExternalDNS all the way. Anything else and you might as well just have your services running in a black box.
upvoted 0 times
...
Howard
6 days ago
ExternalDNS, obviously. Unless you want your Kubernetes resources to be as hard to find as a needle in a haystack.
upvoted 0 times
...
Claribel
7 days ago
I'm with Kelvin. D) ExternalDNS is the clear winner here. Unless you want your Kubernetes services to be, you know, undiscoverable.
upvoted 0 times
...
Kelvin
8 days ago
C) CoreDNS? Nah, that's just the internal DNS server. D) ExternalDNS is the way to go for public discovery.
upvoted 0 times
...
Hermila
10 days ago
Gotta be D) ExternalDNS. It's the only option that mentions 'public DNS servers' in the question.
upvoted 0 times
...
Thora
12 days ago
Hmm, I'm torn between B) DynDNS and D) ExternalDNS. Guess I'll go with the one that's Kubernetes-specific.
upvoted 0 times
...
Lasandra
13 days ago
CoreDNS is a flexible and extensible DNS server that can be easily integrated with Kubernetes. It allows for dynamic updates to DNS records, making it a suitable choice for making resources discoverable to public DNS servers.
upvoted 0 times
...
Diego
14 days ago
Why do you think CoreDNS is the best option?
upvoted 0 times
...
Lasandra
16 days ago
I disagree, I believe the correct answer is C) CoreDNS.
upvoted 0 times
...
Diego
18 days ago
I think the answer is A) kubeDNS.
upvoted 0 times
...
Kimbery
18 days ago
D) ExternalDNS sounds like the way to go. It's specifically designed for making Kubernetes resources discoverable to public DNS.
upvoted 0 times
...
Boris
29 days ago
I'm pretty sure it's C) CoreDNS. That's the default DNS server in Kubernetes, right?
upvoted 0 times
Malcolm
1 days ago
D) ExternalDNS is the correct answer for dynamically making Kubernetes resources discoverable to public DNS servers.
upvoted 0 times
...
Doug
14 days ago
C) CoreDNS is indeed the default DNS server in Kubernetes, but D) ExternalDNS is specifically designed to make Kubernetes resources discoverable to public DNS servers.
upvoted 0 times
...
Theola
19 days ago
A) kubeDNS is also a valid option for making Kubernetes resources discoverable to public DNS servers.
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77