Nutanix NCP-CI-Azure Exam - Topic 2 Question 19 Discussion

Actual exam question for Nutanix's NCP-CI-Azure exam

Question #: 19
Topic #: 2

An administrator is deploying an NC2 cluster in Azure and observes on NC2 console that nodes will not progress and continue in a Booting state.

What is the most likely cause for the node not continuing to deploy?

AThe Azure account does not have an active subscription.

BAn Azure Support case must first be submitted for allowlisting the Azure subscription.

CThe subscription has not been validated to be allowlisted by Microsoft.

DA private DNS server is being used that is not reachable.

Show Suggested Answer

Suggested Answer: C

Azure Subscription Validation: When deploying an NC2 cluster, the Azure subscription must be validated and allowlisted by Microsoft. This is a crucial step to ensure that the necessary permissions and configurations are set up for the deployment.

Booting State Issue: If the nodes are stuck in the Booting state, it often indicates that the subscription has not been properly validated and allowlisted. This prevents the deployment from progressing as required resources and permissions are not fully accessible.

Checking Allowlisting Status: Administrators should verify that their subscription has been allowlisted by contacting Azure support or checking the status through the Azure portal.

Resolution: Once the subscription is validated and allowlisted by Microsoft, the deployment should proceed without the nodes getting stuck in the Booting state.

Nutanix NC2 on Azure Documentation

Azure Subscription Management

by Marsha at Nov 21, 2025, 12:50 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Katy

6 hours ago

Wait, are we sure it's not just an active subscription problem?

upvoted 0 times

...

Chun

5 days ago

I think it's definitely about the subscription not being validated.

upvoted 0 times

...

Edelmira

11 days ago

Sounds like a DNS issue to me.

upvoted 0 times

...

Georgeanna

16 days ago

D) A private DNS server is being used that is not reachable. Classic Azure shenanigans!

upvoted 0 times

...

Zona

21 days ago

A) The Azure account does not have an active subscription. Rookie mistake, am I right?

upvoted 0 times

...

An

26 days ago

Hmm, I'm going with B) An Azure Support case must first be submitted for allowlisting the Azure subscription. Gotta love those bureaucratic hoops!

upvoted 0 times

...

Denna

1 month ago

D) A private DNS server is being used that is not reachable.

upvoted 0 times

...

Iluminada

1 month ago

C) The subscription has not been validated to be allowlisted by Microsoft.

upvoted 0 times

...

Amie

1 month ago

I feel like D could be a factor too, especially if the nodes need to reach a DNS server during boot.

upvoted 0 times

...

Dudley

2 months ago

I'm not entirely sure, but C sounds plausible since it mentions validation by Microsoft, which could definitely hold things up.

upvoted 0 times

...

Lucy

2 months ago

I've seen this kind of issue before with Azure deployments. My money's on option D - a private DNS server that's not reachable. That would definitely cause the nodes to get stuck in the Booting state. I'm pretty confident that's the right answer here.

upvoted 0 times

...

Tom

2 months ago

Okay, let's think this through. The key information here is that the nodes are stuck in a Booting state, which suggests a configuration or connectivity issue. Based on the options, I'm leaning towards either C or D as the most likely cause. I'll need to double-check my understanding of Azure subscription validation and private DNS servers to make the best guess.

upvoted 0 times

...

Felicitas

2 months ago

I think I came across a similar question where allowlisting was mentioned, so B could be relevant here.

upvoted 0 times

...

Reuben

2 months ago

I remember something about subscription issues causing deployment problems, so A might be a possibility.

upvoted 0 times

...

Edward

3 months ago

I agree, C makes sense. Validation issues can cause delays.

upvoted 0 times

...

Kallie

3 months ago

This looks like a tricky one, but I think I've got a strategy. I'll start by eliminating the options that seem less likely, like A and B. Then I'll focus on C and D, trying to understand the implications of each in the context of an NC2 cluster deployment. Hopefully, that will lead me to the most likely cause.

upvoted 0 times

...

Catalina

3 months ago

Hmm, this is a tough one. I think it might have something to do with the Azure subscription, but I'm not sure which option is the most likely cause. I'll need to review the information about allowlisting and private DNS servers to see if I can figure this out.

upvoted 0 times

...

Tracey

3 months ago

I'm not too sure about this one. The question seems a bit tricky, and I'm not familiar with the NC2 cluster in Azure. I'll have to read through the options carefully and try to eliminate the ones that don't seem plausible.

upvoted 0 times

Olga

2 months ago

I think it might be option A. No active subscription could definitely cause issues.

upvoted 0 times

...