Nutanix NCP-CI-AWS Exam - Topic 3 Question 34 Discussion

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

Question #: 34
Topic #: 3

[All NCP-CI-AWS Questions]

An administrator has created an NC2 cluster on AWS, but the NC2 console has issued this alert:

Which two scenarios could have resulted in the cluster creation failure? (Choose two.)

ABad Terraform (TF) state in provisioning

BInsufficient permissions

CNo available AWS credits

DAWS Quota exceeded/instance limit exceeded

Show Suggested Answer

Suggested Answer: B, D

The error message in the image indicates that the cluster creation failed due to reaching the maximum retries for provisioning cluster nodes. Here are two possible scenarios that could lead to this issue:

Insufficient Permissions (Answer B):

If the AWS user or role used to create the cluster does not have sufficient permissions, it can result in failures during the provisioning process. Proper IAM policies must be attached to ensure that the necessary actions can be performed, such as launching instances, creating VPCs, or managing networking components.

AWS Quota Exceeded/Instance Limit Exceeded (Answer D):

AWS imposes quotas and limits on the number of instances and other resources that can be created within an account. If these quotas are exceeded, new instances cannot be provisioned, causing the cluster creation to fail. This can be resolved by requesting a quota increase from AWS.

Nutanix Knowledge Base Article 9774

AWS Service Quotas

Nutanix NC2 on AWS Documentation

by Rueben at Nov 22, 2025, 10:02 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

In

1 day ago

C seems less likely, but still possible. Credits should be checked first.

upvoted 0 times

...

Elina

6 days ago

I lean towards B and D as well. Permissions and limits are common issues.

upvoted 0 times

...

Jovita

11 days ago

D makes sense. If the quota is exceeded, the cluster won't create.

upvoted 0 times

...

Tracey

17 days ago

I feel like A is a strong contender too. Bad TF state can really cause problems.

upvoted 0 times

...

Magdalene

22 days ago

I agree, B is definitely a possibility. But C could also be an issue.

upvoted 0 times

...

Marylin

27 days ago

I think B and D are likely causes. Permissions can mess everything up.

upvoted 0 times

...

Roxane

2 months ago

Yeah, quotas can really mess things up, happened to me before!

upvoted 0 times

...

Eliseo

2 months ago

I disagree, I’ve never had issues with permissions causing failures.

upvoted 0 times

...

Blossom

2 months ago

I think A could also be a problem, bad TF state is tricky!

upvoted 0 times

...

Portia

2 months ago

Definitely B and D, those are common issues.

upvoted 0 times

...

Simona

2 months ago

Haha, I bet the admin was trying to provision the cluster using their personal AWS account with no credits. C) No available AWS credits, for sure!

upvoted 0 times

...

Hollis

2 months ago

A) Bad Terraform (TF) state in provisioning? Nah, that's too obvious. I bet it's a combination of B) and D).

upvoted 0 times

...

Theodora

3 months ago

D) AWS Quota exceeded/instance limit exceeded seems like the most likely culprit. Those pesky AWS limits always trip us up!

upvoted 0 times

...

Carisa

3 months ago

B) Insufficient permissions is definitely the issue here. The admin must have forgotten to grant the necessary IAM permissions.

upvoted 0 times

...

Emilio

3 months ago

I vaguely recall something about AWS credits, but I'm not sure if C is relevant here. It might be a factor, but I can't remember clearly.

upvoted 0 times

...

Corinne

3 months ago

I feel like AWS quotas are something we covered a lot. D seems likely since exceeding limits is a common pitfall.

upvoted 0 times

...

Clemencia

3 months ago

I've seen this kind of issue before. My money's on the AWS quota being the culprit. I'll check the instance limits and see if I can find any other relevant information in the console.

upvoted 0 times

...

Elvera

3 months ago

I'm a bit confused here. Could it be a combination of issues, like insufficient permissions and an exceeded quota? I'll need to carefully examine the cluster creation logs and the account settings.

upvoted 0 times

...

Josephine

4 months ago

I'm not entirely sure, but I think insufficient permissions could also cause a failure. It seems like a common issue in practice questions.

upvoted 0 times

...

Bulah

4 months ago

Ah, this is a tough one. My first guess would be the Terraform state, but the AWS quota could also be a factor. I'll need to investigate both possibilities.

upvoted 0 times

...

Tu

4 months ago

I remember we discussed how bad Terraform state can lead to provisioning issues, so A could definitely be a reason.

upvoted 0 times

...

Melodie

4 months ago

Wait, are you saying no AWS credits can stop a cluster? That's wild!

upvoted 0 times

...

Broderick

5 months ago

Hmm, this looks tricky. I'm not sure if it's a problem with the Terraform state or the AWS credits. I'll need to review the cluster creation process and the account details.

upvoted 0 times

...

Audra

5 months ago

I think the issue could be related to insufficient permissions or an exceeded AWS quota. I'll need to double-check the IAM role and instance limits for the account.

upvoted 0 times

Janey

4 months ago

I agree, permissions can be tricky.

upvoted 0 times

...