D-PST-DY-23 Sample Questions & Answers

PowerStore's file-level quota system is the correct feature for this scenario. A Tree Quota can be applied to a specific directory (folder) within a file system. By setting a hard limit of 5 TB, storage usage is capped. Setting a soft limit of 4.5 TB allows the system to generate alerts and notifications when this threshold is crossed, without immediately blocking new writes. This combination perfectly addresses both the hard cap and the early warning notification requirement.

The native 'Import External Storage' feature within PowerStore is specifically designed for non-disruptive, agentless block migrations from supported arrays like the VNX2. The process works by establishing paths to both the source and target arrays from the host, synchronizing the data in the background, and then performing a cutover that simply involves a multipathing I/O path change, which is transparent to the application and incurs no downtime.

PowerStore snapshots use redirect-on-write technology. The initial snapshot consumes minimal space. However, as data on the source volume is changed or overwritten, the original data blocks are preserved for the snapshot, consuming capacity. Therefore, snapshot consumption is directly proportional to the data change rate (churn) on the source volume. A high churn rate will cause snapshot space usage to grow rapidly.

When a host has multiple paths to the same storage LUN, a multipathing driver is required to manage these paths for load balancing and failover. On Windows Server, this is provided by the native Multipath I/O (MPIO) feature. Without MPIO installed and configured for iSCSI devices, the host will only use the first path it discovers. Installing MPIO and adding support for iSCSI devices allows the host to see all paths and use them according to the configured load balancing policy (e.g., Round Robin, Fail Over Only).

A zero Recovery Point Objective (RPO) means that no data loss is acceptable. This can only be achieved with synchronous replication. In this mode, a write I/O from the host is not acknowledged as complete until it has been successfully written to both the primary PowerStore array and the remote PowerStore array. This guarantees that both sites are always in sync, resulting in an RPO of zero. This mode requires a high-quality, low-latency network link, which the scenario describes.

To enable Active Directory authentication for SMB shares, the NAS server must be joined to the AD domain, just like a Windows server. During the NAS server creation wizard in PowerStore Manager, you must provide the FQDN of the Active Directory domain and the credentials of an AD account that has sufficient privileges to create and join computer objects to the domain. PowerStore will then use these credentials to create a computer account for the NAS server in AD.

A single protection policy in PowerStore can contain a maximum of four snapshot rules OR one replication rule, but not both simultaneously in that quantity. A policy can have up to four snapshot rules for local protection or one replication rule for remote protection. This limitation ensures clarity and prevents overly complex policies.

Adding an expansion enclosure to a running PowerStore appliance is a non-disruptive update (NDU), but it must be done correctly. The proper procedure involves using PowerStore Manager (or CLI) to place the appliance into service mode. This prepares the system for the hardware change. Once in service mode, the new enclosure can be cabled and powered on. After the system recognizes the new hardware, you can exit service mode, and the new capacity will be available.