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.

• ✗

  PUT

  Why it's wrong here

  PUT replaces the entire target resource, so calling it on the network-device collection would overwrite device data rather than return it. It is tempting because PUT does address a specific URI, but it suits creating or fully updating a known resource, not reading a list.

• ✗

  DELETE

  Why it's wrong here

  DELETE removes the identified resource and returns no device list; issuing it against the network-device collection would attempt to delete devices rather than read them. DELETE is correct when decommissioning a specific device by ID, whereas retrieving a collection requires a safe, idempotent read method.

• ✓

  GET

  Why this is correct

  GET retrieves a representation of the network-device collection without modifying server state, matching the read-only intent of listing devices. POST would create resources, PUT would replace them, and DELETE would remove them, none of which fit a retrieval request.

• ✗

  POST

  Why it's wrong here

  POST submits a body to create a resource or trigger an action, so it does not perform a simple collection read and may create or modify data. POST fits creating a device or running an intent operation, but listing existing network devices is a retrieval that should use a safe read method.

Go deeper

Related to this question