Nutanix Nutanix Certifications NCM-MCI-6.5 Questions & Answers

• Question 11:

  CORRECT TEXT Task 5 An administrator has been informed that a new workload requires a logically segmented network to meet security requirements. Network configuration: VLAN: 667 Network: 192.168.0.0 Subnet Mask: 255.255.255.0 DNS server: 34.82.231.220 Default Gateway: 192.168.0.1 Domain: cyberdyne.net IP Pool: 192.168.9.100-200 DHCP Server IP: 192.168.0.2 Configure the cluster to meet the requirements for the new workload if new objects are required, start the name with 667.

  A. Answer: See the for step by step solution.

  Correct Answer: A

  To configure the cluster to meet the requirements for the new workload, you need to do the following steps: Create a new VLAN with ID 667 on the cluster. You can do this by logging in to Prism Element and going to Network Configuration > VLANs > Create VLAN. Enter 667 as the VLAN ID and a name for the VLAN, such as 667_VLAN. Create a new network segment with the network details provided. You can do this by logging in to Prism Central and going to Network > Network Segments > Create Network Segment. Enter a name for the network segment, such as 667_Network_Segment, and select 667_VLAN as the VLAN. Enter 192.168.0.0 as the Network Address and 255.255.255.0 as the Subnet Mask. Enter 192.168.0.1 as the Default Gateway and 34.82.231.220 as the DNS Server. Enter cyberdyne.net as the Domain Name. Create a new IP pool with the IP range provided. You can do this by logging in to Prism Central and going to Network > IP Pools > Create IP Pool. Enter a name for the IP pool, such as 667_IP_Pool, and select 667_Network_Segment as the Network Segment. Enter 192.168.9.100 as the Starting IP Address and 192.168.9.200 as the Ending IP Address. Configure the DHCP server with the IP address provided. You can do this by logging in to Prism Central and going to Network > DHCP Servers > Create DHCP Server. Enter a name for the DHCP server, such as 667_DHCP_Server, and select 667_Network_Segment as the Network Segment. Enter 192.168.0.2 as the IP Address and select 667_IP_Pool as the IP Pool.

  

  

  

• Question 12:

  CORRECT TEXT

  Task 1

  An administrator has been asked to configure a storage for a distributed application which uses large data sets across multiple worker VMs.

  The worker VMs must run on every node. Data resilience is provided at the application level and low cost per GB is a Key Requirement.

  Configure the storage on the cluster to meet these requirements. Any new object created should include the phrase Distributed_App in the name.

  A. Answer: See the for step by step solution.

  Correct Answer: A

  To configure the storage on the cluster for the distributed application, you can follow these steps:

  Log in to Prism Element of cluster A using the credentials provided. Go to Storage > Storage Pools and click on Create Storage Pool. Enter a name for the new storage pool, such as Distributed_App_Storage_Pool, and select the disks to

  include in the pool. You can choose any combination of SSDs and HDDs, but for low cost per GB, you may prefer to use more HDDs than SSDs.

  Click Save to create the storage pool.

  Go to Storage > Containers and click on Create Container. Enter a name for the new container, such as Distributed_App_Container, and select the storage pool that you just created, Distributed_App_Storage_Pool, as the source. Under

  Advanced Settings, enable Erasure Coding and Compression to reduce the storage footprint of the data. You can also disable Replication Factor since data resilience is provided at the application level. These settings will help you achieve

  low cost per GB for the container.

  Click Save to create the container.

  Go to Storage > Datastores and click on Create Datastore. Enter a name for the new datastore, such as Distributed_App_Datastore, and select NFS as the datastore type. Select the container that you just created, Distributed_App_Container,

  as the source.

  Click Save to create the datastore.

  The datastore will be automatically mounted on all nodes in the cluster. You can verify this by going to Storage > Datastores and clicking on Distributed_App_Datastore. You should see all nodes listed under Hosts.

  You can now create or migrate your worker VMs to this datastore and run them on any node in the cluster. The datastore will provide low cost per GB and high performance for your distributed application.

