Cisco CCNP 350-401 ENCOR Python, JSON, YANG, Catalyst Center/SD-WAN APIs, and REST Results Practice Test 2

Topic 19 Practice Test 2 covers Python, JSON, YANG, Catalyst Center/SD-WAN APIs, and REST Results for Cisco 350-401 ENCOR. For broader exam preparation, review the Cisco 350-401 ENCOR Exam Dumps. Every option includes focused technical reasoning explaining both the Cisco enterprise networking concept and its fit to the scenario.

Question 1

A Cisco network automation engineer has this requirement: decode JSON text from a file buffer before accessing nested keys. The implementation should not expand scope beyond this need. Which option solves the requirement at the correct layer? Choose ONE.

response.raise_for_status()
Conflict-aware handling for HTTP 409
Catalyst Center X-Auth-Token header
json.loads()

Correct Answer(s)

Rationale

response.raise_for_status() serves designs that must route HTTP failures into exception handling without manually testing every status code. It raises exceptions for unsuccessful HTTP responses. For this question the team must decode JSON text from a file buffer before accessing nested keys; and therefore is not the best fit.
Conflict-aware handling for HTTP 409 can be appropriate to resolve a create or update that conflicts with existing controller state. It addresses a resource state conflict. This case instead needs decode JSON text from a file buffer before accessing nested keys; leaving the stated need unsatisfied.
Catalyst Center X-Auth-Token header solves scenarios that need to fix a 401 caused by omitting the controller token header. It carries the Catalyst Center access token on API calls. But this case needs the team to decode JSON text from a file buffer before accessing nested keys; so the required behavior is still absent.
json.loads() is the best fit because it parses a JSON string into Python objects. The case requires the team to decode JSON text from a file buffer before accessing nested keys. The scenario depends on exactly that capability.

Question 2

A Cisco network automation engineer is reviewing how to emit valid JSON from in-memory Python data. The selected control should solve this condition directly. What should the team use? Choose ONE.

Explicit HTTP timeout
HTTP GET
Poll an asynchronous task identifier
json.dumps()

Correct Answer(s)

Rationale

Explicit HTTP timeout is intended to return control to retry logic when the API stops responding. It bounds how long an automation request waits. The stated constraint is to emit valid JSON from in-memory Python data; leaving the stated need unsatisfied.
HTTP GET normally helps teams query device inventory from an API. It retrieves a resource without requesting a state change. The design decision here is to emit valid JSON from in-memory Python data; so the required behavior is still absent.
Poll an asynchronous task identifier is useful when teams need to avoid assuming configuration is complete merely because the API accepted the request. It waits for controller-side job completion. The stem instead requires the team to emit valid JSON from in-memory Python data; so it misses the requirement here.
json.dumps() is the best fit because it serializes Python objects into a JSON string. The case requires the team to emit valid JSON from in-memory Python data. That property directly matches the constraint.

Question 3

A Cisco network automation engineer is planning a change to avoid separately passing response text to a JSON parser. Other controls are already satisfactory. Which approach addresses the stated constraint? Choose ONE.

Exponential backoff retry
HTTP POST
response.json()
YANG list key and modeled path

Correct Answer(s)

Rationale

Exponential backoff retry addresses cases that need to make large automation jobs resilient to short-lived API saturation. It spaces retries after transient throttling or server errors. The actual requirement is to avoid separately passing response text to a JSON parser; so the required behavior is still absent.
HTTP POST belongs where the goal is to create a new controller object through a REST endpoint. It submits data to create or invoke an operation. Here the need is to avoid separately passing response text to a JSON parser; so it misses the requirement here.
response.json() is the best fit because it decodes JSON directly from an HTTP response. The case requires the team to avoid separately passing response text to a JSON parser. The choice therefore fits without broadening scope.
YANG list key and modeled path can be appropriate to distinguish one repeated YANG list item from a singleton container. It identifies a unique list entry in structured network data. This case instead needs avoid separately passing response text to a JSON parser; rather than the decision posed here.

Question 4

