CompTIA Cloud+ (CV0-004)TroubleshootingEasy
A cloud administrator is investigating a sudden increase in latency and packet loss between virtual machines (VMs) located in different subnets within the same Virtual Private Cloud (VPC). Network monitoring tools show no spikes in CPU or memory utilization on the VMs themselves. What is the MOST likely cause of this issue?
- AMisconfigured network ACLs blocking inter-subnet traffic.
- BOutdated operating system patches on the affected VMs.
- CInsufficient VM instance types for the current workload.
- DCongestion on the VPC's virtual network gateway.
Show answer & explanationAnswer & explanation
Correct answer: D. Congestion on the VPC's virtual network gateway.
Increased latency and packet loss between subnets in the same VPC, without VM resource issues, often points to a bottleneck at the network's central point, which is the virtual network gateway responsible for routing this traffic.
Why the other options are wrong
- A. Misconfigured network ACLs would likely block traffic entirely, not just cause increased latency and packet loss.
- B. Outdated OS patches are unlikely to cause general inter-subnet network performance issues without other symptoms like service crashes.
- C. VM instance type issues typically manifest as high CPU/memory, not just network latency between subnets.
Virtual Network Gateway Congestion
A bottleneck at the central routing component within a cloud VPC that can lead to increased latency and packet loss for traffic between different subnets or to external networks.
- Handles routing for inter-subnet and external VPC traffic.
- Can become a bottleneck under heavy network load.
- Symptoms include increased latency and packet loss across the network.
Memory trick: VPC Gate is a Traffic Cop; if it's jammed, everyone's slow.