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

Cisco 300-820 Exam - Topic 25 Question 88 Discussion

D18912E1457D5D1DDCBD40AB3BF70D5DRefer 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?
D) The Expressway-E does not have the FQDN of Cisco UCM listed as a SAN in its certificate
A) The Expressway-E certificate includes the Expressway-C FQDN as a SAN entry
B) The Expressway-C is missing the FQDN of Cisco UCM in the Common Name of its certificate
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

Cisco 300-820 Exam - Topic 25 Question 88 Discussion

Actual exam question for Cisco's 300-820 exam
Question #: 88
Topic #: 25
[All 300-820 Questions]

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?

Show Suggested Answer Hide Answer
Suggested Answer: D

by Luke at Oct 22, 2024, 07:02 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Britt
9 months ago
I thought the SAN entries were optional, this is surprising!
upvoted 0 times
...
Winifred
9 months ago
Option C seems right, the peer address mismatch is a classic problem.
upvoted 0 times
...
Roy
10 months ago
Wait, are we sure it's not the Expressway-C's certificate that's the issue?
upvoted 0 times
...
Lashonda
10 months ago
Totally agree, that's a common oversight!
upvoted 0 times
...
Vernice
10 months ago
The Expressway-E certificate needs the FQDN of Cisco UCM as a SAN.
upvoted 0 times
...
Bobbye
10 months ago
I recall that if the FQDN isn’t listed correctly in the SAN, it can cause TLS issues, so maybe option D is the right choice?
upvoted 0 times
...
Eveline
11 months ago
I’m leaning towards option C because it mentions the peer address and SAN entries, but I could be mixing it up with another topic.
upvoted 0 times
...
Ashley
11 months ago
This question feels familiar; I think we had a practice question about TLS negotiation failures related to SAN entries.
upvoted 0 times
...
Asha
11 months ago
I remember studying about SAN entries in certificates, but I'm not entirely sure if the issue is with the Expressway-E or C.
upvoted 0 times
...
Ryann
11 months ago
This seems like a straightforward Expressway certificate issue. I'm pretty confident I can identify the problem based on the information given in the question. Time to put my Cisco collaboration knowledge to the test!
upvoted 0 times
...
Rosalyn
11 months ago
I'm a bit confused by all the technical details in this question. But I'll do my best to carefully read through the information provided and try to identify the most likely cause of the TLS negotiation failure.
upvoted 0 times
...
Quentin
11 months ago
Okay, let's see here. The options mention the Expressway-C FQDN, the Cisco UCM FQDN, and the peer address in the UC traversal zone. I think I have a good idea of where to start troubleshooting.
upvoted 0 times
...
Kristin
11 months ago
Hmm, the question mentions a "TLS negotiation failure" in the UC traversal zone, so I'm guessing the certificate configuration is the problem. I'll need to analyze the Expressway-E certificate closely.
upvoted 0 times
...
Marisha
11 months ago
This looks like a tricky Expressway configuration issue. I'll need to carefully review the logs and certificate details to identify the root cause.
upvoted 0 times
...
Hubert
2 years ago
This question is like a game of Sudoku - you've got to put all the pieces together to get the right answer. I'm going to try to work through it step by step.
upvoted 0 times
Stephane
2 years ago
D) The Expressway-E does not have the FQDN of Cisco UCM listed as a SAN in its certificate
upvoted 0 times
...
Tennie
2 years 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
...
Dannette
2 years ago
B) The Expressway-C is missing the FQDN of Cisco UCM in the Common Name of its certificate
upvoted 0 times
...
Brunilda
2 years ago
A) The Expressway-E certificate includes the Expressway-C FQDN as a SAN entry
upvoted 0 times
...
...
Craig
2 years ago
I'm leaning towards option B. The Expressway-C is missing the FQDN of the Cisco UCM in its certificate, and that's probably causing the problem. But I'm not totally sure.
upvoted 0 times
Veronika
2 years 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
...
Deangelo
2 years ago
B) The Expressway-C is missing the FQDN of Cisco UCM in the Common Name of its certificate
upvoted 0 times
...
Daisy
2 years ago
A) The Expressway-E certificate includes the Expressway-C FQDN as a SAN entry
upvoted 0 times
...
...
Candida
2 years ago
I agree, the Expressway-E certificate might be missing the FQDN of Cisco UCM.
upvoted 0 times
...
Micheline
2 years ago
This question is a real head-scratcher. I'm going to have to think about it for a while. Hopefully, I can figure it out before the exam!
upvoted 0 times
...
Ligia
2 years ago
I think the issue is with the Expressway-E certificate.
upvoted 0 times
...
Cristina
2 years ago
D seems like the most likely answer to me. The Expressway-E certificate is missing the FQDN of the Cisco UCM, and that's causing the TLS negotiation failure.
upvoted 0 times
Carmelina
2 years ago
D) The Expressway-E does not have the FQDN of Cisco UCM listed as a SAN in its certificate
upvoted 0 times
...
Bea
2 years 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
...
Kenny
2 years ago
B) The Expressway-C is missing the FQDN of Cisco UCM in the Common Name of its certificate
upvoted 0 times
...
Ashlee
2 years ago
We should update the certificate to include the necessary information.
upvoted 0 times
...
Eladia
2 years ago
I agree. The TLS negotiation failure is likely due to that mismatch.
upvoted 0 times
...
Rosita
2 years ago
That makes sense. It's important for the certificates to match.
upvoted 0 times
...
Yuette
2 years ago
A) The Expressway-E certificate includes the Expressway-C FQDN as a SAN entry
upvoted 0 times
...
Frederica
2 years ago
D is correct. The Expressway-E certificate needs the FQDN of Cisco UCM.
upvoted 0 times
...
...
Vanna
2 years ago
I think the answer is C. The peer address in the UC Traversal Zone on the Expressway-C is set to the IP of the Expressway-E, but that's not a SAN entry in the Expressway-E certificate. That's got to be the issue.
upvoted 0 times
Rocco
2 years 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
...
Ngoc
2 years ago
B) The Expressway-C is missing the FQDN of Cisco UCM in the Common Name of its certificate
upvoted 0 times
...
Sherly
2 years ago
A) The Expressway-E certificate includes the Expressway-C FQDN as a SAN entry
upvoted 0 times
...
...

Save Cancel