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 NCS-Core Topic 4 Question 69 Discussion

Actual exam question for Nutanix's Nutanix Certified Services Core Infrastructure Professional exam
Question #: 69
Topic #: 4
[All Nutanix Certified Services Core Infrastructure Professional Questions]

A consultant is unable to ping the CVM from the hypervisor using the external interface. The customer's network is configured with the 10.3.12.0/24 subnet without VLAN tagging. The CVM and hypervisor are using the same address space.

What is causing this issue?

Show Suggested Answer Hide Answer
Suggested Answer: B

If a consultant is unable to ping the CVM from the hypervisor using the external interface in a network without VLAN tagging, and both are using the same subnet, the issue might be related to an incorrect default gateway configuration. The default gateway must be correctly set to ensure proper routing of packets between the CVM and the hypervisor. An incorrect gateway can prevent successful communication even if both devices are on the same subnet. Reference:

Nutanix University - NCS-Core 6.8 Learning Path

The Nutanix Bible, Networking chapter (https://www.nutanixbible.com/)


Contribute your Thoughts:

Tequila
3 days ago
Ooh, I bet the 1GbE and 10GbE NICs haven't been separated. That's like trying to fit a square peg in a round hole, am I right?
upvoted 0 times
...
Leila
8 days ago
Hold on, did someone forget to pay the internet bill? The CVM and hypervisor only communicating over 192.168.5.0/24 sounds like a classic case of network isolation.
upvoted 0 times
...
Margret
14 days ago
Hmm, the switch being trunked without a native VLAN sounds like the culprit to me. No VLAN tagging means the packets might be getting dropped.
upvoted 0 times
Rasheeda
4 days ago
User 1: I think the switch being trunked without a native VLAN is causing the issue.
upvoted 0 times
...
...
Ernestine
19 days ago
Actually, I believe the switch being trunked without a native VLAN could also be causing the issue.
upvoted 0 times
...
Bettye
21 days ago
I agree with Felicidad, the default gateway could be the problem.
upvoted 0 times
...
Levi
25 days ago
I'm not sure about that. The question clearly states that the CVM and hypervisor are using the same address space, so the default gateway shouldn't be the problem.
upvoted 0 times
Argelia
3 hours ago
C) The switch is trunked without a native VLAN.
upvoted 0 times
...
Jillian
3 days ago
B) The default gateway is incorrect.
upvoted 0 times
...
Hortencia
5 days ago
A) The 1GbE and 10GbE NICs have not been separated.
upvoted 0 times
...
...
Michal
28 days ago
The default gateway is definitely the issue here. The 10.3.12.0/24 subnet needs a proper gateway to communicate beyond the local network.
upvoted 0 times
Dallas
13 days ago
B) The default gateway is incorrect.
upvoted 0 times
...
Michel
22 days ago
A) The 1GbE and 10GbE NICs have not been separated.
upvoted 0 times
...
...
Felicidad
1 months ago
I think the issue might be with the default gateway.
upvoted 0 times
...

Save Cancel