Pass the Cisco Certified DevNet Associate 200-901 Questions and answers with ValidTests

Generating log bundles is a resource-intensive task that can cause high CPU utilization on the Cisco DNA Center. When the CPU spikes, it can affect the performance of other critical tasks, such as forwarding voice IP packets, leading to delays and poor voice quality. This is especially noticeable during business hours when network utilization is high, and voice traffic is sensitive to latency and jitter. More details can be found in Cisco DNA Center documentation on Managing Logs and System Performance.

The provided Ansible playbook is designed to connect to an IOS router and execute the "show run" command to retrieve the current running configuration. The configuration is then registered in a variable called config. The next task copies the output stored in the config variable to a file in a specified directory on the local machine. The file is named based on the router's hostname.

Here are the steps:

Define the hosts: The playbook targets the {{ router }} group or host.

Gather facts: Enabled with gather_facts: true to collect useful information about the target devices.

Connection type: Local, meaning the playbook runs on the local machine where Ansible is invoked.

Task 1 - ios_command:

Executes the "show run" command.

Uses the provided router credentials.

Registers the command output to the config variable.

Task 2 - copy:

Takes the first element from config.stdout (the output of the "show run" command).

Copies this content to a file in /etc/ansible/configs/, naming the file command_{{ router_hostname }}.txt.

To extract the value "172.16.0.11" from the given JSON data, you need to navigate through the JSON structure using the correct keys and indices. The JSON structure provided is as follows:

"items": [{

"kind": "object#NetworkObj",

"selfLink": "https://10.201.230.5/api/objects/networkobjects/db01 ",

"name": "db01",

"host": {

"kind": "IPv4Address",

"value": "172.16.0.11"

},

"objectId": "db01"

}]

}

Access the 'items' key: This gives you a list containing one object.

Access the first object in the 'items' list: Using the index [0].

Access the 'host' key: This contains the 'kind' and 'value' keys.

Access the 'value' key within the 'host' object: This gives you the required value "172.16.0.11".

Thus, the correct way to access the value "172.16.0.11" is data['items'][0]['host']['value'].

References:

JSON Parsing in Python: Python JSON Module

Cisco DevNet Documentation: DevNet JSON Handling

Solution as below

When using Basic Authentication in HTTP, the username and password are concatenated with a colon (:) in between. This concatenated string is then encoded using Base64. For the provided username devnet and password Cisco123, the string devnet:Cisco123 is encoded in Base64, resulting in ZGV2bmV0OkNpc2NvMTIz. This Base64 string is then included in the HTTP Authorization header. This process is described in the RFC 7617 and is a standard practice in HTTP Basic Authentication.

Bare Metal environments refer to physical servers that run directly on the hardware without a hypervisor. They offer several characteristics related to application deployment:

Provide workloads with access to hardware features: Bare Metal environments allow applications to directly access hardware resources, which can be critical for performance-sensitive applications.

Suitable for legacy applications that do not support virtualization: Some older applications may not be compatible with virtualized environments or may require direct access to physical hardware, making Bare Metal servers an ideal choice.

Bare Metal environments: Offer direct hardware access and are suitable for certain legacy applications.

Not specifically designed for container-based workloads: While containers can run on Bare Metal, these environments are not specifically tailored for containers.

Not providing hypervisors: Bare Metal environments do not include a hypervisor layer, which is a feature of virtualized environments.

The Python script provided makes a GET request to the Cisco DNA Center API to retrieve a list of network devices. The script processes the JSON response, iterates over each item in the response, and prints the hostname and management IP address of each device.

The process_devices function constructs the API URL using the dnac['host'].

It sends an HTTP GET request with the necessary headers, including the authentication token.

The response is parsed as JSON and stored in the data variable.

The script then loops through the data['response'] list, printing the hostname and managementIpAddress for each device.

The Python function shown in the exhibit performs the following operations:

It defines a function get_result().

Inside the function, it sets the url variable to the Cisco DNA Center (DNAC) API endpoint for authentication tokens.

It makes a POST request to the specified URL with HTTP Basic Authentication using the credentials DNAC_USER and DNAC_PASSWORD.

The response from the POST request is expected to be in JSON format.

It extracts the value associated with the key 'Token' from the JSON response.

Finally, it returns this token.

This function's purpose is to obtain and return an authorization token from the Cisco DNA Center API, which can be used for subsequent API requests.

Routing protocol traffic is handled on the control plane of a network device. The control plane is responsible for the exchange of routing information, the computation of the best paths, and the creation of the routing table. Protocols such as OSPF, BGP, and EIGRP operate at the control plane level to ensure that routers have the necessary information to make forwarding decisions. The data plane, on the other hand, is responsible for the actual forwarding of packets based on the routing table created by the control plane. More information on network planes can be found in the Cisco Networking Basics.

Solution below as

Cisco DNA Center provides a REST API that allows users to interact with the network devices managed by the platform. To retrieve a list of network devices, an HTTP GET request is sent to the endpoint https://DNA-c_API_ADDRESS/api/v1/network-device/ . The response from this request contains a list of network devices in JSON format. This API endpoint allows for programmatic access to network device data, facilitating automation and integration with other systems. Detailed information about the Cisco DNA Center APIs can be found in the Cisco DNA Center API documentation.

Top of Form

Bottom of Form

For Basic Authentication in REST APIs, the Base64 encoded credentials must be included in the header of the HTTP request. The correct method is to include the following header in the request:

Authorization: Basic am9objowMTlzNDU2Nzg=

References: Cisco DevNet Associate Certification Guide, Chapter on REST API Authentication methods.