Nutanix NCP-MCI Exam - Topic 5 Question 18 Discussion

Actual exam question for Nutanix's NCP-MCI exam

Question #: 18
Topic #: 5

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?

AThe ports on the upstream switch are not configured for LACP.

BThe existing and the expansion node are on different VLANs.

CThere is a firewall blocking the discovery traffic from the tlu

DLACP configuration must be completed after cluster expansion

Show Suggested 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.

by Chanel at Sep 09, 2024, 07:18 PM

Limited Time Offer

25%

Off

Get Premium NCP-MCI Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Suzi

4 months ago

Really? I thought LACP was done before expansion.

upvoted 0 times

...

Quiana

5 months ago

I agree, LACP is crucial for this setup.

upvoted 0 times

...

Sharika

5 months ago

Wait, are we sure there's no firewall blocking?

upvoted 0 times

...

Basilia

5 months ago

I think it's definitely the LACP config.

upvoted 0 times

...

Selene

5 months ago

Sounds like a VLAN issue to me.

upvoted 0 times

...

Reuben

6 months ago

I thought LACP needed to be set up before adding nodes, but I’m not confident if that’s the right answer for this question.

upvoted 0 times

...

Tamesha

6 months ago

I feel like I read that firewalls can block discovery traffic, but I can't recall if that applies to this scenario.

upvoted 0 times

...

Maricela

6 months ago

I think I came across a similar question where VLAN mismatches caused issues. Could that be the problem here too?

upvoted 0 times

...

Shawnta

6 months ago

I remember something about LACP configurations being crucial for cluster expansions, but I'm not entirely sure if it's the upstream switch settings or something else.

upvoted 0 times

...

Gladis

6 months ago

Alright, time to put on my troubleshooting hat. I'll start by verifying the LACP configuration on the upstream switch and make sure the VLANs are set up correctly.

upvoted 0 times

...

Alaine

6 months ago

I'm a bit confused by this one. I'll need to review the details and try to understand the network setup better before I can make a decision.

upvoted 0 times

...

Hailey

6 months ago

Ah, I think I know what the problem is. The firewall is probably blocking the discovery traffic, so I'll need to check the firewall rules.

upvoted 0 times

...

Jeannine

6 months ago

Okay, let's see here. The node is configured correctly, so it's likely an issue with the network setup. I'll need to double-check the VLAN and LACP configurations.

upvoted 0 times

...

Ammie

6 months ago

Hmm, this one seems tricky. I'll need to carefully review the information provided and think through the possible causes.

upvoted 0 times

...

Nicholle

6 months ago

Okay, let's see. Jian was acquiring feeds from sources like honeynets, P2P monitoring, and application logs. That sounds like he was gathering external intelligence feeds, so I'll go with option B.

upvoted 0 times

...