NCP-CI-AWS Practice Test

Explanation:
To manually hibernate an NC2 on AWS cluster, the administrator can use the following methods:

Select the cluster under NC2 console and Select Hibernate/Resume on the cluster sur page:
Navigate to the specific cluster in the NC2 console and use the provided Hibernate/Resume option.

Log into NC2 console, find the cluster name and select Hibernate/Resume from the ellipses:
Access the NC2 console, locate the cluster name, and select the Hibernate/Resume option from the ellipses (three dots) menu.

These options allow for the manual control of the cluster's hibernation state directly within the NC2 console interface.

Explanation:
AHV (Answer A):
AHV (Acropolis Hypervisor) can be upgraded using Lifecycle Manager (LCM). LCM simplifies the upgrade process and ensures that all components are updated in a coordinated manner.
BIOS (Answer C):
BIOS upgrades can also be performed using LCM. This helps in maintaining hardware compatibility and performance by ensuring that the latest firmware is installed.

Explanation:
In Nutanix Cloud Integration with AWS, specifically version 6.7, the role that allows full access to clusters created within an organization is the Organization Administrator.
The Organization Administrator role has the highest level of privileges within an organization, enabling the user to manage all aspects of the clusters, including creation, modification, and deletion.
This role is designed to oversee and control the entire organization's resources, ensuring comprehensive management capabilities over all clusters and associated resources.

Explanation:

• Upon creation, each node within an AWS NC2 cluster has3 Amazon Elastic Block Store (EBS) volumes attached.
• These volumes are used for different purposes, such as operating system storage, Nutanix services, and user data storage.
• The number of EBS volumes is designed to ensure adequate storage performance and capacity for the NC2 cluster's operations and workload demands.

Explanation:
To ensure that NC2 VMs can access AWS resources without traversing the internet, the administrator can use AWS VPC Peering and Interface Endpoints. Both methods ensure that traffic stays within the AWS network, maintaining security and efficiency.
Interface Endpoint:

• Interface Endpoints allow you to privately connect your VPC to supported AWS services. They use AWS PrivateLink to route traffic directly to services within the AWS network, bypassing the public internet.

• Create an interface endpoint for the required service in the AWS VPC console.
• Ensure the security groups and route tables are configured to allow traffic to the interface endpoint.

• VPC Peering allows the routing of traffic between VPCs using private IP addresses, without the need for internet gateways, NAT devices, or VPN connections.

• Create a VPC peering connection between the VPCs.
• Update the route tables to direct traffic between the peered VPCs.
• Ensure security group rules allow the necessary traffic between VPCs.