An automation performs the following on a monthly basis: - Disable accounts that have not logged on in the last 60 days - Remove firewall rules with zero hits in the last 30 days - Remove DNS entries

Accounts disabled after 60 days of inactivity would affect authentication, but service accounts used for scheduled replication are typically kept active through automated processes and would not go 60 days without activity.

Quarterly replication failover tests generate firewall traffic only once every roughly 90 days, so the associated firewall rules will consistently show zero hits within the 30-day measurement window used by the automation. After six weeks of the automation running, those rules are deleted, and when the quarterly failover test executes, the required network paths are blocked at the firewall, causing the test to fail. This is a direct conflict between a short-window cleanup policy and a legitimate but infrequent periodic workflow.

DNS entries are removed only if not updated in 60 days, and static replication failover DNS records are rarely modified - a missing DNS entry would produce a name resolution error rather than a firewall-level replication block.

Archiving logs older than 30 days affects only historical records and has no impact on the network connectivity, credentials, or replication protocols required for failover test execution.