Courseiva
mediumMultiple Select

200-901 Practice Question: A developer receives HTTP 409 Conflict when updating a network configuration via Cisco…

A developer receives HTTP 409 Conflict when updating a network configuration via Cisco NX-OS API. Which two scenarios could cause this error?

⚠ Common exam trap

Cisco often tests the distinction between client-side errors (400, 401) and server-side state conflicts (409), so the trap here is confusing a malformed request or authentication failure with a resource state conflict.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

The resource was recently modified by another client.

Option A is correct because HTTP 409 Conflict is returned when the target resource's state has changed since the client last read it, typically due to a concurrent modification by another client, so the update cannot be applied against the stale representation. Option B is correct because NX-OS API transactions can hold locks on configuration resources, and attempting to update a resource locked by another transaction produces a 409 Conflict indicating the request conflicts with the current state of the resource. Option C is not correct because malformed JSON causes a 400 Bad Request, as the server cannot parse the payload. Option D is not correct because unsupported parameters typically yield a 400 Bad Request or 422 Unprocessable Entity, not a 409. Option E is not correct because an invalid API key results in 401 Unauthorized (or 403 Forbidden), which is an authentication/authorization failure rather than a resource-state conflict.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✓

    The resource was recently modified by another client.

    Why this is correct

    409 Conflict means the request is valid but clashes with the resource's current state. If another client changed the configuration after this client read it, applying the update could overwrite their changes, so the server refuses. APIs detect this with version numbers or entity tags and conditional requests. The client should re-read the current state, merge its change, and retry.

  • ✓

    The update conflicts with a lock held by another transaction.

    Why this is correct

    When another session holds a lock on the configuration, for example during a transaction or a candidate configuration being edited, a conflicting write cannot be applied and the API returns a conflict instead of waiting indefinitely. The client should wait and retry with a backoff, or coordinate with the other process, rather than repeating the request immediately.

  • ✗

    The request body contains malformed JSON.

    Why it's wrong here

    Malformed JSON fails before the server even looks at the configuration: it cannot parse the request, so it returns 400 Bad Request. 409 is reserved for well-formed requests that conflict with the current state of the resource. Validating JSON before sending, for example with json.dumps() on a Python dictionary rather than building strings by hand, avoids 400 errors.

  • ✗

    The request includes unsupported parameters.

    Why it's wrong here

    Unsupported parameters typically yield HTTP 400 Bad Request, since the API rejects malformed or unknown fields during schema validation. A 409 Conflict signals a state clash, such as editing an object whose configuration revision no longer matches. This option is tempting because parameter errors are common API faults, but they map to 400, not 409.

  • ✗

    The API key used is invalid.

    Why it's wrong here

    An invalid API key or invalid credentials is rejected with 401 Unauthorized, before the server considers the request itself; valid credentials without permission produce 403 Forbidden. 409 only appears for authenticated, well-formed requests that conflict with the resource's current state. Checking the status code family quickly tells you whether to fix authentication, the request, or the state.

About these practice questions

This 200-901 question is part of Courseiva's 975-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

You might also like

Similar 200-901 questions

Written by Johnson Ajibi, MSc IT Security

Security Systems Architect · founder of Courseiva

This 200-901 practice question is part of Courseiva's free Cisco certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 200-901 exam.