Question 700
An application requires a supported vendor-specific setting absent from the blueprint's default rendered commands. Which controlled change best addresses the described requirement?
Explanation
Correct Answer
This action addresses the stated defect: create a narrowly scoped reviewed configlet and validate the resulting generated device configuration. The underlying constraint is that configlets can extend generated device configuration through controlled, scoped supplemental configuration. Verify rather than assume success: confirm only intended device interfaces or nodes receive the supplemental settings without conflicting commands.
Incorrect Answers
The option “Narrow configlet selectors or tags and stage a validated corrective revision” is useful in a different setting: An engineer discovers that a supplemental configuration template was bound to an overly broad tag. The case being tested is: An application requires a supported vendor-specific setting absent from the blueprint's default rendered commands. Create a narrowly scoped reviewed configlet and validate the resulting generated device configuration. The most relevant correction is “Create a narrowly scoped reviewed configlet and validate the resulting generated device configuration”.
That choice—“Update the approved property set and stage dependent configurations through normal blueprint review”—addresses this other problem: A blueprint operator maintains repeated data center operational variables that should have a single validated definition. Here the scenario is: An application requires a supported vendor-specific setting absent from the blueprint's default rendered commands. Create a narrowly scoped reviewed configlet and validate the resulting generated device configuration. The most relevant correction is “Create a narrowly scoped reviewed configlet and validate the resulting generated device configuration”.
“Investigate unexpected changes using the appropriate generated-config view and approved override workflow” is associated with a distinct issue: An audit asks why some device commands come from the baseline while others appear from intended virtual-network configuration. By contrast, the actual problem is: An application requires a supported vendor-specific setting absent from the blueprint's default rendered commands. Create a narrowly scoped reviewed configlet and validate the resulting generated device configuration. The most relevant correction is “Create a narrowly scoped reviewed configlet and validate the resulting generated device configuration”.