A new service was introduced to support global users. Some offices connect by name without issues, while others fail with connection errors. The network team confirms there are no network blocks preventing traffic from reaching the service endpoints, and security group rules are consistent. Which cause is leading to these failures?
Locations are using stale name references that do not align with the new service
An encryption certificate mismatch is blocking requests
A firewall rule is discarding traffic from particular regions
A vantage point-based routing policy is configured for limited offices
Offices are relying on stale name references that do not match the new service, leading to connection problems. When these references are updated, all offices can access the service. An encryption certificate mismatch usually triggers a warning about trust but does not block specific regions selectively. A vantage point-based routing policy typically directs traffic to regional servers, but it would not target a small number of offices unless it was configured for these offices alone. Firewall rules usually block traffic at a broader level, not for a limited set of offices.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
Why do stale name references cause connection issues?
Open an interactive chat with Bash
How can a DNS cache be cleared on devices or servers?
Open an interactive chat with Bash
What are some ways to prevent stale DNS records from causing issues in future deployments?