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

Cisco Exam 500-710 Topic 1 Question 84 Discussion

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

Which statement about setting up a call bridge cluster for a resilient and scalable Cisco Meeting Server deployment is true?

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

Myra
4 months ago
Call bridges should be able to read/write to any database in a cluster to ensure redundancy and scalability.
upvoted 0 times
...
Maybelle
4 months ago
Why do you think that, Myra?
upvoted 0 times
...
Myra
4 months ago
I disagree, I believe the correct answer is D.
upvoted 0 times
...
Maybelle
4 months ago
Having only one call bridge configured per domain in a database cluster ensures efficiency and avoids conflicts.
upvoted 0 times
...
Janna
4 months ago
Why do you think that, Maybelle?
upvoted 0 times
...
Maybelle
4 months ago
I think the correct answer is C.
upvoted 0 times
...
Carla
5 months ago
I see your point. Maybe C is the correct answer after all.
upvoted 0 times
...
Jenise
5 months ago
I agree with Having one call bridge per domain sounds more efficient.
upvoted 0 times
...
Elly
5 months ago
But wouldn't it make more sense to have only one call bridge per domain?
upvoted 0 times
...
Carla
5 months ago
I disagree, I believe it's A.
upvoted 0 times
...
Elly
5 months ago
I think the right answer is C.
upvoted 0 times
...
Clarinda
6 months ago
Hmm, that makes sense. But option D, where call bridges can read and write to any database in the cluster at any time, sounds the most flexible to me.
upvoted 0 times
...
Cristal
6 months ago
Ooh, option D sounds interesting! 'Call bridges can read/write to any database in a cluster at any time.' That could offer a lot of flexibility and redundancy. But I wonder if there are any trade-offs or potential issues with that approach.
upvoted 0 times
...
Frank
6 months ago
Okay, let's start with option A. I don't think that's correct, as a full mesh connection between call bridges and databases might not be the most efficient or scalable approach.
upvoted 0 times
...
Clay
6 months ago
Good point. Option C, where only one call bridge is configured per domain in a database cluster, might be a better solution. That way, you have redundancy at the domain level.
upvoted 0 times
...
Izetta
6 months ago
You're right. Option B sounds more plausible, where the call bridges only connect to a master database. That would provide a centralized point of control and management.
upvoted 0 times
Deeann
5 months ago
Agreed. Having call bridges connect to a master database simplifies coordination.
upvoted 0 times
...
Adelina
5 months ago
I think option B is the correct choice.
upvoted 0 times
...
...
Kris
6 months ago
I agree. Option B, where call bridges only connect to the master database, seems like a more centralized approach. But I wonder if that could be a single point of failure?
upvoted 0 times
Florencia
5 months ago
User 2
upvoted 0 times
...
Tonette
5 months ago
User 1
upvoted 0 times
...
Tu
5 months ago
User 2
upvoted 0 times
...
Gerald
5 months ago
User 1
upvoted 0 times
...
...
German
6 months ago
Hmm, I'm not sure about that. Option C mentions something about only one call bridge per domain in a database cluster. That might be the way to go for a resilient and scalable deployment.
upvoted 0 times
...
Wayne
6 months ago
Okay, let's start with option A. Connecting call bridges to databases in full mesh sounds like it could work, but I'm not sure if that's the most efficient or resilient setup.
upvoted 0 times
...
Val
6 months ago
Yeah, me neither. But let's think through the options and see if we can figure it out.
upvoted 0 times
...
Carlton
6 months ago
Hmm, this question seems a bit tricky. I'm not sure if I fully understand the concept of a call bridge cluster for Cisco Meeting Server deployment.
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