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.)

AkubeDNS

BDynDNS

CCoreDNS

DExternalDNS

Show Suggested 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.

by Gearldine at Mar 20, 2025, 06:42 AM

Limited Time Offer

25%

Off

Get Premium 1Z0-1084-25 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Polly

2 months 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

Catarina

17 days ago

A) kubeDNS is fine, but ExternalDNS offers more flexibility and control.

upvoted 0 times

...

Clarinda

1 months ago

D) ExternalDNS is definitely the way to go for making Kubernetes resources discoverable.

upvoted 0 times

...

Coleen

1 months ago

C) CoreDNS can also be used, but ExternalDNS is the most recommended.

upvoted 0 times

...

Wayne

2 months ago

A) kubeDNS is also a good option, but ExternalDNS is more versatile.

upvoted 0 times

...

Howard

2 months 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

2 months 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

2 months 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

2 months ago

Gotta be D) ExternalDNS. It's the only option that mentions 'public DNS servers' in the question.

upvoted 0 times

Gertude

24 days ago

ExternalDNS is definitely the way to go for that specific requirement.

upvoted 0 times

...

Jaime

1 months ago

I agree, D) ExternalDNS is the best choice for making Kubernetes resources discoverable to public DNS servers.

upvoted 0 times

...

Thora

2 months 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

2 months 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

2 months ago

Why do you think CoreDNS is the best option?

upvoted 0 times

...

Lasandra

2 months ago

I disagree, I believe the correct answer is C) CoreDNS.

upvoted 0 times

...

Diego

2 months ago

I think the answer is A) kubeDNS.

upvoted 0 times

...

Kimbery

2 months ago

D) ExternalDNS sounds like the way to go. It's specifically designed for making Kubernetes resources discoverable to public DNS.

upvoted 0 times

Deonna

17 days ago

D) ExternalDNS is the best option for dynamically making Kubernetes resources discoverable to public DNS servers.

upvoted 0 times

...

Glenna

18 days ago

C) CoreDNS is another good choice, but ExternalDNS is more specialized for Kubernetes resources.

upvoted 0 times

...

Geraldine

1 months ago

A) kubeDNS is also an option, but ExternalDNS is more commonly used for this purpose.

upvoted 0 times

...

Antonio

1 months ago

A) kubeDNS and CoreDNS are good options, but ExternalDNS is specifically designed for this purpose.

upvoted 0 times

...

Maddie

1 months ago

D) ExternalDNS is the best option for dynamically making Kubernetes resources discoverable to public DNS servers.

upvoted 0 times

...

Rikki

1 months ago

C) CoreDNS is a good choice, but ExternalDNS is more commonly used for making Kubernetes resources discoverable to public DNS.

upvoted 0 times

...

Wilda

2 months ago

A) kubeDNS is another option, but ExternalDNS is specifically designed for this purpose.

upvoted 0 times

...

Boris

3 months ago

I'm pretty sure it's C) CoreDNS. That's the default DNS server in Kubernetes, right?

upvoted 0 times

Malcolm

2 months ago

D) ExternalDNS is the correct answer for dynamically making Kubernetes resources discoverable to public DNS servers.

upvoted 0 times

...

Doug

2 months 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

2 months ago

A) kubeDNS is also a valid option for making Kubernetes resources discoverable to public DNS servers.

upvoted 0 times

...