CV0-003 · Question #284
Worldwide users from an organization are experiencing intermittent access to a global cloud application. The cloud provider availability dashboard shows all resource availability has been 100% in…
The correct answer is D. Evaluate the DNS to ensure all configurations are correct. Intermittent global access with no reported outages or resource issues most commonly points to DNS misconfiguration affecting hostname resolution for users worldwide.
Question
Worldwide users from an organization are experiencing intermittent access to a global cloud application. The cloud provider availability dashboard shows all resource availability has been 100% in the last two weeks. No network outages have been reported. Which of the following should the organization's administrator do BEFORE calling the cloud provider?
Options
- ACheck the firewall rules on the headquarters site.
- BRestart the application and applicable services.
- CAllow all traffic at the cloud provider side from any private IP address.
- DEvaluate the DNS to ensure all configurations are correct.
How the community answered
(36 responses)- A8% (3)
- B11% (4)
- C3% (1)
- D78% (28)
Why each option
Intermittent global access with no reported outages or resource issues most commonly points to DNS misconfiguration affecting hostname resolution for users worldwide.
Firewall rules at headquarters would only affect users at that site, not worldwide users experiencing intermittent failures.
Restarting the application is premature and treats a symptom rather than identifying a root cause, especially when provider resources show 100% availability.
Allowing all traffic from any private IP is a security risk and irrelevant because no network outage has been reported and private IPs do not cross the public internet.
DNS is the foundational service that translates application hostnames into routable addresses; a misconfiguration such as incorrect A/CNAME records, TTL conflicts, or replication failures would cause intermittent, geography-dependent access failures that never appear on a cloud provider availability dashboard. Evaluating DNS first rules out a client-side or infrastructure name resolution issue before engaging the provider.
Concept tested: DNS troubleshooting for global cloud application access
Source: https://learn.microsoft.com/en-us/azure/dns/dns-troubleshoot
Topics
Community Discussion
No community discussion yet for this question.