Question 30
A proprietary monitoring agent needs device-level CLI configuration not generated by standard Apstra intents. Which evidence most directly verifies the intended network outcome?
Explanation
Correct Answer
This directly tests the desired result: confirm only intended device interfaces or nodes receive the supplemental settings without conflicting commands. The decisive investigation is to review supported configlet scope and possible conflicts with generated native configuration. The governing principle is that configlets can extend generated device configuration through controlled, scoped supplemental configuration.
Incorrect Answers
That choice—“Confirm only approved target devices receive the supplemental command after commit”—addresses this other problem: A new configlet unexpectedly adds a command to spine switches when it was intended for a single border leaf. Here the scenario is: A proprietary monitoring agent needs device-level CLI configuration not generated by standard Apstra intents. Configlets can extend generated device configuration through controlled, scoped supplemental configuration. The direct acceptance evidence is “Confirm only intended device interfaces or nodes receive the supplemental settings without conflicting commands”.
The option “Confirm every intended consumer receives the updated value and unrelated devices retain their settings” is useful in a different setting: A team wants to reuse the same approved DNS and NTP settings across multiple racks without editing every switch individually. The case being tested is: A proprietary monitoring agent needs device-level CLI configuration not generated by standard Apstra intents. Configlets can extend generated device configuration through controlled, scoped supplemental configuration. The direct acceptance evidence is “Confirm only intended device interfaces or nodes receive the supplemental settings without conflicting commands”.
“Confirm the selection contains exactly the intended leafs and excludes similarly named devices elsewhere” is relevant to a different condition: An automation needs to find only leafs assigned to a particular rack, but a free-text search returns similarly named unrelated devices. The stated question instead concerns: A proprietary monitoring agent needs device-level CLI configuration not generated by standard Apstra intents. Configlets can extend generated device configuration through controlled, scoped supplemental configuration. The direct acceptance evidence is “Confirm only intended device interfaces or nodes receive the supplemental settings without conflicting commands”.