500-710 Dumps With Exact Questions and Answers

The Expressway solution can be peered with a Cisco Unified Communications Manager to allow for greater capabilities.  This is true because the Expressway-C can connect to the Unified CM via a SIP trunk or a line-side connection, and the Expressway-E can enable firewall traversal and business-to-business communications for the Unified CM endpoints 1 2 .

The Expressway series can never operate as a standalone call-control solution.  This is false because the Expressway series can act as a standalone call-control solution for SIP and H.323 endpoints, and can provide interworking between them 1 3 .

The Expressway series requires the peering with a Cisco Unified Communications Manager to act as a call-control device.  This is false because the Expressway series does not depend on the Unified CM for call-control functionality, although it can enhance the Unified CM capabilities when peered with it 1 3 .

The Expressway series may operate as a standalone call-control solution.  This is true because the Expressway series can support SIP and H.323 endpoints without requiring the Unified CM, and can also provide session management and interworking features 1 3 .

The Expressway series only supports SIP-based communications.  This is false because the Expressway series supports both SIP and H.323 protocols, and can interwork between them 1 3 .  References  :=  1 :  Cisco Expressway Administrator Guide (X14.0) - Introduction   2 :  Cisco Expressway Administrator Guide (X15.0) - Unified Communications   3 :  Concept of Zones Demystified On Cisco Expressway Series

= The Cisco Meeting Server uses a RESTful API to interact with the server. The API commands are sent via HTTP requests to the web admin service, which processes them and returns the response. The four basic API commands are GET, POST, PUT, and DELETE.  Each command has a different function and syntax, as explained below 1 2 :

GET: Retrieves existing information from the server. The syntax is  GET /api/v1/ < object > / < id >  where  < object >  is the type of object to retrieve, such as call, participant, space, etc., and  < id >  is the unique identifier of the object, such as a UUID or a name. For example,  GET /api/v1/calls/12345678-1234-1234-1234-123456789012  will return the information about the call with the specified UUID.

POST: Creates new information on the server. The syntax is  POST /api/v1/ < object >  where  < object >  is the type of object to create, such as call, participant, space, etc. The request body contains the attributes and values of the object to create, in JSON format. For example,  POST /api/v1/spaces  with the request body  {"name": "Test Space", "uri": "test@domain.com"}  will create a new space with the specified name and URI.

PUT: Modifies existing information on the server. The syntax is  PUT /api/v1/ < object > / < id >  where  < object >  is the type of object to modify, such as call, participant, space, etc., and  < id >  is the unique identifier of the object, such as a UUID or a name. The request body contains the attributes and values of the object to modify, in JSON format. For example,  PUT /api/v1/spaces/12345678-1234-1234-1234-123456789012  with the request body  {"name": "New Name"}  will change the name of the space with the specified UUID to “New Name”.

DELETE: Deletes existing information from the server. The syntax is  DELETE /api/v1/ < object > / < id >  where  < object >  is the type of object to delete, such as call, participant, space, etc., and  < id >  is the unique identifier of the object, such as a UUID or a name. For example,  DELETE /api/v1/spaces/12345678-1234-1234-1234-123456789012  will delete the space with the specified UUID.

In this question, the API command that is used to modify a configuration setting on the Cisco Meeting Server is PUT, as it allows changing the attributes and values of an existing object on the server.

References  :=  Cisco Meeting Server Basic API Functions ,  Cisco Meeting Server - Programming Guides

= The scaled and resilient server deployment model is the best solution to accommodate fail-over for Cisco Meeting Server. This model involves deploying multiple Meeting Servers clustered together to provide greater scale and resilience in the deployment. The cluster can span across different locations and support up to 2500 HD ports. The cluster can also handle the failure of one or more servers without affecting the ongoing conferences or the user experience.  The cluster uses a load balancer to distribute the incoming calls among the available servers, and uses a database replication mechanism to synchronize the conference state and configuration across the servers 1 2 3   References  :=  1 Cisco Meeting Server - Configuration Guides   2 Cisco Meeting Server 3.8, Scaled and Resilient Server Deployment Guide   3 Cisco Meeting Server 3.8, White Paper on Load Balancing Calls Across Cisco Meeting Servers