DES-1111 Sample Questions & Answers

This is the optimal combination. TimeFinder SnapVX provides highly space-efficient, pointer-based snapshots for frequent local recovery points against logical corruption. SRDF/S (Synchronous) provides zero data loss (RPO=0) remote replication for disaster recovery. Together, they form a comprehensive business continuity solution that addresses both requirements.

SRDF/Star is the correct topology. It allows a primary site (A) to replicate to a secondary site (B) using one SRDF mode (e.g., synchronous) while also replicating to a tertiary site (C) using another SRDF mode (e.g., asynchronous). In this configuration, Site B also replicates to Site C, providing protection against a failure at Site A. This 'star' configuration with a primary workload site and two remote sites meets the requirements perfectly.

In SRDF/A, the 'Consistent' state means that the R2 side has a consistent copy of the data, but there might still be delta sets that have been captured on the R1 side and are currently in transit over the network. The SRDF session cannot be dissolved until all captured data has been successfully transmitted and applied to the R2 side. The presence of these in-transit delta sets will cause the dissolve operation to fail.

While bandwidth is important, the most critical and restrictive requirement for SRDF/Metro is round-trip network latency. To maintain synchronous writes and provide a single LUN image across both sites, the latency must be very low, typically under 10ms round-trip time (RTT), with under 5ms being the strong recommendation for performance. The 50km distance is within the supported range, but if the network path introduces higher latency, the implementation will fail or perform poorly.

For SRDF/S, every host write must be acknowledged by the remote array before being acknowledged back to the host. Therefore, the network must be able to handle the peak write workload. The two most critical metrics are the peak write throughput (MB/s) to determine bandwidth, and the peak write I/O operations per second (IOPS) to understand the number of round trips and the impact of latency. Read operations are not replicated and are therefore irrelevant for sizing the replication link.

With a vVols implementation, storage operations are VM-centric and managed through the vSphere client. When a snapshot is requested in vCenter, the VASA (vSphere APIs for Storage Awareness) provider communicates the request to the PowerMax array, which then uses its native TimeFinder SnapVX technology to create a highly efficient, offloaded snapshot of the necessary vVols. The storage administrator does not need to interact directly with the array.

Deduplication works by identifying and eliminating redundant blocks of data. Encrypted data has high entropy, meaning blocks appear unique even if the underlying data is identical. This prevents the deduplication engine from finding matches, resulting in a ratio near 1:1. Compression, which works on patterns within individual blocks, may still yield some results (though often limited on encrypted data), but deduplication will be almost completely ineffective.

Open Replicator is designed for data mobility and migration between PowerMax/VMAX arrays and supported third-party storage arrays. It can perform a 'hot pull' or 'hot push' of data while the application remains online. After the initial synchronization, only a very brief cutover period is required to switch the host's access to the new PowerMax array, minimizing downtime.

This statement is true. One of the powerful features of SnapVX is its ability to link a single source snapshot to up to 1024 different target devices. Each link provides a unique, read/write, point-in-time copy that can be used for development, testing, or analytics without impacting the source or other linked copies. This is highly efficient as new writes are only stored for the specific target being modified.

The Storage Resource Pool (SRP) is the fundamental concept in PowerMax Virtual Provisioning. It abstracts the underlying physical disks into a single large pool of capacity. All thin devices are then provisioned from this SRP, which automatically handles data layout and striping across all drives to ensure balanced performance and utilization, greatly simplifying storage administration.