• Question 13:

  CORRECT TEXT

  Task 10

  An administrator is working to create a VM using Nutanix V3 API calls with the following specifications.

  *

  VM specifications:

  *

  vCPUs: 2

  *

  Memory: BGb

  *

  Disk Size: 50Gb

  *

  Cluster: Cluster A

  *

  Network: default- net

  

  The API call is falling, indicating an issue with the payload:

  The body is saved in Desktop/ Files/API_Create_VM,text

  Correct any issues in the text file that would prevent from creating the VM. Also ensure the VM will be created as speeded and make sure it is saved for re-use using that filename.

  Deploy the vm through the API

  Note: Do not power on the VM.

  A. Answer: See the for step by step solution.

  Correct Answer: A

  https://portal.nutanix.com/page/documents/kbs/details?targetId=kA00e000000LLEzCAO https://jsonformatter.curiousconcept.com/#

  acli net.list(uuid network defult_net)

  ncli cluster info(uuid cluster)

  Put Call: https://Prism Central IP address : 9440/api/nutanix/v3vms Edit these lines to fix the API call, do not add new lines or copy lines. You can test using the Prism Element API explorer or PostMan Body:

  {

  {

  "spec": {

  "name": "Test_Deploy",

  "resources": {

  "power_state":"OFF",

  "num_vcpus_per_socket": ,

  "num_sockets": 1,

  "memory_size_mib": 8192,

  "disk_list": [

  {

  "disk_size_mib": 51200,

  "device_properties": {

  "device_type":"DISK"

  }

  },

  {

  "device_properties": {

  "device_type":"CDROM"

  }

  }

  ],

  "nic_list":[

  {

  "nic_type": "NORMAL_NIC",

  "is_connected": true,

  "ip_endpoint_list": [

  {

  "ip_type": "DHCP"

  }

  ],

  "subnet_reference": {

  "kind": "subnet",

  "name": "default_net",

  "uuid": "00000000-0000-0000-0000-000000000000"

  }

  }

  ],

  },

  "cluster_reference": {

  "kind": "cluster",

  "name": "NTNXDemo",

  "uuid": "00000000-0000-0000-0000-000000000000"

  }

  },

  "api_version": "3.1.0",

  "metadata": {

  "kind": "vm"

  }

  }

  https://www.nutanix.dev/2019/08/26/post-a-package-building-your-first-nutanix-rest-api- post-request/

  Reference

• Question 14:

  CORRECT TEXT

  Task 2

  An administrator needs to configure storage for a Citrix-based Virtual Desktop infrastructure.

  Two VDI pools will be created

  Non-persistent pool names MCS_Pool for tasks users using MCS Microsoft Windows 10 virtual Delivery Agents (VDAs)

  Persistent pool named Persist_Pool with full-clone Microsoft Windows 10 VDAs for power users

  20 GiB capacity must be guaranteed at the storage container level for all power user VDAs

  The power user container should not be able to use more than 100 GiB

  Storage capacity should be optimized for each desktop pool.

  Configure the storage to meet these requirements. Any new object created should include the name of the pool(s) (MCS and/or Persist) that will use the object.

  Do not include the pool name if the object will not be used by that pool.

  Any additional licenses required by the solution will be added later.

  A. Answer: See the for step by step solution.

  Correct Answer: A

  To configure the storage for the Citrix-based VDI, you can follow these steps:

  Log in to Prism Central using the credentials provided. Go to Storage > Storage Pools and click on Create Storage Pool. Enter a name for the new storage pool, such as VDI_Storage_Pool, and select the disks to include in the pool. You can

  choose any combination of SSDs and HDDs, but for optimal performance, you may prefer to use more SSDs than HDDs.

  Click Save to create the storage pool.

  Go to Storage > Containers and click on Create Container. Enter a name for the new container for the non-persistent pool, such as MCS_Pool_Container, and select the storage pool that you just created, VDI_Storage_Pool, as the source.

  Under Advanced Settings, enable Deduplication and Compression to reduce the storage footprint of the non-persistent desktops. You can also enable Erasure Coding if you have enough nodes in your cluster and want to save more space.

  These settings will help you optimize the storage capacity for the non-persistent pool.

  Click Save to create the container.

  Go to Storage > Containers and click on Create Container again. Enter a name for the new container for the persistent pool, such as Persist_Pool_Container, and select the same storage pool, VDI_Storage_Pool, as the source.

  Under Advanced Settings, enable Capacity Reservation and enter 20 GiB as the reserved capacity. This will guarantee that 20 GiB of space is always available for the persistent desktops. You can also enter 100 GiB as the advertised

  capacity to limit the maximum space that this container can use. These settings will help you control the storage allocation for the persistent pool.

  Click Save to create the container.

  Go to Storage > Datastores and click on Create Datastore. Enter a name for the new datastore for the non-persistent pool, such as MCS_Pool_Datastore, and select NFS as the datastore type. Select the container that you just created,

  MCS_Pool_Container, as the source.

  Click Save to create the datastore.

  Go to Storage > Datastores and click on Create Datastore again. Enter a name for the new datastore for the persistent pool, such as Persist_Pool_Datastore, and select NFS as the datastore type. Select the container that you just created,

  Persist_Pool_Container, as the source.

  Click Save to create the datastore.

  The datastores will be automatically mounted on all nodes in the cluster. You can verify this by going to Storage > Datastores and clicking on each datastore. You should see all nodes listed under Hosts.

  You can now use Citrix Studio to create your VDI pools using MCS or full clones on these datastores. For more information on how to use Citrix Studio with Nutanix Acropolis, seeCitrix Virtual Apps and Desktops on NutanixorNutanix

  virtualization environments.

  

  

  https://portal.nutanix.com/page/documents/solutions/details?targetId=BP-2079-Citrix- Virtual-Apps-and-Desktops:bp-nutanix-storage-configuration.html

• Question 15:

  CORRECT TEXT Task 6 An administrator has requested the commands needed to configure traffic segmentation on an unconfigured node. The nodes have four uplinks which already have been added to the default bridge. The default bridge should have eth0 and

  eth1 configured as active/passive, with eth2 and eth3 assigned to the segmented traffic and configured to take advantage of both links with no changes to the physical network components. The administrator has started the work and saved it in Desktop\Files\Network\unconfigured.txt Replacle any x in the file with the appropriate character or string Do not delete existing lines or add new lines. Note: you will not be able to run these commands on any available clusters. Unconfigured.txt manage_ovs --bond_name brX-up --bond_mode xxxxxxxxxxx --interfaces ethX,ethX update_uplinks manage_ovs --bridge_name brX-up --interfaces ethX,ethX --bond_name bond1 -- bond_mode xxxxxxxxxxx update_uplinks

  A. Answer: See the for step by step solution.

  Correct Answer: A

  To configure traffic segmentation on an unconfigured node, you need to run the following commands on the node: manage_ovs --bond_name br0-up --bond_mode active-backup --interfaces eth0,eth1 update_uplinks manage_ovs --bridge_name br0-up --interfaces eth2,eth3 --bond_name bond1 --bond_mode balance-slb update_uplinks These commands will create a bond named br0-up with eth0 and eth1 as active and passive interfaces, and assign it to the default bridge. Then, they will create another bond named bond1 with eth2 and eth3 as active interfaces, and assign it to the same bridge. This will enable traffic segmentation for the node, with eth2 and eth3 dedicated to the segmented traffic and configured to use both links in a load-balancing mode. I have replaced the x in the file Desktop\Files\Network \unconfigured.txt with the appropriate character or string for you. You can find the updated file in Desktop\Files\Network\configured.txt.

  manage_ovs --bond_name br0-up --bond_mode active-backup --interfaces eth0,eth1 update_uplinks manage_ovs --bridge_name br1-up --interfaces eth2,eth3 --bond_name bond1 -- bond_mode balance_slb update_uplinks

  https://portal.nutanix.com/page/documents/solutions/details?targetId=BP-2071-AHV- Networking:ovs-command-line-configuration.html

• Question 16:

  CORRECT TEXT

  Task 15

  An administrator found a CentOS VM, Cent_Down, on the cluster with a corrupted network stack. To correct the issue, the VM will need to be restored from a previous snapshot to become reachable on the network again.

  VM credentials:

  Username: root

  Password: nutanix/4u

  Restore the VM and ensure it is reachable on the network by pinging 172.31.0.1 from the VM.

  Power off the VM before proceeding.

  A. Answer: See the for step by step solution.

  Correct Answer: A

  To restore the VM and ensure it is reachable on the network, you can follow these steps:

  Log in to the Web Console of the cluster where the VM is running. Click on Virtual Machines on the left menu and find Cent_Down from the list. Click on the power icon to power off the VM.

  Click on the snapshot icon next to the power icon to open the Snapshot Management window.

  Select a snapshot from the list that was taken before the network stack was corrupted. You can use the date and time information to choose a suitable snapshot. Click on Restore VM and confirm the action in the dialog box. Wait for the

  restore process to complete.

  Click on the power icon again to power on the VM. Log in to the VM using SSH or console with the username and password provided. Run the command ping 172.31.0.1 to verify that the VM is reachable on the network. You should see a

  reply from the destination IP address.

  Go to VMS from the prism central gui

  Select the VMand go to More -> Guest Shutdown

  Go to Snapshots tab and revert to latest snapshot available power on vm and verify if ping is working