nerdexam
CompTIA

CV0-002 · Question #306

IaaS users are reporting longer than expected wait times when accessing the virtual file repository. There are more than 2TB of free disk space, and vCPU and vRAM do not reach more than 75% utilizatio

The correct answer is B. Access the cloud services portal and check the amount of CPU and RAM on the host machine.. When IaaS users experience slow access to a virtual file repository despite sufficient virtual disk space, vCPU, and vRAM, the administrator should investigate the underlying host machine's resources.

Troubleshooting

Question

IaaS users are reporting longer than expected wait times when accessing the virtual file repository. There are more than 2TB of free disk space, and vCPU and vRAM do not reach more than 75% utilization. In which of the following ways should the cloud systems administrator analyze this issue?

Options

  • AAccess the cloud services portal and increase the amount of available disk space by 25%.
  • BAccess the cloud services portal and check the amount of CPU and RAM on the host machine.
  • CAccess the cloud services portal and look at the historical performance numbers.
  • DAccess the cloud services portal and check the security log for access denied requests.

How the community answered

(25 responses)
  • A
    8% (2)
  • B
    76% (19)
  • C
    4% (1)
  • D
    12% (3)

Why each option

When IaaS users experience slow access to a virtual file repository despite sufficient virtual disk space, vCPU, and vRAM, the administrator should investigate the underlying host machine's resources.

AAccess the cloud services portal and increase the amount of available disk space by 25%.

The question explicitly states there is 'more than 2TB of free disk space,' indicating that insufficient disk space is not the cause of the performance issue.

BAccess the cloud services portal and check the amount of CPU and RAM on the host machine.Correct

Since the VM's reported vCPU and vRAM utilization are below 75% and disk space is plentiful, the bottleneck might be at the physical host level. Checking the host machine's actual CPU and RAM utilization will help determine if the physical resources allocated to the virtual machine or shared by other VMs on the same host are constrained, leading to performance issues.

CAccess the cloud services portal and look at the historical performance numbers.

While looking at historical performance numbers can be useful for trend analysis, the immediate priority is to identify the current bottleneck, which in this case points to the physical host resources given the VM's reported health.

DAccess the cloud services portal and check the security log for access denied requests.

Slow access times are a performance issue, not typically related to access denied requests, which would manifest as an inability to access rather than slow access.

Concept tested: IaaS performance troubleshooting - host resources

Source: https://learn.microsoft.com/en-us/azure/virtual-machines/monitor-vm-performance

Topics

#Performance troubleshooting#IaaS resource monitoring#Virtualization bottlenecks

Community Discussion

No community discussion yet for this question.

Full CV0-002 Practice