NCM-MCI Exam Dumps and Practice Questions

Here is the step-by-step solution to configure Cluster 1 from its Prism Element interface.

1. Disable the backup_schedule_check NCC Check

This will prevent the WARN message for the NoVMs protection domain.

Log in to the Cluster 1 Prism Element (PE) interface.

Navigate to the Health dashboard (click the 'heart' icon in the top-left).

In the left-hand menu, select NCC.

In the search bar for the checks, type backup_schedule_check to find the specific check.

Select the checkbox next to the backup_schedule_check in the list.

Click the Disable button that appears above the table. This will stop this check from running during NCC health reports.

2. Configure and Resolve Pulse Alerts

This process involves two parts: disabling the alerting policy, and then enabling Pulse itself to resolve the underlying condition.

A . Disable the Alert Policy

This stops the system from generating a new alert if Pulse is ever disabled, satisfying the 'do not want an alert' requirement.

Click the gear icon (Settings) in the top-right corner.

From the left-hand menu, select Alert Policies.

In the search bar, type Pulse to find the policy.

Select the checkbox for the alert policy named Pulse is not enabled (or pulse_disabled_alert).

Click the Update button.

Uncheck the Enable box for the policy.

Click Save.

B . Enable Pulse (to Resolve the Condition)

This enables the Pulse service to record messages (as requested) and fixes the root cause of the alert, allowing it to be resolved.

Click the gear icon (Settings) in the top-right corner.

From the left-hand menu, select Pulse.

Click the Enable Pulse button (or 'Update' if it's already partially configured).

Check the box for Enable Pulse.

(Note: Any 'Enable alerts for Pulse' boxes would remain unchecked or be ignored, as the main Alert Policy itself is now disabled.)

Click Save.

C . Resolve the Active Alert

Navigate to the Alerts dashboard (click the 'bell' icon in the top-left).

Find the active alert: Pulse is not enabled.

(Note: If the alert is not present, you would first go to the Health dashboard, run the check_pulse NCC check to generate it, and then return to the Alerts dashboard.)

Select the checkbox next to the 'Pulse is not enabled' alert.

Click the Resolve button that appears at the top of the list. Since the underlying condition (Pulse being disabled) is now fixed, the alert will be successfully resolved.

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.

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.

Here is the step-by-step solution to create the high-performance SQL VM on Cluster 1.

This task requires two phases: first, creating a new all-flash storage container, and second, creating the VM with a specific vNUMA and disk controller configuration for maximum performance.

1. Access Cluster 1 Prism Element

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. Create the All-Flash Storage Container

To maximize performance for a 'write-intensive' workload on a hybrid cluster, the data and log disks must be placed on an all-flash container.

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

From the left-hand menu, select Storage.

Click the + Storage Container button.

Fill in the basic details:

Name: NEWSQL_Flash_Container

Click Advanced Settings.

Scroll down to the Storage Tier section.

Select the SSD radio button. This pins all data in this container to the SSD tier, ensuring all-flash performance.

Click Save.

3. Create and Configure the VM

Now, create the VM, applying vNUMA and multi-SCSI controller best practices.

From the main PE dashboard, navigate to the VM view.

Click the + Create VM button.

Enter the compute details. This configuration is critical for vNUMA performance, as it tells the VM's guest OS about the underlying physical NUMA topology (2 CPUs with 8 cores each).

Name: NEWSQL_VM

vCPUs: 12

Number of Sockets: 2

Cores per vCPU: 6 (This creates a 2-socket, 6-core VM, totaling 12 vCPUs)

Memory: 128 GB

Scroll down to the Disks section and add the OS disk:

Click + Add New Disk.

Storage Container: Select the default (hybrid) container.

Size: 100 GB

Bus: SCSI

Device Index: 0 (This will be scsi.0)

Click Add.

Add the Data disk (on its own controller for parallel processing):

Click + Add New Disk.

Storage Container: Select NEWSQL_Flash_Container.

Size: 750 GB

Bus: SCSI

Device Index: 1 (This creates a new controller, scsi.1)

Click Add.

Add a Log disk (on its own controller, a best practice for 'write-intensive' SQL):

Click + Add New Disk.

Storage Container: Select NEWSQL_Flash_Container.

Size: 100 GB (A common size for a log disk)

Bus: SCSI

Device Index: 2 (This creates a third controller, scsi.2)

Click Add.

Review the configuration: You should now have three disks attached, each on a separate controller (scsi.0, scsi.1, scsi.2). This provides the maximum I/O performance.

Ensure the Power on VM after creation box is unchecked.

Click Save.

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