Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Nutanix Exam NCP-MCI Topic 2 Question 7 Discussion

Actual exam question for Nutanix's NCP-MCI exam
Question #: 7
Topic #: 2
[All NCP-MCI Questions]

Refer to Exhibit:

The Update Source for LCM has been configured as shown in the exhibit. Inventory is failing consistently.

What is the likely cause of this issue?

Show Suggested Answer Hide Answer
Suggested Answer: A, B

According to the Nutanix Volumes - Recommendations And Best Practices web search result3, two actions that the administrator should take when designing the Volume Group are:

Distribute workload across multiple virtual disks: Use multiple disks rather than a single large disk for an application. Consider using a minimum of one disk per Nutanix node to distribute the workload across all nodes in a cluster. Multiple disks per Nutanix node may also improve an application's performance. For performance-intensive environments, we recommend using between four and eight disks per CVM for a given workload.

Enable RSS (Receive Side Scaling): Receive-side scaling (RSS) allows the system to use multiple CPUs for network activity. With RSS enabled, multiple CPU cores process network traffic, preventing a single CPU core from becoming a bottleneck. Enabling RSS within hosts can be beneficial for heavy iSCSI workloads. For VMs running in ESXi environments, RSS requires VMXNET3 VNICs. For Hyper-V environments, enable VMQ to take full advantage of Virtual RSS.


Contribute your Thoughts:

Misty
1 days ago
Hmm, I'd check the firewall settings first. Blocking port 433 seems like the most likely culprit here. That's the standard HTTPS port, right?
upvoted 0 times
...
Dominga
9 days ago
I believe it could also be due to the license assigned to the cluster expiring.
upvoted 0 times
...
Dianne
10 days ago
I agree with Therese, port 433 being blocked makes sense.
upvoted 0 times
...
Therese
14 days ago
I think the likely cause is port 433 being blocked.
upvoted 0 times
...

Save Cancel