A Cisco Meeting Server cluster is deployed across three data centers. One is headquarters, and two are branch offices. Which database deployment is ideal for geo-redundancy in multiple locations?

An administrator sets up conference resources by using a clustered Cisco Meeting Server deployment for video endpoints that are registered to Expressway. The administrator must ensure that no single server gets overloaded within the cluster. What should be configured to accomplish this goal?

Refer to the exhibit.

An administrator tries to access Cisco TMS GUI and sees this error message. Which step resolves this issue?

Refer to the exhibit.
guest login request 562763450: resolution in progress
guest login request 562763450: call ID lookup scheduled
guest login request 562763450: resolution in progress
guest login request 562763450: credential storage scheduled (queue length: 1) created guest account with user ID "quest487660227" guest login request 562763450: credential storage executed guest login request 562763450: credential storage in progress guest login request 562763450: successfully stored credentials instantiating user "guest487660227" conference f5771a88-0f36-4b58-8dbd-934aaa579ebf: locked due to lack of lock consensus conference f5771a88-0f36-4b58-8dbd-934aaa579ebf: lock state has changed to locked API "3.0 Record Test Space" Space GUID: 71b4f99f-2365-4730-b3d9-d2d61505150c <--> Call Correlator GUID: 334b0c10-6f85-4760-97ab- conference f5771a88-0f36-4b58-8dbd-934aaa579ebf: lock state has changed to unlocked starting automatic recording (space "3.0 Record Test Space") API call leg 121d2c87-6940-4483-8d3d-71ff162947ba in call f5771a88-0f36-4b58b8dbd-934aaa579ebf (API call 5a0a7f49-78f8-46fd-add9-4a conference f5771a88-0f36-4b58-8dbd-934aaa579ebf has control/media GUID:
d7f2d940-c7d9-4421-8f13-7bf94756b08a
conference f5771a88-0f36-4b58-8dbd-934aaa579ebf named "3.0 Record Test Space" unable to start recording - recorder URI not configured new session created for user "guest487660227" call 49: allocated for guest487660227 "Web" conference participation call 49: configured - API call leg 121d2c87-6940-4483-8d3d-8d3d-71ff162947ba call 49: setting up combined RTP session for DTLS (combined media and control) participant "quest487660227" joined space 71b4f99f-2365-4730-b3d9-d2d61505150c (3.0 Record Test Space) participant "quest487660227" (121d2c87-6940-4483-8d3d-71ff162947ba) joined conference f5771a88-0f36-4b58-8dbd-934aaa579ebf via W call 49: starting DTLS combined media negotiation (as initiator) call 49: completed DTLS combined media negotiation invalid API operation - unhandleable URI /api/v1/recorders user "guest487660227": deactivating due to session resource teardown call 49: tearing down ("guest487660227" conference media) call 449: destroying API call leg 121d2c87-6940-4483-8d3d-71ff162947ba An administrator tries to implement a recording with a Cisco Meeting Server version 3.0 deployment. A separate VM is deployed and configured with the recorder service. During testing, it is discovered that the recording is failing, and the administrator collects logs.
Which configuration step should be completed?

Which type of zone should be configured on the Expressway-C to route calls to Cisco Meeting Server spaces?