Cisco Exam 300-820 Topic 12 Question 69 Discussion

Actual exam question for Cisco's 300-820 exam

Question #: 69
Topic #: 12

D18912E1457D5D1DDCBD40AB3BF70D5D

Refer to the exhibit showing logs from the Expressway-C, a copy of the Expressway-E certificate, and the UC traversal zone configuration for the Expressway-C. An office administrator is deploying mobile and remote access and sees an issue with the UC traversal zone. The zone is showing ''TLS negotiation failure''. What is causing this issue?

AThe Expressway-E certificate includes the Expressway-C FQDN as a SAN entry

BThe Expressway-C is missing the FQDN of Cisco UCM in the Common Name of its certificate

CIn the UC Traversal Zone on the Expressway-C, the peer address is set to the IP of the Expressway-E,
which is not a SAN entry in the Expressway-E certificate

DThe Expressway-E does not have the FQDN of Cisco UCM listed as a SAN in its certificate

Show Suggested Answer

Suggested Answer: D

by Rolande at Mar 07, 2024, 02:21 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Roosevelt

5 months ago

We should check the certificates and configurations closely to determine the exact cause.

upvoted 0 times

...

Dulce

5 months ago

I agree, that might be the issue causing the TLS negotiation failure.

upvoted 0 times

...

Candida

5 months ago

Could it be that the Expressway-E does not have the FQDN of Cisco UCM listed as a SAN in its certificate?

upvoted 0 times

...

Charlene

5 months ago

Actually, I think the UC Traversal Zone on the Expressway-C has the peer address set to the IP of the Expressway-E, which is not a SAN entry in the Expressway-E certificate.

upvoted 0 times

...

Skye

6 months ago

No, I believe the problem lies with the Expressway-C missing the FQDN of Cisco UCM in the Common Name of its certificate.

upvoted 0 times

...

Mozell

6 months ago

I think the issue is with the Expressway-E certificate including the Expressway-C FQDN as a SAN entry.

upvoted 0 times

...

Thurman

6 months ago

Yes, the peer address should be the FQDN of the Expressway-E, not just its IP.

upvoted 0 times

...

Jina

6 months ago

I think the issue lies with the UC Traversal Zone configuration on the Expressway-C.

upvoted 0 times

...

Ivette

6 months ago

That could be a possibility. The Common Name in the certificate is important.

upvoted 0 times

...

Oneida

6 months ago

Could it also be that the Expressway-C is missing the FQDN of Cisco UCM in its certificate?

upvoted 0 times

...

Thurman

6 months ago

I agree with Ivette. The Expressway-E certificate might not have the correct SAN entry.

upvoted 0 times

...

Ivette

7 months ago

I think the issue is with the Expressway-E certificate.

upvoted 0 times

...

Martina

8 months ago

That's a good point. If the Expressway-E doesn't have the FQDN of Cisco UCM listed as a SAN in its certificate, that could also be the culprit.

upvoted 0 times

...

Blondell

8 months ago

Option C looks promising to me. The fact that the peer address in the UC Traversal Zone is set to the IP of the Expressway-E, which is not a SAN entry in the Expressway-E certificate, could definitely cause the TLS negotiation failure.

upvoted 0 times

Filiberto

7 months ago

G: So, ensuring the peer address matches the SAN entry in the certificate is key for successful TLS negotiation.

upvoted 0 times

...

Annice

8 months ago

F: That makes sense. Not having the correct peer address in the UC Traversal Zone could definitely cause the TLS negotiation failure.

upvoted 0 times

...

Loise

8 months ago

E: Option C looks promising to me. The fact that the peer address in the UC Traversal Zone is set to the IP of the Expressway-E.

upvoted 0 times

...

Patria

8 months ago

D: The Expressway-E does not have the FQDN of Cisco UCM listed as a SAN in its certificate

upvoted 0 times

...

Almeta

8 months ago

C: In the UC Traversal Zone on the Expressway-C, the peer address is set to the IP of the Expressway-E, which is not a SAN entry in the Expressway-E certificate

upvoted 0 times

...

Jacquline

8 months ago

B: The Expressway-C is missing the FQDN of Cisco UCM in the Common Name of its certificate

upvoted 0 times

...

Alishia

8 months ago

A: The Expressway-E certificate includes the Expressway-C FQDN as a SAN entry

upvoted 0 times

...

Van

8 months ago

I agree, the key here is to figure out what the issue is with the TLS negotiation failure. Let's go through the options carefully.

upvoted 0 times

...

Weldon

8 months ago

Hmm, this question seems to be testing our understanding of certificate configuration and traversal zone setup. It's important to pay attention to the details like the SAN entries and the common name in the certificates.

upvoted 0 times

...