NCP-CI-Azure Reviews Questions

Node Termination Observation:When a node is terminated from the Azure portal, the NC2 cluster will detect that the node is no longer operational.

Marking as Degraded:NC2 will mark the node as degraded, indicating that the node is not functioning as expected. This status allows administrators to take necessary actions to resolve the issue, such as provisioning a new node or addressing the degradation cause.

References:

Nutanix NC2 Cluster Management Guide

Azure Instance Termination Documentation

Payment Method Options:When using a Pay As You Go subscription plan and opting to pay directly to Nutanix, wire transfer is a valid and secure payment method.

Direct Payment:Wire transfers allow for the direct transfer of funds from the organization's bank account to Nutanix, ensuring a straightforward and efficient payment process.

References:

Nutanix Billing and Payment Documentation

Pay As You Go Subscription Payment Methods Guide

Role Requirements: The task involves creating and managing multiple organizations and clusters, along with managing user access across the company.

Role Capabilities: The "Customer Administrator" role is designed to provide extensive administrative capabilities, including:

Creating and managing organizations.

Managing clusters.

Handling user access and permissions.

Comparison of Roles:

Cluster Administrator: Primarily focuses on managing individual clusters but does not encompass organization-wide administrative tasks.

Customer Security Administrator: Focuses on security-related tasks and does not have broad administrative capabilities across organizations and clusters.

Organization Administrator: Manages organizational settings but might not cover all aspects needed for multiple clusters and user access management.

Conclusion: The "Customer Administrator" role meets all the requirements for managing organizations, clusters, and user access comprehensively.

References:

Nutanix Role-Based Access Control Documentation

NC2 on Azure User Roles Guide

Jump Host VM in External VNet with VNet Peering:

Deploy Jump Host VM:Deploy a VM in an external VNet that is not within the same network as Prism Central.

VNet Peering:Establish VNet peering between the external VNet and the Prism Central VNet. This allows the Jump Host to communicate with Prism Central securely.

Jump Host VM in Prism Central VNet Inside a Delegated Subnet:

Deploy Jump Host VM:Deploy the Jump Host VM directly in the Prism Central VNet within a delegated subnet. This places the Jump Host in the same network environment as Prism Central, allowing direct access.

References:

Azure VNet Peering Documentation

Nutanix NC2 Networking and Access Configuration Guide