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.

• ✗

  <lock>

  Why it's wrong here

  Locking a datastore prevents concurrent edits during a transaction; it changes no configuration value itself. It is tempting because editing the hostname safely often involves locking the running datastore first, but the actual modification requires <edit-config> with the hostname leaf.

• ✗

  <copy-config>

  Why it's wrong here

  <copy-config> replaces an entire datastore with another's contents, overwriting the full configuration rather than altering one leaf. It is tempting when cloning configurations between devices, but changing a single hostname requires <edit-config> with a targeted hostname element.

• ✓

  <edit-config>

  Why this is correct

  The `<edit-config>` operation writes configuration changes into the running datastore, which is exactly what altering a hostname requires. It targets the specified configuration node and applies the new value, satisfying NETCONF's requirement for modifying device configuration rather than merely retrieving state with `<get-config>`.

• ✗

  <get-config>

  Why it's wrong here

  <get-config> retrieves configuration data from a datastore; it performs no write, so the hostname stays unchanged. It is tempting because engineers verify current settings before editing, and retrieval is the natural first step, yet the change itself demands <edit-config> targeting the hostname node.

Go deeper

Related to this question