A Cisco network automation engineer is evaluating a design that must keep error responses from being processed as though they were successful data. The team wants to avoid custom compensating code. Which option is the best fit? Choose ONE.

response.raise_for_status()
Refresh the API token after HTTP 401
HTTP PUT
json.loads()

Correct Answer(s)

Rationale

response.raise_for_status() is the best fit because it raises exceptions for unsuccessful HTTP responses. The case requires the team to keep error responses from being processed as though they were successful data. The choice therefore fits without broadening scope.
Refresh the API token after HTTP 401 solves scenarios that need to recover when Catalyst Center reports unauthorized because its token has expired. It handles expired or invalid authentication. But this case needs the team to keep error responses from being processed as though they were successful data; which leaves this requirement unresolved.
HTTP PUT is intended to repeat the same full-resource update without creating additional objects. It replaces a resource representation idempotently. The stated constraint is to keep error responses from being processed as though they were successful data; rather than the decision posed here.
json.loads() normally helps teams avoid manual string splitting when consuming structured JSON text. It parses a JSON string into Python objects. The design decision here is to keep error responses from being processed as though they were successful data; so it does not meet this constraint.

Question 5

A Cisco network automation engineer is correcting an implementation so it can make request latency failure deterministic for an orchestration pipeline. Existing unrelated behavior must remain intact. Which choice most directly meets the requirement? Choose ONE.

Correct authorization or role after HTTP 403
HTTP PATCH
json.dumps()
Explicit HTTP timeout

Correct Answer(s)

Rationale

Correct authorization or role after HTTP 403 normally helps teams grant the required controller role rather than repeatedly reauthenticating a forbidden user. It addresses authenticated-but-forbidden access. The design decision here is to make request latency failure deterministic for an orchestration pipeline; which leaves this requirement unresolved.
HTTP PATCH is useful when teams need to change only selected fields without resending the entire object. It applies a partial resource update. The stem instead requires the team to make request latency failure deterministic for an orchestration pipeline; rather than the decision posed here.
json.dumps() addresses cases that need to emit valid JSON from in-memory Python data. It serializes Python objects into a JSON string. The actual requirement is to make request latency failure deterministic for an orchestration pipeline; so it does not meet this constraint.
Explicit HTTP timeout is the best fit because it bounds how long an automation request waits. The case requires the team to make request latency failure deterministic for an orchestration pipeline. The scenario depends on exactly that capability.

Question 6

A Cisco network automation engineer has been asked to retry temporary 5xx failures with increasing delays. The rest of the architecture is already approved. What should be selected for this design? Choose ONE.

Correct the URI or identifier after HTTP 404
HTTP DELETE
response.json()
Exponential backoff retry

Correct Answer(s)

Rationale

Correct the URI or identifier after HTTP 404 belongs where the goal is to handle deletion or inventory drift when the requested resource no longer exists. It addresses a missing API resource. Here the need is to retry temporary 5xx failures with increasing delays; rather than the decision posed here.
HTTP DELETE serves designs that must delete an API-managed object by its resource URI. It removes the addressed REST resource. For this question the team must retry temporary 5xx failures with increasing delays; so it does not meet this constraint.
response.json() can be appropriate to avoid separately passing response text to a JSON parser. It decodes JSON directly from an HTTP response. This case instead needs retry temporary 5xx failures with increasing delays; which is a different design problem.
Exponential backoff retry is the best fit because it spaces retries after transient throttling or server errors. The case requires the team to retry temporary 5xx failures with increasing delays. That property directly matches the constraint.

Question 7

A Cisco network automation engineer needs a solution that can distinguish an authentication failure from a missing-resource response. The decision must follow the platform’s intended semantics. Which mechanism should the architect select? Choose ONE.

Conflict-aware handling for HTTP 409
Refresh the API token after HTTP 401
Content-Type header
response.raise_for_status()

Correct Answer(s)

Rationale

