Free Cisco 200-901 Practice Exam with Questions & Answers | Set: 14

The HTTP status code 400 (Bad Request) is used by a REST API to indicate that the server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).

To ensure the result set is returned in reverse chronological order based on when messages were entered, we need to use the sortBy parameter with the value lastactivity. This parameter sorts the rooms by their last activity timestamp, ensuring the most recent rooms are listed first.

Example:

GET /v1/rooms?sortBy=lastactivity

References:

Cisco Webex Teams API Documentation (explains query parameters and their usage in API calls)

Cisco DevNet Associate Exam Topics: APIs and Automation (understanding how to utilize query parameters to retrieve data)

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

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.

1 – A, 2 – B, 3 – D, 4 – C

The docker run -p 3000:5000 command maps port 3000 on the host to port 5000 on the Docker container. This means that any process on the host that wants to access the service running inside the container should connect to port 3000 on the host. The service inside the container listens on port 5000, but from the host's perspective, it will be accessed via port 3000. More information on Docker port mapping can be found in the Docker documentation.

A router is a network device that routes traffic between different broadcast domains and subnets. Routers operate at the network layer (Layer 3) of the OSI model and use IP addresses to make forwarding decisions. They are responsible for determining the best path for data packets to travel across interconnected networks, ensuring that traffic is correctly directed from one broadcast domain to another.

References:

Cisco Router Basics

Broadcast Domains and Routers

=========================

YANG model-driven programmability allows for the configuration of devices using data models. In NX-OS, this includes both native and OpenConfig-based models.

YANG Models: These are used to model configuration and state data for network devices. Native models are specific to the vendor, while OpenConfig models are vendor-neutral.

Configuration Management: YANG models facilitate consistent and programmable configuration of network devices, which can be done through APIs like NETCONF or RESTCONF.