An administrator is experiencing problems with several operations, including VM IP address assignment validations, VM power-on and VM power-off…

--- QUESTION #72 --- An administrator is experiencing problems with several operations, including VM IP address assignment validations, VM power-on and VM power-off operations. Whenever a related operation is performed, an alert is generated in the NC2 console indicating that the Cloud API endpoints are unavailable. The issue was further investigated and it was determined that NC2 is unable to make API calls to the underlying cloud infrastructure due to network connectivity misconfigurations. Which two connectivity misconfigurations could be causing this issue? (Choose two.)

A. AWS VPC endpoints are used for connectivity to AWS services.
B. Subnets are connected to the Internet via NAT gateways.
C. Route tables for cloud subnets contain incorrect route entries.
D. IAM roles and policies are incorrectly configured. --- Correct Answer: C, D

Explanation: The alert "Cloud API endpoints are unavailable" signifies a failure in communication between the Nutanix cluster and AWS APIs. The question attributes this to "network connectivity misconfigurations." Incorrect route table entries (C) directly cause network connectivity failure by preventing IP packets from reaching the AWS service endpoints. Incorrectly configured IAM roles and policies (D) result in API call rejection due to insufficient permissions, which also prevents successful communication. Nutanix documentation confirms that both network path issues (routing) and IAM permission failures are primary causes for this symptom.

Why Incorrect Options are Wrong:
A. Using AWS VPC endpoints is a valid and often recommended configuration for private AWS API access, not an inherent misconfiguration.

B. Connecting subnets to the Internet via NAT gateways is a standard, valid architecture for outbound access and not a misconfiguration itself.

References:
1. Nutanix Cloud Clusters on AWS Deployment and User Guide v6.8, "Troubleshooting NC2 on AWS" section: This guide often details common alerts and their root causes. It specifies that alerts related to AWS API unavailability should prompt checks of both network connectivity (route tables, security groups) and the IAM role permissions. This supports both (C) and (D) as potential causes for the described symptom.
2. AWS VPC User Guide, "Route tables for your VPC": "A route table contains a set of rules, called routes, that are used to determine where network traffic from your subnet or gateway is directed." An incorrect entry here would directly cause the network connectivity failure described, supporting option (C).
3. AWS Identity and Access Management User Guide, "Policies and permissions in IAM": This document explains that IAM policies define permissions. If the policy attached to the NC2 role lacks necessary permissions (e.g., ec2:StartInstances), API calls will fail. This supports option (D) as a cause for failed VM operations.