Conflict-aware handling for HTTP 409 solves scenarios that need to reconcile current state before retrying an operation rejected for conflict. It addresses a resource state conflict. But this case needs the team to distinguish an authentication failure from a missing-resource response; so it does not meet this constraint.
Refresh the API token after HTTP 401 is the best fit because it handles expired or invalid authentication. The case requires the team to distinguish an authentication failure from a missing-resource response. That property directly matches the constraint.
Content-Type header normally helps teams fix a request rejected because the server cannot interpret the submitted body format. It describes the media type of the request body. The design decision here is to distinguish an authentication failure from a missing-resource response; and therefore is not the best fit.
response.raise_for_status() is useful when teams need to route HTTP failures into exception handling without manually testing every status code. It raises exceptions for unsuccessful HTTP responses. The stem instead requires the team to distinguish an authentication failure from a missing-resource response; leaving the stated need unsatisfied.

Question 8

A Cisco network automation engineer must choose a mechanism to separate authorization policy failure from token-expiration handling. No broader redesign is requested. What is the most appropriate implementation? Choose ONE.

HTTP GET
Correct authorization or role after HTTP 403
Accept header
Explicit HTTP timeout

Correct Answer(s)

Rationale

HTTP GET is useful when teams need to perform a safe retrieval operation that should not create a new object. It retrieves a resource without requesting a state change. The stem instead requires the team to separate authorization policy failure from token-expiration handling; which is a different design problem.
Correct authorization or role after HTTP 403 is the best fit because it addresses authenticated-but-forbidden access. The case requires the team to separate authorization policy failure from token-expiration handling. This addresses the requirement at the intended layer.
Accept header belongs where the goal is to state which media type the client can consume in the response. It requests a preferred response representation. Here the need is to separate authorization policy failure from token-expiration handling; leaving the stated need unsatisfied.
Explicit HTTP timeout serves designs that must return control to retry logic when the API stops responding. It bounds how long an automation request waits. For this question the team must separate authorization policy failure from token-expiration handling; so the required behavior is still absent.

Question 9

A Cisco network automation engineer has this requirement: troubleshoot a valid token calling the wrong resource path. Unrelated availability and identity settings must not change. Which option solves the requirement at the correct layer? Choose ONE.

HTTP POST
Catalyst Center X-Auth-Token header
Correct the URI or identifier after HTTP 404
Exponential backoff retry

Correct Answer(s)

Rationale

HTTP POST serves designs that must invoke an action-style API whose documentation requires a POST body. It submits data to create or invoke an operation. For this question the team must troubleshoot a valid token calling the wrong resource path; and therefore is not the best fit.
Catalyst Center X-Auth-Token header can be appropriate to authenticate subsequent Catalyst Center requests after obtaining the token. It carries the Catalyst Center access token on API calls. This case instead needs troubleshoot a valid token calling the wrong resource path; leaving the stated need unsatisfied.
Correct the URI or identifier after HTTP 404 is the best fit because it addresses a missing API resource. The case requires the team to troubleshoot a valid token calling the wrong resource path. It satisfies the case while preserving unrelated controls.
Exponential backoff retry is intended to make large automation jobs resilient to short-lived API saturation. It spaces retries after transient throttling or server errors. The stated constraint is to troubleshoot a valid token calling the wrong resource path; so it misses the requirement here.

Question 10

A Cisco network automation engineer is reviewing how to avoid treating a duplicate-resource conflict as a transport outage. The change should be limited to the relevant layer. What should the team use? Choose ONE.

HTTP PUT
Poll an asynchronous task identifier
Conflict-aware handling for HTTP 409
Refresh the API token after HTTP 401

Correct Answer(s)

Rationale

HTTP PUT is intended to choose replacement semantics rather than a partial field change. It replaces a resource representation idempotently. The stated constraint is to avoid treating a duplicate-resource conflict as a transport outage; leaving the stated need unsatisfied.
Poll an asynchronous task identifier normally helps teams track a long-running controller operation after the initial request returns a task reference. It waits for controller-side job completion. The design decision here is to avoid treating a duplicate-resource conflict as a transport outage; so the required behavior is still absent.
Conflict-aware handling for HTTP 409 is the best fit because it addresses a resource state conflict. The case requires the team to avoid treating a duplicate-resource conflict as a transport outage. That is the requested behavior here.
Refresh the API token after HTTP 401 addresses cases that need to request a fresh token before repeating a call rejected as unauthenticated. It handles expired or invalid authentication. The actual requirement is to avoid treating a duplicate-resource conflict as a transport outage; which leaves this requirement unresolved.

