Question 610
The deployment team is preparing a sign-off for: A new branch firewall appears in inventory but it does not receive the expected shared inspection rule. Which mistaken assumption should be rejected before approval?
Explanation
Correct Answer
The risky assumption is assuming belonging to the same tenant means every device shares identical policies without folder scope. In this particular incident, a new branch firewall appears in inventory but it does not receive the expected shared inspection rule. The safer path is to inspect its folder membership, associated snippets and current device management state and then, when verified, to associate the firewall with the correct configuration scope and push the approved shared rule. 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
Using a global one-click push for an untested rule simply because configuration is centrally managed. The check concerns using a global one-click push for an untested rule simply because configuration is centrally managed, not confirming that assuming belonging to the same tenant means every device shares identical policies without folder scope.
Treating a saved candidate edit in Strata Cloud Manager as proof of deployed enforcement. This assesses treating a saved candidate edit in Strata Cloud Manager as proof of deployed enforcement; it does not determine the reported condition—a new branch firewall appears in inventory but it does not receive the expected shared inspection rule.
Assuming a visual dashboard screenshot is a reliable backup of the complete deployed policy. The case-specific requirement is confirming that assuming belonging to the same tenant means every device shares identical policies without folder scope, which that option does not establish.