Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Cisco Exam 500-710 Topic 1 Question 92 Discussion

Actual exam question for Cisco's 500-710 exam
Question #: 92
Topic #: 1
[All 500-710 Questions]

Where must TURN servers be configured in a resilient and scalable Cisco Meeting Servers solution?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

Salome
4 months ago
I hope the correct answer isn't A. That would be like trying to balance a bowling ball on a toothpick.
upvoted 0 times
...
Erick
4 months ago
I bet the engineers who came up with this question were having a field day, like 'Let's see if they can handle this one!'
upvoted 0 times
Isadora
4 months ago
D) CMS core and CMS edge
upvoted 0 times
...
Margarett
4 months ago
B) CMS core, CMS edge, and Cisco Unified Communications Manager
upvoted 0 times
...
...
Elsa
4 months ago
C? No way, man. You can't just leave the TURN servers on the edge, that's a disaster waiting to happen. D is the only logical choice here.
upvoted 0 times
Hana
3 months ago
Definitely, it's better to be safe than sorry when it comes to TURN servers.
upvoted 0 times
...
Twanna
4 months ago
Yeah, having redundancy in place is crucial for a scalable solution.
upvoted 0 times
...
Becky
4 months ago
I agree, having TURN servers on both the core and edge is the best option for resilience.
upvoted 0 times
...
...
Brandon
4 months ago
I think TURN servers should be configured in CMS core and CMS edge. This way, we can distribute the load and improve performance.
upvoted 0 times
...
Van
5 months ago
D is the way to go. Gotta have that redundancy in the TURN servers for a robust setup.
upvoted 0 times
Marti
3 months ago
Having TURN servers on both the core and edge ensures a scalable and robust Cisco Meeting Servers solution.
upvoted 0 times
...
Davida
4 months ago
It's important to have a resilient setup with TURN servers on both the core and edge.
upvoted 0 times
...
France
4 months ago
I agree, having TURN servers on both the core and edge is essential for redundancy.
upvoted 0 times
...
Hyman
4 months ago
Having TURN servers in both the core and edge is the best practice for a resilient and scalable solution.
upvoted 0 times
...
Vivan
4 months ago
Definitely, it's important to ensure a robust setup with redundancy in place.
upvoted 0 times
...
Jacob
4 months ago
I agree, having TURN servers in both the core and edge is essential for redundancy.
upvoted 0 times
...
...
Tegan
5 months ago
I believe TURN servers are only needed in CMS core. It should be enough for a Cisco Meeting Servers solution.
upvoted 0 times
...
Vi
5 months ago
I agree with Mira. Having TURN servers in multiple locations ensures resilience and scalability.
upvoted 0 times
...
Mira
5 months ago
I think TURN servers should be configured in CMS core, CMS edge, and Cisco Unified Communications Manager.
upvoted 0 times
...
Coral
5 months ago
Hmm, seems like a tricky one. I'll go with B. Better safe than sorry, right?
upvoted 0 times
...
Felix
5 months ago
I think the correct answer is D. TURN servers must be configured in both the CMS core and CMS edge for a resilient and scalable Cisco Meeting Servers solution.
upvoted 0 times
Jacquline
4 months ago
Having TURN servers in both locations helps with load balancing and redundancy in case one location fails.
upvoted 0 times
...
Marcos
4 months ago
I thought it was only necessary to have TURN servers in the CMS core. Good to know it should also be in the CMS edge.
upvoted 0 times
...
Santos
5 months ago
Yes, that's correct. Having TURN servers in both locations ensures a resilient and scalable Cisco Meeting Servers solution.
upvoted 0 times
...
Celeste
5 months ago
I believe the correct answer is D. TURN servers should be configured in both the CMS core and CMS edge.
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