Question 11

A Cisco network automation engineer is planning a change to read controller state before deciding whether a change is required. Only this stated constraint is driving the decision. Which approach addresses the stated constraint? Choose ONE.

HTTP PATCH
YANG list key and modeled path
Correct authorization or role after HTTP 403
HTTP GET

Correct Answer(s)

Rationale

HTTP PATCH addresses cases that need to preserve unspecified resource fields while applying a targeted update. It applies a partial resource update. The actual requirement is to read controller state before deciding whether a change is required; so the required behavior is still absent.
YANG list key and modeled path belongs where the goal is to address one interface entry in a YANG list using its key. It identifies a unique list entry in structured network data. Here the need is to read controller state before deciding whether a change is required; so it misses the requirement here.
Correct authorization or role after HTTP 403 serves designs that must separate authorization policy failure from token-expiration handling. It addresses authenticated-but-forbidden access. For this question the team must read controller state before deciding whether a change is required; which leaves this requirement unresolved.
HTTP GET is the best fit because it retrieves a resource without requesting a state change. The case requires the team to read controller state before deciding whether a change is required. This addresses the requirement at the intended layer.

Question 12

A Cisco network automation engineer is evaluating a design that must request a token from an authentication endpoint that specifies POST. The team wants the most specific native mechanism. Which option is the best fit? Choose ONE.

HTTP POST
HTTP DELETE
json.loads()
Correct the URI or identifier after HTTP 404

Correct Answer(s)

Rationale

HTTP POST is the best fit because it submits data to create or invoke an operation. The case requires the team to request a token from an authentication endpoint that specifies POST. The choice therefore fits without broadening scope.
HTTP DELETE solves scenarios that need to delete an API-managed object by its resource URI. It removes the addressed REST resource. But this case needs the team to request a token from an authentication endpoint that specifies POST; which leaves this requirement unresolved.
json.loads() is intended to decode JSON text from a file buffer before accessing nested keys. It parses a JSON string into Python objects. The stated constraint is to request a token from an authentication endpoint that specifies POST; rather than the decision posed here.
Correct the URI or identifier after HTTP 404 normally helps teams handle deletion or inventory drift when the requested resource no longer exists. It addresses a missing API resource. The design decision here is to request a token from an authentication endpoint that specifies POST; so it does not meet this constraint.

Question 13

A Cisco network automation engineer is correcting an implementation so it can repeat the same full-resource update without creating additional objects. The implementation should not expand scope beyond this need. Which choice most directly meets the requirement? Choose ONE.

Content-Type header
json.dumps()
HTTP PUT
Conflict-aware handling for HTTP 409

Correct Answer(s)

Rationale

Content-Type header normally helps teams differentiate request-body encoding from the response format the client would prefer. It describes the media type of the request body. The design decision here is to repeat the same full-resource update without creating additional objects; which leaves this requirement unresolved.
json.dumps() is useful when teams need to convert a Python dictionary into JSON text for logging or a request body. It serializes Python objects into a JSON string. The stem instead requires the team to repeat the same full-resource update without creating additional objects; rather than the decision posed here.
HTTP PUT is the best fit because it replaces a resource representation idempotently. The case requires the team to repeat the same full-resource update without creating additional objects. It satisfies the case while preserving unrelated controls.
Conflict-aware handling for HTTP 409 belongs where the goal is to reconcile current state before retrying an operation rejected for conflict. It addresses a resource state conflict. Here the need is to repeat the same full-resource update without creating additional objects; which is a different design problem.

Question 14

A Cisco network automation engineer has been asked to use RESTCONF to modify a subset of YANG-modeled configuration. The selected control should solve this condition directly. What should be selected for this design? Choose ONE.

Accept header
HTTP PATCH
response.json()
HTTP GET

