Pass the Nutanix NCS Professional NCS-Core Questions and answers with ValidTests

To ensure the new application is securely deployed without affecting existing applications, the administrator should create new categories for the VMs hosting the new application. This approach allows for targeted application of security policies without impacting other applications. After creating these new categories, the administrator should then create new security policies that incorporate these categories and specify the unique, non-standard ports used by the application, ensuring that security is tailored specifically to the new application's needs.References: Nutanix Prism Central Guide, Nutanix Security Configuration Best Practices.

When changing VLAN configurations for hosts and Controller Virtual Machines (CVMs) in a Nutanix cluster, doing so while the cluster is running can result in temporary communication losses, leading to alerts such as a node appearing down. To avoid these disruptions and ensure a smooth reconfiguration process, it is advisable to stop the cluster services before making VLAN changes. This prevents the cluster from detecting intermittent connectivity as node failures, thereby avoiding false alerts in Prism Element.

References:

Nutanix Bible (https://www.nutanixbible.com ), particularly the sections discussing cluster operations and network reconfiguration.

Nutanix University: NCS-Core 6.8 Training (https://university.nutanix.com ), which includes best practices for network configuration.

In a Nutanix cluster, when a Controller Virtual Machine (CVM) fails, the iSCSI targets for the volume groups managed by that CVM are not left inoperable. Instead, the volume group's iSCSI targets (vDisks) are automatically redirected to another operational CVM in the cluster. This failover mechanism ensures that there is no interruption in service or data availability. The redirection is seamless and does not require manual intervention, allowing for continuous access to the volume group by the SQL cluster.

References:

Nutanix Bible: Data Protection and High Availability

Nutanix University: Resiliency and Disaster Recovery

For re-configuring an existing cluster for a new use case where data preservation is not a concern, and there is a lack of CVM credentials:

C. Foundation VM - Bare Metal: This tool allows for a complete re-installation of the Nutanix software from scratch, which is ideal in scenarios where existing configurations and data are no longer needed, and access credentials are unknown or lost.

References:

Nutanix Bible (https://www.nutanixbible.com ), especially sections on cluster reconfiguration and Foundation tools.

Nutanix University: NCS-Core 6.8 Training (https://university.nutanix.com ), where cluster deployment and reconfiguration scenarios are extensively covered.

In the scenario where a consultant observes ping timeouts after shutting down one of the links during a port failover test, the issue is likely due to a Native VLAN mismatch on the switchport. The configuration settings shown in the second exhibit indicate different native VLANs for the switch ports connected to the Nutanix node. This mismatch can cause connectivity issues when one of the links is down, as VLAN tagging inconsistencies prevent proper fallback and routing of traffic.References: Cisco Networking Troubleshooting Guide, Nutanix Network Configuration Best Practices.

If a customer needs to re-image an existing cluster and both the Foundation Applet and Foundation VM are unavailable, the consultant can access Foundation-as-a-Service (FaaS) through the CVM IP address followed by port 9443, as indicated in Option C. FaaS allows for the re-imaging of Nutanix nodes through a web interface hosted directly on the CVM, making it an effective tool for deploying and managing clusters without needing additional installation media or virtual machines.References: Nutanix Foundation as a Service (FaaS) Documentation, Nutanix Support Portal.

For continuing the cluster deployment without an NTP server immediately available: A. An NTP server is not required for the initial foundation process of the cluster and can indeed be added later. This allows the deployment to proceed without delays, although it's critical to add NTP synchronization as soon as possible post-deployment to ensure proper cluster time management. B. If an NTP server is to be provided using an FQDN, then a DNS server must indeed be available. This is because the FQDN needs to be resolved to an IP address, which requires DNS resolution services. Options C and D are not strictly required as per Nutanix deployment standards; a single NTP server can suffice initially, and there's no requirement for it to be external or in a comma-separated list unless specifically dictated by network or organizational policies.References: Nutanix Installation and Configuration Guide, Nutanix Foundation Tool documentation.

To satisfy the customer's request for additional performance and resiliency tests on a cluster, deploying Nutanix X-Ray is the best option. X-Ray is a performance testing and benchmarking tool specifically designed for hyper-converged infrastructures and provides a range of tests that simulate real-world scenarios, stress tests, and resiliency tests. This tool allows the consultant to comprehensively assess the performance, fault tolerance, and operational resilience of the Nutanix cluster, meeting the customer's testing requirements effectively.References: Nutanix X-Ray Documentation, Nutanix Performance Testing Best Practices.

The Nutanix Field Installation Guide primarily provides instructions for using Foundation. Foundation is the tool used for deploying, imaging, and configuring Nutanix nodes in a new installation or when expanding existing clusters. This tool is essential for setting up the Nutanix environment correctly and efficiently.References:

Nutanix University - NCS-Core 6.8 Learning Path

The Nutanix Bible, Foundation chapter (https://www.nutanixbible.com/ )

ref: https://portal.nutanix.com/page/documents/details?targetId=Web-Console-Guide-Prism-v55:wc-network-visualization-intro-c.html