Nutanix NCM-MCI Practice Exam Questions & Answers

Here is the step-by-step solution to modify the security policy file as required.

Navigate to the desktop and open the file Security Policy.txt (which corresponds to the provided Security Policy.bak content) using a text editor like Notepad.

Modify the file content by replacing the xxxxx and xxxx placeholders according to the security requirements.

Modifications by Rule

Here are the specific changes to make within the file:

1. Quarantine Rule

Requirement 1 (No Logging): The quarantine rule should not be logged.

Change 'is_policy_hitlog_enabled': 'xxxxx' to 'is_policy_hitlog_enabled': 'false'

Requirement 2 (Enforce): This rule must be enforced.

Change 'action': 'xxxxx' (under quarantine_rule) to 'action': 'APPLY'

Requirement 3 (Environment): The rule must affect the 'SecOps' environment.

Change 'Environment': ['xxxxx'] to 'Environment': ['SecOps']

2. SMB-block Rule

Requirement 1 (Logging): This rule must be logged.

Change 'is_policy_hitlog_enabled': 'xxxxx' to 'is_policy_hitlog_enabled': 'True'

Requirement 2 (Monitor): This rule must not be enforced, only logged.

Change 'action': 'xxxxx' (under isolation_rule) to 'action': 'MONITOR'

Requirement 4 (Tags): The rule must affect the 'smbhost' and 'smbclient' tags.

Change 'SMBv1': ['xxxxx'] to 'SMBv1': ['smbhost']

Change 'SMRv1': ['xxxxx'] to 'SMRv1': ['smbclient']

3. DN test (dn-policy1) Rule

Requirement 2 (Monitor): This rule must not be enforced, only logged.

Change 'action': 'xxxx' (under app_rule) to 'action': 'MONITOR'

Requirement 5 (Allow IPv6): This policy must allow IPv6 traffic.

Change 'allow_ipv6_traffic': 'xxxx' to 'allow_ipv6_traffic': 'True'

Final Step

After making all the replacements, Save the file, overwriting the original Security Policy.txt on the desktop.

Example of completed rules (replace xxxxx accordingly):

Rule Name: Quarantine Rule

Logged: false

Action: APPLY

Environment: SecOps

Protocols: TCP

Ports: 8080

Rule Name: SMB Rule

Logged: True

Action: MONITOR

Tags: smbhost, smbclient

Protocols: TCP

Ports: 8080

Rule Name: DN Test Policy

Logged: True

Action: MONITOR

Environment: Non-Prod

Protocols: ALL

Ports: 8080

Here is the step-by-step solution to complete both tasks on Cluster 1.

This solution requires you to first find the IP of Cluster 2 (for the SMTP server) and then perform all configurations within the Prism Element interface for Cluster 1.

Prerequisite: Find Cluster 2 IP

In Prism Central, navigate to Hardware > Clusters.

Find Cluster 2 in the list and note its IP Address. You will use this in the steps below.

Task 1: Create the VM Template

Log in to the Prism Element (PE) interface for Cluster 1. (From PC, go to Hardware > Clusters > click the name 'Cluster 1').

Navigate to the VM view from the main dashboard.

Click the + Create VM button.

Fill in the VM details based on the NVD-2031 'Small VM' configuration (e.g., 2 vCPUs, 1 Core per vCPU, 4 GB RAM).

Name: Small Template

Compute Details:

vCPUs: 2

Number of Cores per vCPU: 1

Memory: 4 GB

Scroll down to Storage and click + Add New Disk.

Operation: Select Clone from Image Service.

Image: Select any available guest OS image (e.g., a Windows or CentOS image).

Storage Container: Ensure the default container is selected (as required by the task).

Click Add.

Scroll down to Network Adapters (NIC) and click + Add NIC.

Select any available VLAN/Subnet (e.g., Primary).

Click Add.

Click Save. The VM will be created (and remain powered off).

Find the new Small Template VM in the list. Select its checkbox.

Click the Actions dropdown and select Convert to Template.

Confirm the action by clicking OK.

Task 2: Configure SMTP and NCC Reports

While still in the Cluster 1 Prism Element interface, click the gear icon (Settings) in the top-right corner.

Select SMTP Server from the left-hand menu.

Click the Configure button.

In the 'Server Settings' tab, fill in the following:

Server Address: Enter the Cluster 2 IP Address (which you found in the prerequisite step).

Port: 25 (leave as default).

From Email Address: [email protected]

Click Next.

In the 'Email Recipients' tab, click + Add Email Recipient.

Address: [email protected]

Ensure all severities (Critical, Warning, Info) are checked.

Click Save.

Click + Add Email Recipient again.

Address: [email protected]

Ensure all severities are checked.

Click Save.

Click Done. A test email will be sent.

In the main Settings menu, select Alerts and Notifications.

Scroll to the NCC Health Checks section.

Check the box labeled Email Nutanix Cluster Check reports to recipients. (This will use the SMTP settings and recipients you just configured).

Click Save.

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

Here is the step-by-step solution to configure syslog for Cluster 1.

1. Access Cluster 1 Prism Element

Since the requirement is to only configure Cluster 1 and not other clusters, this task must be performed in the Prism Element (PE) interface for Cluster 1.

From the main Prism Central dashboard, navigate to Hardware > Clusters.

Find Cluster 1 in the list and click its name. This will open the specific Prism Element login page for that cluster.

Log in to Cluster 1's Prism Element interface.

2. Add the Syslog Server

In the Cluster 1 PE interface, click the gear icon (Settings) in the top-right corner.

From the left-hand menu, select Syslog.

In the 'Remote Syslog Server' section, click the + Add Syslog Server button.

Fill in the server details as required:

Name: Corp_Syslog

IP Address: 34.142.155.231

Port: 514

Protocol: TCP (This provides the highest reliability, as requested).

Click Save.

3. Configure Log Modules and Severities

Now, we must specify which logs to send to the new server.

On the same Syslog settings page, find the 'Syslog Configuration' section and click the Configure button (or Modify if a default is present).

A dialog box 'Select Modules and Levels' will appear.

Uncheck all modules to ensure no extra logs are sent.

Check the box for the RSyslog Server Module (or rsyslog_forwarder).

For this module, check the boxes for the severities: Critical, Warning, and Info.

Check the box for the ApiServer module.

This module logs all operational tasks and audit trails, which includes all Virtual Machine changes.

For this module, check the boxes for the top severity levels: Critical, Warning, and Info.

Ensure no other modules (like Stargate, Cerebro, Zookeeper, etc.) are checked.

Click Save.

Cluster 1 is now configured to send its audit logs (including VM changes) and its own syslog monitoring logs to the Corp_Syslog server via TCP, fulfilling all security requirements.

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, see Citrix Virtual Apps and Desktops on Nutanix or Nutanix virtualization environments.

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

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.

Here is the step-by-step solution to configure the Volume Group for optimized performance in the production environment.

This task is performed in Prism Central.

From the main dashboard, navigate to Compute & Storage > Volume Groups.

Find the Volume Group named Database_VM in the list.

Select the checkbox next to Database_VM.

Click the Actions dropdown menu and select Update.

In the 'Update Volume Group' dialog, scroll to the bottom of the 'Basic Configuration' section.

Find the checkbox labeled Enable Client Side Load Balancing and check it.

Note: This setting allows the iSCSI initiator within the guest VM to connect to all CVMs in the cluster, distributing the storage load from the three vDisks across all three nodes in the production environment instead of focusing all I/O on just one.

Click Save.