Correct Answer(s)

Rationale

Accept header belongs where the goal is to separate response-content negotiation from the encoding of the request body. It requests a preferred response representation. Here the need is to use RESTCONF to modify a subset of YANG-modeled configuration; rather than the decision posed here.
HTTP PATCH is the best fit because it applies a partial resource update. The case requires the team to use RESTCONF to modify a subset of YANG-modeled configuration. The scenario depends on exactly that capability.
response.json() can be appropriate to avoid separately passing response text to a JSON parser. It decodes JSON directly from an HTTP response. This case instead needs use RESTCONF to modify a subset of YANG-modeled configuration; which is a different design problem.
HTTP GET solves scenarios that need to perform a safe retrieval operation that should not create a new object. It retrieves a resource without requesting a state change. But this case needs the team to use RESTCONF to modify a subset of YANG-modeled configuration; and therefore is not the best fit.

Question 15

A Cisco network automation engineer needs a solution that can express removal through the standard REST method rather than an update workaround. Other controls are already satisfactory. Which mechanism should the architect select? Choose ONE.

HTTP DELETE
Catalyst Center X-Auth-Token header
response.raise_for_status()
HTTP POST

Correct Answer(s)

Rationale

HTTP DELETE is the best fit because it removes the addressed REST resource. The case requires the team to express removal through the standard REST method rather than an update workaround. That is the requested behavior here.
Catalyst Center X-Auth-Token header is intended to authenticate subsequent Catalyst Center requests after obtaining the token. It carries the Catalyst Center access token on API calls. The stated constraint is to express removal through the standard REST method rather than an update workaround; which is a different design problem.
response.raise_for_status() normally helps teams keep error responses from being processed as though they were successful data. It raises exceptions for unsuccessful HTTP responses. The design decision here is to express removal through the standard REST method rather than an update workaround; and therefore is not the best fit.
HTTP POST is useful when teams need to invoke an action-style API whose documentation requires a POST body. It submits data to create or invoke an operation. The stem instead requires the team to express removal through the standard REST method rather than an update workaround; leaving the stated need unsatisfied.

Question 16

A Cisco network automation engineer must choose a mechanism to fix a request rejected because the server cannot interpret the submitted body format. The team wants to avoid custom compensating code. What is the most appropriate implementation? Choose ONE.

Content-Type header
Poll an asynchronous task identifier
Explicit HTTP timeout
HTTP PUT

Correct Answer(s)

Rationale

Content-Type header is the best fit because it describes the media type of the request body. The case requires the team to fix a request rejected because the server cannot interpret the submitted body format. The choice therefore fits without broadening scope.
Poll an asynchronous task identifier addresses cases that need to track a long-running controller operation after the initial request returns a task reference. It waits for controller-side job completion. The actual requirement is to fix a request rejected because the server cannot interpret the submitted body format; and therefore is not the best fit.
Explicit HTTP timeout belongs where the goal is to make request latency failure deterministic for an orchestration pipeline. It bounds how long an automation request waits. Here the need is to fix a request rejected because the server cannot interpret the submitted body format; leaving the stated need unsatisfied.
HTTP PUT serves designs that must choose replacement semantics rather than a partial field change. It replaces a resource representation idempotently. For this question the team must fix a request rejected because the server cannot interpret the submitted body format; so the required behavior is still absent.

Question 17

A Cisco network automation engineer has this requirement: state which media type the client can consume in the response. Existing unrelated behavior must remain intact. Which option solves the requirement at the correct layer? Choose ONE.

YANG list key and modeled path
Accept header
Exponential backoff retry
HTTP PATCH

Correct Answer(s)

Rationale

YANG list key and modeled path serves designs that must distinguish one repeated YANG list item from a singleton container. It identifies a unique list entry in structured network data. For this question the team must state which media type the client can consume in the response; and therefore is not the best fit.
Accept header is the best fit because it requests a preferred response representation. The case requires the team to state which media type the client can consume in the response. That makes it the narrowest correct answer.
Exponential backoff retry solves scenarios that need to retry temporary 5xx failures with increasing delays. It spaces retries after transient throttling or server errors. But this case needs the team to state which media type the client can consume in the response; so the required behavior is still absent.
HTTP PATCH is intended to preserve unspecified resource fields while applying a targeted update. It applies a partial resource update. The stated constraint is to state which media type the client can consume in the response; so it misses the requirement here.

