Question 690
A team wants to reuse the same approved DNS and NTP settings across multiple racks without editing every switch individually. Which evidence most directly verifies the intended network outcome?
Explanation
Correct Answer
This directly tests the desired result: confirm every intended consumer receives the updated value and unrelated devices retain their settings. The decisive investigation is to inspect property-set values, consumers and intended scope before updating a shared parameter. The governing principle is that Apstra property sets can centralize reusable named parameters referenced by supported configuration templates.
Incorrect Answers
“Confirm only intended device interfaces or nodes receive the supplemental settings without conflicting commands” is associated with a distinct issue: A proprietary monitoring agent needs device-level CLI configuration not generated by standard Apstra intents. By contrast, the actual problem is: A team wants to reuse the same approved DNS and NTP settings across multiple racks without editing every switch individually. Apstra property sets can centralize reusable named parameters referenced by supported configuration templates. The direct acceptance evidence is “Confirm every intended consumer receives the updated value and unrelated devices retain their settings”.
The option “Confirm only approved target devices receive the supplemental command after commit” is useful in a different setting: A new configlet unexpectedly adds a command to spine switches when it was intended for a single border leaf. The case being tested is: A team wants to reuse the same approved DNS and NTP settings across multiple racks without editing every switch individually. Apstra property sets can centralize reusable named parameters referenced by supported configuration templates. The direct acceptance evidence is “Confirm every intended consumer receives the updated value and unrelated devices retain their settings”.
“Confirm the pending diff no longer includes the bad edit and the active blueprint is unchanged” is relevant to a different condition: A team wants to undo only the last local edit in Staged without reverting the whole network to an older committed state. The stated question instead concerns: A team wants to reuse the same approved DNS and NTP settings across multiple racks without editing every switch individually. Apstra property sets can centralize reusable named parameters referenced by supported configuration templates. The direct acceptance evidence is “Confirm every intended consumer receives the updated value and unrelated devices retain their settings”.