300-835 · Question #2
Which two files must be downloaded from a Cisco Unified Communications Manager server in order to build requests for the AXL API? (Choose two.)
The correct answer is A. AXLEnums.xsd C. AXLSoap.wsdl. To interact with CUCM's AXL SOAP API, you need AXLEnums.xsd (A) because it is the XML Schema Definition file that defines the valid enumeration types and data structures used in AXL requests, and AXLSoap.wsdl (C) because the WSDL (Web Services Description Language) file describes
Question
Options
- AAXLEnums.xsd
- BAXL_CUCM.xsd
- CAXLSoap.wsdl
- DCUCM_AXL.json
- EAXLWSDL.xml
How the community answered
(46 responses)- A93% (43)
- D4% (2)
- E2% (1)
Explanation
To interact with CUCM's AXL SOAP API, you need AXLEnums.xsd (A) because it is the XML Schema Definition file that defines the valid enumeration types and data structures used in AXL requests, and AXLSoap.wsdl (C) because the WSDL (Web Services Description Language) file describes the available operations, message formats, and binding details needed to construct valid SOAP calls. Together, these two files give a client application everything it needs to know the shape of every AXL request and response.
The distractors are wrong for the following reasons:
- B (AXL_CUCM.xsd) - the filename is fabricated; no such file exists in the CUCM AXL download package.
- D (CUCM_AXL.json) - AXL is entirely SOAP/XML-based; JSON is not part of the AXL interface.
- E (AXLWSDL.xml) - a plausible-sounding distractor, but the actual WSDL file is named
AXLSoap.wsdl, not this.
Memory tip: AXL = Administrative XML Layer - it's pure XML/SOAP, so you always need a .wsdl (service description) and an .xsd (schema/enumerations). The real files follow the pattern AXLSoap.wsdl and AXLEnums.xsd - both start with "AXL," making the two imposters (wrong prefix or wrong format) easy to eliminate.
Topics
Community Discussion
No community discussion yet for this question.