MENU
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?
Suggested Answer: D
Get Premium 300-820 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
39 comments · newest first
BR
Britt
11 months ago
I thought the SAN entries were optional, this is surprising!
WI
Winifred
11 months ago
Option C seems right, the peer address mismatch is a classic problem.
RO
Roy
11 months ago
Wait, are we sure it's not the Expressway-C's certificate that's the issue?
LA
Lashonda
11 months ago
Totally agree, that's a common oversight!
VE
Vernice
12 months ago
The Expressway-E certificate needs the FQDN of Cisco UCM as a SAN.
BO
Bobbye
12 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?
EV
Eveline
1 year 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.
AS
Ashley
1 year ago
This question feels familiar; I think we had a practice question about TLS negotiation failures related to SAN entries.
AS
Asha
1 year 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.
RY
Ryann
1 year 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!
RO
Rosalyn
1 year 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.
QU
Quentin
1 year 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.
KR
Kristin
1 year 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.
MA
Marisha
1 year 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.
HU
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.
ST
Stephane
2 years ago
D) The Expressway-E does not have the FQDN of Cisco UCM listed as a SAN in its certificate
TE
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
DA
Dannette
2 years ago
B) The Expressway-C is missing the FQDN of Cisco UCM in the Common Name of its certificate
BR
Brunilda
2 years ago
A) The Expressway-E certificate includes the Expressway-C FQDN as a SAN entry
CR
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.
VE
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
DE
Deangelo
2 years ago
B) The Expressway-C is missing the FQDN of Cisco UCM in the Common Name of its certificate
DA
Daisy
2 years ago
A) The Expressway-E certificate includes the Expressway-C FQDN as a SAN entry
CA
Candida
2 years ago
I agree, the Expressway-E certificate might be missing the FQDN of Cisco UCM.
MI
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!
LI
Ligia
2 years ago
I think the issue is with the Expressway-E certificate.
CR
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.
CA
Carmelina
2 years ago
D) The Expressway-E does not have the FQDN of Cisco UCM listed as a SAN in its certificate
BE
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
KE
Kenny
2 years ago
B) The Expressway-C is missing the FQDN of Cisco UCM in the Common Name of its certificate
AS
Ashlee
2 years ago
We should update the certificate to include the necessary information.
EL
Eladia
2 years ago
I agree. The TLS negotiation failure is likely due to that mismatch.
RO
Rosita
2 years ago
That makes sense. It's important for the certificates to match.
YU
Yuette
2 years ago
A) The Expressway-E certificate includes the Expressway-C FQDN as a SAN entry
FR
Frederica
2 years ago
D is correct. The Expressway-E certificate needs the FQDN of Cisco UCM.
VA
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.
RO
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
NG
Ngoc
2 years ago
B) The Expressway-C is missing the FQDN of Cisco UCM in the Common Name of its certificate
SH
Sherly
2 years ago
A) The Expressway-E certificate includes the Expressway-C FQDN as a SAN entry