A platform team deploys Bandwidth Control and firewall policy changes through an API.

Option A adds the missing observability control before a high-impact automated change. Validating monitoring subscriptions helps ensure that telemetry will be collected during the rollout, while exporting pre-change ZDX and Firewall Insights baselines creates a reference for detecting latency, loss, application, and policy-behavior regressions. Zscaler’s ZDX Reference Architecture recommends controlled deployment and validation, and the Internet and SaaS performance troubleshooting runbook uses ZDX and Firewall Insights as complementary evidence sources. Monthly aggregation is too delayed for rollout protection. Longer API-token lifetimes address authentication continuity, not missing monitoring data or application performance. Running automation weekly merely reduces deployment frequency; it does not prove telemetry coverage or provide a reliable before-and-after comparison for each policy change.

================