Question 240
To prevent recurrence of this provider network issue: A network operator attempts to PATCH a YANG counter marked `config false`, then blames access control when the edit is rejected. Which control should be retained?
Explanation
Correct Answer
Inspect writable-state metadata when generating automation forms from YANG models. This helps prevent recurrence of the issue: A network operator attempts to PATCH a YANG counter marked `config false`, then blames access control when the edit is rejected. Acceptance evidence should be: Counter retrieval succeeds and a controlled mutation remains rejected by schema or datastore rules.
Incorrect Answers
Pin model versions and retain schema-validation fixtures during integration upgrades. That is a sensible control for ANOTHER scenario: Two providers exchange YANG model payloads that use identical local leaf names but different module namespaces, so parsing associates traffic counters with the wrong schema. It is less targeted to this issue than: Inspect writable-state metadata when generating automation forms from YANG models.
Test list-key encoding and cross-interface isolation for every API client. That is a sensible control for ANOTHER scenario: A YANG list declares an interface name as its key but a RESTCONF update sends a request to the list root without an instance identifier, modifying the wrong scope. It is less targeted to this issue than: Inspect writable-state metadata when generating automation forms from YANG models.
Require read-before-write or idempotency controls on mutating API workflows. That is a sensible control for ANOTHER scenario: A script uses an unscoped POST endpoint and accidentally creates multiple static routes when its retry logic repeats a successful but slow request. It is less targeted to this issue than: Inspect writable-state metadata when generating automation forms from YANG models.