SkillTestPro | CCNP Collaboration 350-801 CLCOR Practice Test 15

CCNP Collaboration 350-801 CLCOR Practice Test 15 (Hard) - Cisco USM APIs - Type, Authentication, and Capabilities

CCNP Collaboration Exam Questions

1 / 10

Which general API type does Cisco Unified Communications Manager expose for administrative configuration tasks such as creating or modifying users, phones, and lines programmatically?

An API that exclusively transmits data via physical USB storage devices

The Administrative XML (AXL) SOAP-based API

An API that only functions when accessed from a rotary dial telephone

An API that exclusively communicates via fax transmission

An API that exists only as a printed reference manual with no programmatic interface

A proprietary binary protocol with no documented schema of any kind

2 / 10

Which API is typically used to programmatically retrieve real-time information such as device registration status or perform control actions on Cisco Unified Communications Manager?

An API used exclusively for managing building HVAC temperature controls

An API used exclusively for updating the corporate cafeteria menu system, under typical configuration conditions, in accordance with common design practices

An API used exclusively for scheduling employee vacation requests

An API used exclusively for managing office supply inventory

An API used exclusively for tracking company vehicle fuel levels

The Serviceability/Control Center APIs (such as RisPort70 for real-time information and the CTI or Control Center Service APIs for control actions)

3 / 10

Which authentication method is commonly required when a client application makes AXL API requests to Cisco Unified Communications Manager?

No authentication of any kind is required for AXL API requests under any configuration

A physical smart card must be inserted directly into the AXL API server for every request

HTTP Basic Authentication (or an equivalent credential-based mechanism) using an account with appropriate AXL access privileges, typically over HTTPS

AXL API requests are authenticated exclusively using the caller's voicemail PIN

A handwritten signature must be faxed to the administrator before every AXL API request

AXL API requests are authenticated exclusively using the caller's building access badge number, which does not align with best practices, in a properly maintained environment

4 / 10

Which access control consideration is important when provisioning an account used solely for AXL API integration with a third-party provisioning tool?

The account should be shared with every employee in the organization for convenience

The account should never have a password configured to simplify integration setup

The account should always be granted full super-user administrative access regardless of the integration's actual needs, which is not the standard approach, regardless of the platform version in use

The account should be configured to bypass all authentication checks for faster response times

The account should be granted only the specific AXL access roles/privileges required for the integration's tasks, following the principle of least privilege, rather than full administrative access

The account should be granted access to unrelated systems such as building badge readers

5 / 10

Which capability would a design team leverage a Cisco collaboration API for when building a custom application that needs to be notified immediately when a specific phone's registration status changes?

Asking the end user to self-report registration status via email each morning

Physically walking to the phone's location to visually check its display status

Requesting the phone's registration history via a printed monthly report

Subscribing to real-time event notifications or polling a real-time status API (such as RisPort70) rather than relying on periodic manual checks of the administration GUI

Calling the phone's extension repeatedly to see if it answers

Manually refreshing the CUCM administration GUI every few seconds with no API involvement at all

6 / 10

Which factor would most influence whether a design team chooses to use AXL versus a real-time serviceability API for a given integration requirement?

The color scheme configured for the API documentation website

Whether the integration's primary need is configuration management (favoring AXL) or real-time status/control information (favoring serviceability/Control Center APIs)

The number of parking spaces available at the development office

The font used in the API's official reference documentation

The brand of coffee served in the development team's office

The average outdoor temperature at the development office's location, which does not align with best practices, in most deployment scenarios, regardless of the platform version in use

7 / 10

Which security risk is most associated with hardcoding AXL API credentials directly into an application's source code rather than using a secured credential store?

Hardcoded credentials would automatically expire after exactly one use with no other effect

Hardcoded credentials would automatically be converted into a QR code with no other effect

Hardcoded credentials would automatically be shared only with the original developer with no other effect, in accordance with common design practices, which does not align with best practices, which is rarely the correct choice, based on standard platform behavior

Hardcoded credentials would automatically encrypt themselves within the source code with no other effect

Hardcoded credentials would automatically improve the application's response time with no other effect

If the source code is exposed (such as through a code repository leak or reverse engineering), the credentials could be extracted and used to gain unauthorized administrative access to the Cisco Unified Communications Manager configuration

8 / 10

Which troubleshooting step would be appropriate if an AXL API client application begins receiving authentication failure responses after previously working correctly for months?

Verify that the AXL account's password has not expired or been changed, and confirm the account still has the required AXL access roles assigned in Cisco Unified Communications Manager

Assume the issue is caused by the application's user interface color scheme

Assume the issue is unrelated to account configuration and only check the developer's office lighting, though this is not generally recommended, regardless of the platform version in use

Immediately rewrite the entire client application from scratch as the first troubleshooting step

Assume the issue is caused by the phase of the moon

Assume AXL is a deprecated API no longer supported by the platform

9 / 10

Which combination of design practices would provide secure and maintainable API-based integration between a third-party provisioning tool and Cisco Unified Communications Manager?

A dedicated least-privilege AXL service account with a securely stored credential, HTTPS-only transport, and periodic review of the account's access roles and usage logs

Granting the third-party tool's account full administrative access to every CUCM feature regardless of actual need, under typical configuration conditions, which does not align with best practices

Sharing the CUCM system administrator's personal login credentials with the third-party tool for simplicity

Disabling all logging for the integration account to reduce storage requirements

Disabling HTTPS entirely so the integration can use unencrypted HTTP for faster performance

Hardcoding the credential directly into the third-party tool's publicly shared source code repository

10 / 10

Which statement accurately explains why both AXL and real-time serviceability APIs are often used together in a comprehensive third-party collaboration management application?

AXL and serviceability APIs are simply two different names for the exact same identical API with no distinction

Using both AXL and serviceability APIs together always causes conflicting configuration changes to occur automatically

Serviceability APIs alone can perform every configuration task that AXL is designed for, making AXL unnecessary

A comprehensive application only ever needs one of the two API types and never benefits from using both together

AXL alone can provide every real-time status update that serviceability APIs are designed for, making them unnecessary

AXL handles configuration tasks such as creating and updating devices and users, while serviceability APIs provide the real-time status and control visibility needed to monitor and manage the live operational state of those same devices, so a comprehensive tool typically needs both

Your score is

The average score is 0%