DES-1241 Specialist - Platform Engineer, PowerStore Version 1.0 Practice Questions

This is the fundamental distinction. CRUs, such as power supplies, fans, and drives, are designed for simple, often tool-less, and non-disruptive replacement by a customer or local IT staff. FRUs, such as nodes, embedded modules, or the chassis itself, are more complex components whose replacement requires specialized procedures and training, and must be performed by authorized Dell service personnel to avoid system damage or data loss.

The management network is essential for system administration, monitoring, and accessing the PowerStore Manager UI.

The storage network is used for host data access via protocols like iSCSI.

The replication network is used for data replication between PowerStore systems for disaster recovery or data mobility.

According to Dell PowerStore documentation, the system health LED uses a color code to indicate overall status. Solid blue or solid green indicates normal operation. A blinking amber or solid amber light signifies a hardware fault. This could be a failed drive, power supply, fan, or other component. The engineer's next step should be to check PowerStore Manager for specific alerts to identify the failed component.

This is false. Adding an expansion enclosure is a non-disruptive hardware upgrade procedure. The new enclosure can be racked and cabled to the base enclosure's back-end SAS ports while the cluster is running. Once cabled, the system will automatically detect the new hardware, and the new drives can be added to the storage pool through PowerStore Manager without any downtime.

Official hardware specifications, including detailed power and environmental requirements, are always located in the product's technical documentation. The Hardware Information Guide provides a comprehensive overview of specifications, while the Installation and Service Guide contains the necessary details for planning a physical installation. These documents are the authoritative source for this information, found on the Dell Support site via the PowerStore Info Hub.

This is the standard best practice for high availability. By distributing the connections from each node across both redundant fabrics (Fabric A and Fabric B), the system can tolerate the failure of an entire switch, a fabric, or a node without losing connectivity. If all of Node A's ports went to Fabric A, a failure of Fabric A would completely isolate Node A from the hosts.

The root cause is an MTU mismatch. The hosts and PowerStore are sending large 9000-byte jumbo frames, but the switches in the middle are configured for a standard 1500-byte MTU. This forces the switches to drop the oversized packets, leading to intermittent connectivity loss and retransmissions, especially under high load. Step E, reviewing the switch port MTU configuration and discovering the mismatch, is the step that directly identifies this root cause.

The correct approach is to isolate the faulty node and perform a targeted CRU (Customer Replaceable Unit) replacement. Since node A is healthy and serving all I/O, the cluster is not down. The documented procedure for replacing a component like a DIMM in a single node involves safely powering down only that node while the peer node remains active. This minimizes disruption. A full cluster power-down is unnecessary and causes a complete outage. Forcing the node out of service mode is risky and does not address the underlying hardware fault. A full node replacement (FRU) is premature without first attempting the CRU replacement.

High latency between nodes is often caused by physical layer issues on the ICD network. Checking cables for damage, reseating them, and ensuring the correct SFP/QSFP modules are used and healthy is a primary diagnostic step.

The svc_network_diag service script is a specific tool designed to diagnose network issues, including latency, on the internal PowerStore networks like the ICD. This provides detailed diagnostic data beyond what the pre-upgrade health check shows.

This is the correct and most efficient method. By creating a single LACP bond (Link Aggregation) with multiple ports and configuring the corresponding switch ports as a trunk (allowing multiple VLANs), you achieve both high availability and the required network segmentation. PowerStore Manager can then tag the different network types (management, storage, replication) with their specific VLAN IDs, directing traffic over the trunked LACP bond to the correct network segment.