Question 18

A Cisco network automation engineer is reviewing how to fix a 401 caused by omitting the controller token header. The rest of the architecture is already approved. What should the team use? Choose ONE.

json.loads()
Refresh the API token after HTTP 401
Catalyst Center X-Auth-Token header
HTTP DELETE

Correct Answer(s)

Rationale

json.loads() is intended to avoid manual string splitting when consuming structured JSON text. It parses a JSON string into Python objects. The stated constraint is to fix a 401 caused by omitting the controller token header; leaving the stated need unsatisfied.
Refresh the API token after HTTP 401 normally helps teams recover when Catalyst Center reports unauthorized because its token has expired. It handles expired or invalid authentication. The design decision here is to fix a 401 caused by omitting the controller token header; so the required behavior is still absent.
Catalyst Center X-Auth-Token header is the best fit because it carries the Catalyst Center access token on API calls. The case requires the team to fix a 401 caused by omitting the controller token header. That is the requested behavior here.
HTTP DELETE addresses cases that need to remove YANG-modeled data through a RESTCONF endpoint that supports DELETE. It removes the addressed REST resource. The actual requirement is to fix a 401 caused by omitting the controller token header; which leaves this requirement unresolved.

Question 19

A Cisco network automation engineer is planning a change to avoid assuming configuration is complete merely because the API accepted the request. The decision must follow the platform’s intended semantics. Which approach addresses the stated constraint? Choose ONE.

Poll an asynchronous task identifier
json.dumps()
Correct authorization or role after HTTP 403
Content-Type header

Correct Answer(s)

Rationale

Poll an asynchronous task identifier is the best fit because it waits for controller-side job completion. The case requires the team to avoid assuming configuration is complete merely because the API accepted the request. That is the requested behavior here.
json.dumps() belongs where the goal is to convert a Python dictionary into JSON text for logging or a request body. It serializes Python objects into a JSON string. Here the need is to avoid assuming configuration is complete merely because the API accepted the request; so it misses the requirement here.
Correct authorization or role after HTTP 403 serves designs that must separate authorization policy failure from token-expiration handling. It addresses authenticated-but-forbidden access. For this question the team must avoid assuming configuration is complete merely because the API accepted the request; which leaves this requirement unresolved.
Content-Type header can be appropriate to differentiate request-body encoding from the response format the client would prefer. It describes the media type of the request body. This case instead needs avoid assuming configuration is complete merely because the API accepted the request; rather than the decision posed here.

Question 20

A Cisco network automation engineer is evaluating a design that must build a RESTCONF path that selects a specific modeled list instance. No broader redesign is requested. Which option is the best fit? Choose ONE.

response.json()
YANG list key and modeled path
Correct the URI or identifier after HTTP 404
Accept header

Correct Answer(s)

Rationale

response.json() can be appropriate to extract keys from a REST response whose media type is JSON. It decodes JSON directly from an HTTP response. This case instead needs build a RESTCONF path that selects a specific modeled list instance; so it misses the requirement here.
YANG list key and modeled path is the best fit because it identifies a unique list entry in structured network data. The case requires the team to build a RESTCONF path that selects a specific modeled list instance. This addresses the requirement at the intended layer.
Correct the URI or identifier after HTTP 404 is intended to troubleshoot a valid token calling the wrong resource path. It addresses a missing API resource. The stated constraint is to build a RESTCONF path that selects a specific modeled list instance; rather than the decision posed here.
Accept header normally helps teams separate response-content negotiation from the encoding of the request body. It requests a preferred response representation. The design decision here is to build a RESTCONF path that selects a specific modeled list instance; so it does not meet this constraint.

All Certifications, Certifications

Related posts:

Leave a Reply Cancel reply