EMC DEE-1111 Practice Test Questions Answers

A noisy neighbor issue occurs when one or more applications consume more resources than expected, causing performance degradation for other applications. This can affect the SL compliance of a storage group, as the service level defines the expected response time and performance for the applications in that group. If a noisy neighbor consumes too much cache, bandwidth, or CPU cycles, it can cause the SL compliance to drop below the target level. Therefore, answer A is correct.

B, C, and D are incorrect because they are not likely to cause SL compliance impact for a storage group. Queue depth full event (B) is a host-side issue that occurs when the host queue depth is too low or the host I/O rate is too high, causing the host to stop sending I/O requests to the array. Host queue depth setting © is also a host-side parameter that determines how many I/O requests can be queued by the host. Performance thresholds (D) are user-defined values that trigger alerts when certain metrics exceed or fall below the specified levels. None of these factors affect the SL compliance of a storage group on the array.

The NDM Updates feature should be used to complete the migration and address the client’s concern. The NDM Updates feature is designed to help automate the process of moving applications across arrays requiring a short application downtime. It allows application migration from a VMAX (5876) array to a VMAX3 (5977), VMAX All Flash (5978), or PowerMax (5978) array1. It supports pre-sync data between arrays and then schedule downtime to do the cutover1. References: Dell EMC PowerMax and VMAX: Non-Disruptive Migration Best Practices and Operational Guide

The symstar halt command is used to write disable devices and synchronize SRDF data to remote sites in an SRDF/Star configuration. This command ensures that all sites have a consistent copy of data before switching the workload site from one site to another. Therefore, the symstar halt command should be used before the workload switch in case of a disaster at the workload site of an SRDF/Star configuration1

The user has been assigned the RemoteRep role only. The RemoteRep role allows users to create, manage, and delete SRDF device pairs, as well as view array information, masking objects, device information, and RBAC rules2. However, it does not allow users to create and delete SRDF groups, which requires the StorageAdmin role. Therefore, answer C is correct.

A, B, and D are incorrect because they do not match the user’s profile. SecurityAdmin (A) role allows users to manage security settings such as authentication methods, certificates, RBAC rules, and audit logs2. Auditor (B) role allows users to view array information and audit logs only2. LocalRep (D) role allows users to create, manage, and delete TimeFinder SnapVX sessions from a source device2. None of these roles allow users to create and delete SRDF device pairs.

The correct sequence of steps to configure and bring up an SRDF/Star environment is as follows:

Verify SRDF/Star control host connectivity and array settings. This step involves checking the network connectivity between the control host and the three arrays involved in the SRDF/Star configuration, as well as verifying the array settings such as RDF mode, RDF consistency, and RDF emulation. The control host is the host that runs the Solutions Enabler SYMCLI commands to manage the SRDF/Star configuration.The three arrays are the primary array, the secondary array, and the tertiary array.1

Enable SRDF/Star configuration. This step involves enabling the SRDF/Star feature on the primary array using the symstar enable command. This command also creates a STAR control device group on the primary array, which contains a single device that acts as a control point for the SRDF/Star configuration.The STAR control device group must have a unique name and number across all arrays.1

Add BCV devices to the SRDF/Star configuration. This step involves adding Business Continuance Volume (BCV) devices to the STAR control device group on the primary array using the symstar add bcv command. BCV devices are local copies of data that can be used for backup, restore, or testing purposes. BCV devices are required for SRDF/Star configurations to enable fast recovery in case of a disaster.The number of BCV devices must match the number of R1 devices in the SRDF/Star configuration.1

Create an SRDF/Star composite group and options file. This step involves creating an SRDF/Star composite group on the control host using the symstar create command. An SRDF/Star composite group is a logical grouping of devices that span across three arrays and have different SRDF roles: R11, R21, and R22. An R11 device is an R1 device that is paired with another R1 device in a different SRDF group. An R21 device is an R2 device that is paired with another R1 device in a different SRDF group. An R22 device is an R2 device that is paired with another R2 device in a different SRDF group.The symstar create command also creates an options file that contains various parameters for the SRDF/Star configuration, such as RDF mode, RDF consistency, RDF emulation, and bias setting.1

Perform the symstar setup operation and create composite groups on target sites. This step involves performing the symstar setup operation on the control host using the symstar setup command. This command establishes the SRDF/Star configuration by creating RDF pairs between devices in different arrays, creating RDF groups on each array, creating composite groups on each array, and synchronizing data across all devices.The symstar setup command also creates composite groups on the secondary and tertiary arrays using the same name and number as the composite group on the primary array.1

References:

Dell EMC Solutions Enabler 9.2 SRDF Family CLI User Guide