Question 190
The deployment team is preparing a sign-off for: A configuration push succeeds for two firewalls but fails for a smaller model whose supported address-object count is exceeded. Which mistaken assumption should be rejected before approval?
Explanation
Correct Answer
The risky assumption is assuming a successful push on a large appliance proves the same configuration fits every model. In this particular incident, a configuration push succeeds for two firewalls but fails for a smaller model whose supported address-object count is exceeded. The safer path is to inspect per-device push jobs, platform resource limits and the rejected object quantity and then, when verified, to reduce or restructure object use within platform-supported limits before targeting that device. 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
Treating a tenant-level successful job label as proof all possible devices were targeted. The check concerns treating a tenant-level successful job label as proof all possible devices were targeted, not confirming that assuming a successful push on a large appliance proves the same configuration fits every model.
Force-unlocking configuration while a legitimate colleague is still editing without checking ownership. This assesses force-unlocking configuration while a legitimate colleague is still editing without checking ownership; it does not determine the reported condition—a configuration push succeeds for two firewalls but fails for a smaller model whose supported address-object count is exceeded.
Deleting an object before checking all policies that reference it. The case-specific requirement is confirming that assuming a successful push on a large appliance proves the same configuration fits every model, which that option does not establish.