Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Nutanix Exam NCP-MCI Topic 5 Question 18 Discussion

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

Refer to the exhibit.

An administrator is adding a new node to a cluster. The node has been imaged to the same versions of AHV and AOS that the cluster running, configured with appropriate IP addresses, and br0-up has been configured the same the existing uplink bonds

When attempting to add the node to the cluster with the Expand Cluster function in Prism , the cluster is unable to find the new node.

Based on the above output from the new node, what is most likely the cause of this issue?

Show Suggested Answer Hide Answer
Suggested Answer: B

The task that needs to be performed when time is not synchronizing properly after deploying a cluster is NTP configuration. In the Nutanix Multicloud Infrastructure (NCP-MCI) 6.5, Network Time Protocol (NTP) is used to synchronize the system time across all the nodes in a cluster. If the time is not synchronizing properly, it indicates that there might be an issue with the NTP configuration. Therefore, checking and correcting the NTP configuration would be the appropriate action to resolve this issue. The other options like DNS configuration, HA configuration, and SMTP configuration are not directly related to time synchronization in a cluster.


Contribute your Thoughts:

Carli
2 months ago
Wait, what if the answer is the ports on the upstream switch are not configured for LACP? That would be a real 'switch' up! Haha, get it?
upvoted 0 times
Shakira
7 days ago
User 3: Let's check the switch configuration to see if that's the issue.
upvoted 0 times
...
Gertude
9 days ago
User 2: It could be, but it might also be something else causing the problem.
upvoted 0 times
...
Lazaro
16 days ago
User 1: Maybe that's the issue, the ports on the switch are not configured for LACP.
upvoted 0 times
...
...
Delila
2 months ago
Ah, the old 'different VLAN' trick! Classic Nutanix exam question. Time to brush up on my network configuration skills.
upvoted 0 times
...
Nobuko
2 months ago
I'm going with option D. The LACP configuration must be completed after cluster expansion. It's like trying to put the cart before the horse!
upvoted 0 times
Elina
2 days ago
It could also be that there is a firewall blocking the discovery traffic from the tlu.
upvoted 0 times
...
Madonna
3 days ago
Maybe the ports on the upstream switch are not configured for LACP.
upvoted 0 times
...
Rima
28 days ago
I agree, the LACP configuration should be completed after cluster expansion.
upvoted 0 times
...
Margart
1 months ago
I think option D is the most likely cause of the issue.
upvoted 0 times
...
...
Josue
2 months ago
Hmm, I'm not sure. Could it be the firewall blocking the discovery traffic? Or maybe the LACP configuration needs to be done after expansion?
upvoted 0 times
...
Lavonda
2 months ago
The answer is B. The existing and the expansion node are on different VLANs. That would prevent the cluster from discovering the new node.
upvoted 0 times
Rebecka
1 months ago
B) The existing and the expansion node are on different VLANs.
upvoted 0 times
...
Candida
1 months ago
A) The ports on the upstream switch are not configured for LACP.
upvoted 0 times
...
...
Tyisha
2 months ago
I believe the firewall could also be blocking the discovery traffic.
upvoted 0 times
...
Veta
2 months ago
I agree with Jeannetta, it could be the ports on the switch not configured for LACP.
upvoted 0 times
...
Jeannetta
3 months ago
I think the issue might be with the LACP configuration.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77