200-901 Understanding and Using APIs Practice Question

Answer analysis

Option-by-option breakdown

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

• ✓

  application/yang-data+json

  Why this is correct

  `application/yang-data+json` is the media type RESTCONF mandates for JSON-encoded YANG data, as defined in RFC 8040. It satisfies the stem's JSON encoding constraint by pairing the `+json` structured suffix with the `yang-data` subtype, letting the server parse the payload against the YANG schema rather than treating it as generic JSON.

• ✗

  application/json

  Why it's wrong here

  RESTCONF requires the Content-Type header to identify the request body's encoding as application/yang-data+json, not the generic application/json media type. It is tempting because application/json is the standard JSON media type for most REST APIs, but RESTCONF mandates the YANG-specific type.

• ✗

  text/json

  Why it's wrong here

  RESTCONF requires the media type application/yang-data+json, which identifies the YANG-modelled payload; text/json is a generic type that RESTCONF servers reject. It tempts because text/json appears in ad-hoc APIs, and would be acceptable only where no YANG data model governs the representation.

• ✗

  application/xml

  Why it's wrong here

  RESTCONF uses the Content-Type header to declare the request body's media type, and JSON encoding requires application/yang-data+json, not application/xml. The XML variant, application/yang-data+xml, is the correct choice when a client sends XML-encoded YANG data instead of JSON.

Go deeper

Related to this question