384
Appendix
■
Answers to Practice Test Questions
57. B. The Cisco feature Software Defined-Access (SD-Access) is an automated Plug and
Play (PnP) solution that automates the underlay and overlay of the fabric. Easy-QOS was
a feature in the original Application Policy Infrastructure Controller-Enterprise Module
(APIC-EM); it has since been renamed Application Policies in Cisco DNA Center. The
System 360 feature inside of Cisco DNA Center allows you to view all of the settings
and health of the controller. The Cisco Identity Services Engine (ISE) is a product that
integrates with Cisco DNA Center to provide information about security groups and
identity of security principals.
58. C. Cisco DNA Center cannot provide device configuration backups; that function still
requires Cisco Prime Infrastructure (CPI). Cisco DNA Center can perform client coverage
heat maps, client triangulation, and application health reports.
59. D. In order for network discovery to find new network devices, you must configure
a command-line interface (CLI) of SSH or Telnet and Simple Network Management
Protocol (SNMP). Logging is not required for network discovery.
60. B. Representational state transfer (REST) APIs normally utilize HyperText Transfer
Protocol (HTTP) for moving data. It performs this via a get URI and it receives a response
in XML, JSON, or another data transfer language. Although you can encrypt the HTTP
traffic with SSL (HTTPS), its core language is still HTTP. Simple Network Management
Protocol (SNMP) and Simple Network Time Protocol (SNTP) are not used with REST
APIs. Simple Object Access Protocol (SOAP) is considered an alternate technology to
REST for API access.
61. B. You will authenticate with Cisco DNA Center by sending a POST request to the API
for an authentication token. You can then use the authentication token for all subsequent
requests to Cisco DNA Center. You will not pass the username and password; the
username and password must be encoded in Base64 to obtain the authentication token.
The
dna/system/api/v1/auth/token API requires a POST request to obtain the
authentication token, not a GET request. The Cisco DNA Center does not use public-
private key pairs for API authentication.
62. D. The CREATE, READ, UPDATE, DELETE (CRUD) framework describes the various
actions that can be performed on data via the REST-based API. Although CRUD sounds
like it might clean up memory, it has nothing to do with memory cleanup. It works in
conjunction with REST-based APIs as a framework for the manipulation of data. The
Base64 algorithm is used for data encoding, when it is needed.
63. A. Basic authentication is used for token requests with the Cisco DNA Center. Active
Directory (AD) integrated authentication and pass-through authentication are Microsoft-
only types of authentication, and the Cisco DNA Center does not support them. Secure
Sockets Layer (SSL) is a method of encryption for authentication requests, but it is not an
authentication method.
64. B. After the initial POST to obtain the authentication token, it should be placed in the
header of subsequent requests as an X-Auth-Token element. You will most likely use a
variable to store the token, but a variable by itself is not enough to authenticate subsequent
requests. The token is not passed in the URI of subsequent requests. Although performing
a POST within 10 seconds of the subsequent request is a good idea, if the token is not
placed in the header, it will not authenticate you.
Chapter 6: Automation and Programmability (Domain 6)
Do'stlaringiz bilan baham: |