New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Nutanix NCP-CI-AWS Exam - Topic 4 Question 19 Discussion

Actual exam question for Nutanix's NCP-CI-AWS exam
Question #: 19
Topic #: 4
[All NCP-CI-AWS Questions]

An administrator has deployed an NC2 cluster in AWS.

The following configuration decisions were made:

Created a new VPC from the NC2 console as part of the deployment

Selected the Public option for prism access policy

Host type selected was i13en,metal

The administrator now has a goal of provision public internet access to a user VM (UVM),web-1, on the Nutanix cluster. The admin can access Prism Element via the public DNS of the Auto-created load balancer.

The administrator tries to create another network load balancer for the web server access. After creating the load balancer and registering web-1's IP address as a target, the administrator finds that the health check for the VM target is failing and the DNS returns as NOT Found message in the browser.

Why is the issue happening?

Show Suggested Answer Hide Answer
Suggested Answer: C

When creating an NC2 cluster in AWS, the account used to run the CloudFormation script requires specific permissions to ensure the deployment is successful. The required permissions are:

IAMFullAccess: Provides full access to IAM resources.

AmazonEC2FullAccess: Allows full access to EC2 resources.

AWSCIoudFormationFullAccess: Grants full access to manage AWS CloudFormation stacks.

These permissions are necessary to create, manage, and deploy the required AWS resources for the NC2 cluster.


Nutanix Support & Insights

AWS IAM Documentation

Contribute your Thoughts:

0/2000 characters
Gail
3 months ago
The load balancer might just be taking time to provision.
upvoted 0 times
...
Matilda
3 months ago
I think a public IP is definitely needed for web-1.
upvoted 0 times
...
Krystal
3 months ago
Wait, can you even use a network load balancer for public access?
upvoted 0 times
...
Apolonia
4 months ago
I agree, the inbound rules are probably blocking access.
upvoted 0 times
...
Gene
4 months ago
Sounds like a security group issue to me.
upvoted 0 times
...
Jeannetta
4 months ago
I thought we learned that application load balancers are better for web traffic. Could that be why the network load balancer isn’t working here?
upvoted 0 times
...
Blossom
4 months ago
This seems similar to a practice question we did on load balancers. I wonder if the health check is failing because the UVM isn’t configured correctly in the security group.
upvoted 0 times
...
Jacki
4 months ago
I’m not entirely sure, but I think the load balancer might need a public IP assigned to the VM for it to be reachable from the internet.
upvoted 0 times
...
Latosha
5 months ago
I remember something about security groups being crucial for allowing traffic. Maybe the inbound rules are blocking access to web-1?
upvoted 0 times
...
Starr
5 months ago
This seems straightforward to me. The issue is that the web-1 VM doesn't have a public IP address, so the load balancer can't reach it. I'd recommend assigning a public IP to the web-1 VM and then trying the load balancer again.
upvoted 0 times
...
Allene
5 months ago
I'm a bit confused on the difference between a network load balancer and an application load balancer. I'll need to review the AWS documentation to understand which one is appropriate for this scenario.
upvoted 0 times
...
Malcolm
5 months ago
I've seen issues like this before. My guess is that the security group rules are not allowing the load balancer to access the web-1 VM. I'd start there and make sure the inbound rules are set up correctly.
upvoted 0 times
...
Youlanda
5 months ago
Okay, let me think this through step-by-step. The key things I need to check are the security group rules, the web-1 VM's IP address, and the load balancer settings.
upvoted 0 times
...
Ocie
5 months ago
Hmm, this seems like a tricky one. I'll need to carefully review the details about the VPC, security group, and load balancer configuration to figure out what's going on.
upvoted 0 times
...
Gilma
10 months ago
I bet the admin is scratching their head, wondering why this isn't working. Guess they need to brush up on their Nutanix and AWS networking skills. Maybe they should try asking Alexa for help?
upvoted 0 times
Lorean
9 months ago
C) The administrator needs to provision an application load balancer instead of a network load balancer to allow Internet traffic to access the UVM subnet.
upvoted 0 times
...
Marti
9 months ago
B) The administrator has not modified the inbound rules under the UVM security group to allow the network load balancer to access the UVM subnet.
upvoted 0 times
...
Rodrigo
10 months ago
A) The load balancer is still in a Provisioning state.
upvoted 0 times
...
...
Amira
10 months ago
An application load balancer, eh? Sounds like the admin is trying to overcomplicate things. Why not just use a good old-fashioned network load balancer and save everyone the headache?
upvoted 0 times
Sherita
10 months ago
B
upvoted 0 times
...
Maybelle
10 months ago
B
upvoted 0 times
...
...
Yan
10 months ago
But could it also be that the administrator has not modified the inbound rules under the UVM security group to allow the network load balancer to access the UVM subnet?
upvoted 0 times
...
Adrianna
10 months ago
I agree with Stanford. The load balancer needs to finish provisioning before it can successfully route traffic.
upvoted 0 times
...
Barrett
11 months ago
No public IP for web-1? Well, that's the problem right there! Can't have a public-facing web server without a public IP, duh!
upvoted 0 times
Lisbeth
10 months ago
No public IP for web-1? Well, that's the problem right there! Can't have a public-facing web server without a public IP, duh!
upvoted 0 times
...
Allene
10 months ago
C) The administrator has not assigned a public IP to web-1.
upvoted 0 times
...
Viola
10 months ago
B) The administrator has not modified the inbound rules under the UVM security group to allow the network load balancer to access the UVM subnet.
upvoted 0 times
...
Jaleesa
10 months ago
A) The load balancer is still in a Provisioning state.
upvoted 0 times
...
...
Stanford
11 months ago
I think the issue is happening because the load balancer is still in a Provisioning state.
upvoted 0 times
...
Marget
11 months ago
Ohhh, the administrator forgot to open up the security group! That's a classic newbie mistake. Better fix that before trying anything else.
upvoted 0 times
...
Noe
11 months ago
The load balancer is still in a Provisioning state, so it's not ready to receive traffic yet. Gotta be patient, my friend!
upvoted 0 times
...

Save Cancel