Question 650
The deployment team is preparing a sign-off for: An automation triggers a configuration push to the wrong folder whenever a branch name contains a common prefix. Which mistaken assumption should be rejected before approval?
Explanation
Correct Answer
The risky assumption is matching deployment scope through an ambiguous partial display name for a privileged action. In this particular incident, an automation triggers a configuration push to the wrong folder whenever a branch name contains a common prefix. The safer path is to review the automation's target selectors, folder identifiers and authorization before deployment and then, when verified, to use stable unique folder/device identifiers and verify targets prior to performing the push. The risk statement matters because it would obscure the true mechanism, broaden permissions, or falsely certify that the required outcome had been achieved.
Incorrect Answers
Blindly replacing the shared configuration with an older local copy during concurrent changes. The check concerns blindly replacing the shared configuration with an older local copy during concurrent changes, not confirming that matching deployment scope through an ambiguous partial display name for a privileged action.
Reporting a successful schedule trigger as proof that the underlying push completed. This assesses reporting a successful schedule trigger as proof that the underlying push completed; it does not determine the reported condition—an automation triggers a configuration push to the wrong folder whenever a branch name contains a common prefix.
Assuming variables with the same name mean the same value regardless of configuration scope. The case-specific requirement is confirming that matching deployment scope through an ambiguous partial display name for a privileged action, which that option does not establish.