FlashArray-Implementation-Specialist事前に試験練習テストで使おう（最新236問題)
有効なFlashArray-Implementation-Specialist試験解答PDF一年無料更新
質問 # 23
Which FlashArray//XL DirectMemory Modules (DMMs) configuration condition is true?
- A. DMMs are required for baseline array initialization.
- B. DMMs are only compatible with //XL 170.
- C. DMMs cannot be installed in a DirectFlash Shelf (DFS).
- D. DMMs use different drive slots to regular DirectFlash modules.
正解：C
解説：
FlashArray//XL architectures offer the ability to leverage DirectMemory Modules (DMMs) to drastically accelerate read-intensive workloads. DMMs are specialized drives built on Storage Class Memory (SCM) technologies, such as Intel Optane. They act as a high-speed read cache tier, sitting seamlessly between the array's ultra-fast NVRAM (which handles incoming writes) and the standard DirectFlash Modules (which provide the bulk capacity).
Because the entire purpose of a DirectMemory Module is to provide the absolute lowest read latency possible, physical proximity to the controller's CPUs and direct access to internal PCIe lanes is mandatory. Therefore, DMMs must be installed directly into the primary FlashArray chassis in specifically designated slots.
Installing DMMs into an external DirectFlash Shelf (DFS) is strictly prohibited and physically unsupported.
Routing read-cache traffic across an external NVMe-oF (RoCE) backend fabric-even at 100GbE speeds- would introduce microsecond latency overheads that completely defeat the performance benefits of Storage Class Memory. Furthermore, DMMs share the exact same physical U.2/NVMe drive slot form factor as standard capacity DFMs (making Option C false), and they are supported across multiple array models beyond just the //XL 170 (making Option B false). An Implementation Engineer must strictly validate the chassis population rules before inserting DMMs to ensure the system recognizes the cache tier correctly upon initialization.
質問 # 24
During a hardware NDU from a FlashArray//X20R3 to an X20R4-LL (low-line) model, the Implementation Engineer encounters a failure during the power supply check. Voltage readings are correct.
What is a likely cause of this failure?
- A. Purity does NOT recognize the power supplies installed in the array.
- B. There are more than 10 drives installed in the chassis.
- C. The power cables are NOT fully seated in the array.
- D. The facility power is providing 208V instead of 120V.
正解：B
解説：
When performing a Hardware Non-Disruptive Upgrade (HWNDU) to the FlashArray//XR4 generation, Implementation Engineers must be acutely aware of power constraints. The //XR4 architecture introduced massive performance upgrades, leveraging PCIe Gen4 and newer Intel processors. Consequently, standard
//XR4 arrays strictly require high-line power (200V-240V) to operate.
However, to accommodate entry-level customers in smaller datacenters or edge locations, Pure Storage released the //X10R4-LL and //X20R4-LL ("Low-Line") models. These specific models are equipped with power supplies designed to run on standard 120V circuits.
The critical tradeoff for using 120V low-line power is a strict physical limitation on available wattage.
Because 120V circuits cannot deliver the peak wattage required to spin up a fully populated chassis while driving the Gen4 compute overhead, the //X10R4-LL and //X20R4-LL strictly support a maximum of 10 capacity drives (a single data pack) in the chassis.
If an Implementation Engineer is upgrading an older //X20R3 that had 20 drives (which was previously supported on low-line power due to lower CPU overheads) to an //X20R4-LL, the pre-flight power supply validation script will intentionally fail. The array detects that the 120V supplies cannot safely support the 20 physical drives currently seated in the chassis. To resolve this, the customer must either provide 208V+ high- line power and use standard R4 power supplies, or migrate the excess capacity to an external DirectFlash Shelf (which has its own independent power).
質問 # 25
An Implementation Engineer is performing a hardware NDU from a fully populated FlashArray//X90R3 to a FlashArray//XL that already contains 20 DFM-Ds. The drive transfer is complete, and the //XL is still in SPM (Shelf Personality Mode).
What is the next step the Implementation Engineer should take to continue the upgrade?
- A. Hot swap and move each DMM into any open //XL slot without evacuation.
- B. Evacuate and remove each DMM one-by-one, then set aside.
- C. Run the purehw dmm migrate command to transfer cache state to the //XL.
- D. Evacuate DMMs as a data pack, then install into any open slot in the //XL.
正解：B
解説：
Upgrading from a fully populated FlashArray//X90 R3 to a FlashArray//XL introduces a unique set of hardware migration challenges. To facilitate this massive transition, Pure Storage utilizes a feature called Shelf Personality Mode (SPM). In SPM, the legacy //X90 controllers temporarily act as a "dumb" NVMe-oF expansion shelf attached to the new //XL controllers, allowing the capacity drives to be transparently migrated without external swing hardware.
However, DirectMemory Modules (DMMs)-which are high-speed Storage Class Memory (SCM) drives used strictly for read caching-are handled differently than standard capacity DirectFlash Modules (DFMs).
DMMs do not hold persistent, uniquely resilient user data; they hold a volatile copy of hot read blocks.
While the system is still operating in Shelf Personality Mode, the official Hardware NDU procedure dictates that the Implementation Engineer cannot simply yank the DMMs out, nor can they be migrated collectively as a "data pack." Instead, the engineer must evacuate and remove each DMM one-by-one, and set them aside
. By initiating a manual evacuation on a DMM, Purity gracefully flushes the read cache mapping for that specific module. Once fully evacuated, the drive is safely removed from the legacy //X90 chassis. After the HWNDU is completely finished and the //XL is operating independently, the engineer can then re-insert those compatible DMMs into specific designated slots (typically slots 20-39) on the new //XL chassis to rebuild the cache tier.
質問 # 26
What is the maximum number of SAS shelves supported for FlashArray//XL?
- A. 0
- B. 1
- C. 2
正解：A
解説：
The FlashArray//XL supports 0 (zero) SAS expansion shelves for permanent capacity.
Architecture: The FlashArray//XL is architected exclusively for NVMe storage media. Its backend connectivity utilizes 100GbE RoCE (RDMA over Converged Ethernet) to connect to DirectFlash Shelves (DFS). It does not possess the legacy SAS controllers or ports required to drive SAS expansion shelves.
Migration Exception: While a "SAS Swing Shelf" (containing legacy SSDs from an older array) might be temporarily attached during a specific Data-in-Place upgrade migration scenario, this is a transient state. In terms of supported operational configuration for storage capacity, the limit is zero. The platform relies entirely on DirectFlash Modules in the chassis and external DirectFlash Shelves.
Contrast: Older generations (FlashArray//M, FlashArray//X R1/R2) supported SAS shelves, but the //XL platform eliminates this protocol entirely in favor of end-to-end NVMe.
質問 # 27
An Implementation Engineer completes an installation running 6.x and needs to log back into the array to run final health checks.
After rebooting the controllers, which user account should the Implementation Engineer use to log in?
- A. pureeng
- B. puresetup
- C. pureuser
- D. root
正解：C
解説：
During the initial deployment of a Pure Storage FlashArray, the Implementation Engineer relies heavily on the puresetup account. This restricted, low-level shell is specifically engineered to handle local KVM tasks like installing the Purity operating system (pureinstall) and defining the baseline network configurations (puresetup newarray).
However, once the initialization script finishes successfully and the controllers reboot, the array transitions from an unconfigured piece of hardware into a fully functional, highly available clustered storage system. At this stage, the puresetup account has served its primary purpose.
To log back into the array via SSH or the web GUI to run final health validations (such as verifying cluster status with pureadm list or checking drive health with puredrive list), the Implementation Engineer must authenticate using the default administrative account: pureuser .
The pureuser account possesses full array administrator privileges and provides unrestricted access to the standard Purity//FA command-line interface. Using pureuser validates that the cluster's internal database is actively authenticating administrative sessions and confirms the array is ready to be handed over to the customer for production workload provisioning. (Note: After logging in as pureuser with the factory default password, a critical post-installation step is immediately changing that password to comply with the customer's security policies). The pureeng account (Option C) is a protected internal account reserved strictly for Pure Storage Support and Escalation Engineering.
質問 # 28
If a Technical Support Engineer (TSE) is not available to perform health checks after an installation, what action should the Implementation Engineer take?
- A. Verify that Remote Assist (RA) is open and update the case.
- B. Email the account team
- C. Update and close the case.
正解：A
解説：
If a Pure Storage Technical Support Engineer (TSE) is unavailable to immediately perform the remote health checks upon the completion of the physical installation, the correct procedure is to verify that Remote Assist (RA) is enabled and update the support case with this information.
Standard operating procedure dictates that the Implementation Engineer must not close the install case until the array has been health-checked and verified by Support. Closing the case (Option B) would signal that the work is complete when the critical validation step is missing, potentially leaving the customer with an unverified system. Emailing the account team (Option A) is helpful for visibility but does not advance the technical workflow required to close the loop.
By confirming RA is open (using purearray remoteassist) and documenting the active session port in the case notes, the Implementation Engineer enables the Support team to perform the health checks asynchronously as soon as a TSE becomes available. This ensures the "handshake" between the onsite engineer and the remote support team is maintained without delaying the engineer's departure from the site, while guaranteeing the array will be validated before final sign-off.
質問 # 29
What command should the Implementation Engineer run to configure a proxy?
- A. purenetwork proxy set https://yourproxyserver:1234
- B. purearray configure --proxy url https://example.proxy.server
- C. puresetup proxy https://yourproxyserver:1234
- D. purearray setattr --proxy https://yourproxyserver:1234
正解：D
解説：
For a Pure Storage FlashArray to fully utilize its predictive support capabilities, it must maintain a persistent, secure outbound connection to the Pure1 cloud infrastructure. This allows the array's Callhome Connection Manager (CCM) to transmit telemetry data, hardware alerts, and heartbeat signals. However, in many enterprise environments, storage management networks do not have direct, unfiltered access to the public internet. Instead, all outbound HTTP/HTTPS traffic must be routed through a corporate proxy server.
To facilitate this, the Implementation Engineer must configure the FlashArray to tunnel its Call Home traffic through the customer's proxy. The officially supported Purity CLI command to achieve this is purearray setattr --proxy https:// < proxy_address > : < port > .
By executing this command, the system modifies its global network attributes. Purity immediately updates the internal routing daemon, instructing it to encapsulate all outgoing Pure1 management traffic and direct it to the specified proxy IP or hostname on the designated port (e.g., port 8080 or 3128). Options B, C, and D are fabricated commands that do not exist within the Purity CLI framework. Once the proxy is set, the engineer should always validate the configuration by running purearray test phonehome to ensure the proxy is properly allowing the traffic to pass through to the Pure Storage cloud endpoints.
質問 # 30
What is the speed of the Ethernet ports to connect a FlashArray //E to a DFS?
- A. 100G
- B. 25G
- C. 40G
正解：B
解説：
FlashArray//E models utilize 25Gb Ethernet (25G) ports for connecting to DirectFlash Shelves (DFS). These 25G ports are designed to handle the high throughput demands of DFS, providing efficient data transfer between the storage array and expansion shelves. This configuration ensures optimal performance and scalability for FlashArray//E systems.
質問 # 31
What command will view NVRAM install and update status?
- A. puredrive list
- B. purehw list --all
- C. purearray list
正解：B
解説：
The command purehw list --all displays detailed hardware information, including NVRAM installation and update status on the FlashArray.
質問 # 32
An Implementation Engineer is getting ready to install four DFMs into a 16-module efficiency bundle and notices that the new modules are DFMDs while the installed modules are DFMs.
What should the Implementation Engineer do to get the array using a 20-module wide write group?
- A. Work with the account team to ship DFMs instead of the DFMDs.
- B. Install the four new DFMDs and run puredrive admit.
- C. Install the four new DFMDs, run puredrive admit and have support set the tunable puretune --set allow_dfmd_in_dfm_wwg 1 < CASE > .
- D. Insert the DFMDs into a separate swing shelf to isolate them from the DFMs.
正解：A
解説：
Understanding the strict hardware boundaries of Pure Storage capacity expansion is critical. DirectFlash Modules (DFMs) and DirectFlash Modules with Distributed NVRAM (DFMDs) are fundamentally different hardware components. Standard DFMs contain only raw NAND flash and rely entirely on centralized, dedicated NVRAM modules located in the array chassis to protect write cache. DFMDs, however, feature their own onboard non-volatile memory to distribute the cache load across the capacity drives (primarily utilized in //XL and //XR4 architectures).
Pure Storage architecture explicitly dictates that drives operating within a single efficiency bundle or Wide Write Group (WWG) must be of the exact same hardware classification to ensure predictable parity calculation, wear leveling, and cache distribution. Mixing legacy DFMs with newer DFMDs within the same
20-module write group creates a severe hardware imbalance and is a strictly unsupported configuration.
While internal engineering tunables (like those suggested in Option A) occasionally exist to force overrides in lab environments, applying them in a customer's production array to bypass physical hardware incompatibility violates all implementation best practices. The only correct and safe action for the Implementation Engineer is to halt the physical installation, flag the Bill of Materials (BOM) mismatch, and work with the account
/logistics team to RMA the DFMDs and ship the correct standard DFMs.
質問 # 33
An Implementation Engineer has installed a data pack and the list command shows the drives in "unadmitted" status. Which command should the Implementation Engineer run to complete the admission?
- A. purearray drive admit
- B. puredrive
- C. puredrive add
正解：A
解説：
When new capacity (a data pack) is physically installed into a FlashArray, the drives are detected by the system but are not automatically added to the storage pool to prevent accidental data overwrites or configuration errors. They appear in an "unadmitted" state.
To logically add these drives to the array's capacity, the Implementation Engineer must explicitly admit them.
The command to perform this action is purearray drive admit (or puredrive admit in some contexts, but purearray drive admit is the specific option provided and valid). This command triggers the Purity software to format the new drives, add them to the system's write groups, and begin rebalancing data across the expanded capacity. Without running this admission command, the drives will remain visible but unusable for storage.
=========
質問 # 34
Prior to running the puresetup newarray command, which command should an Implementation Engineer run on a new install of a FlashArray//XR4 array?
- A. purehw list
- B. cobalt_check.py
- C. hardware_check.py
- D. pureboot list
正解：B
解説：
The introduction of the FlashArray//XR4 and FlashArray//CR4 models represented a massive internal redesign for Pure Storage. Internally, this new hardware generation and its corresponding Baseboard Management Controller (BMC) architecture are codenamed "Cobalt" .
Because the Cobalt architecture leverages a highly complex, modular PCIe Gen4 midplane and swappable OCP 3.0 networking cards, validating that all internal hardware is seated correctly before logically forming the cluster is mandatory. If an NVRAM module, direct-attach backend cable, or OCP card is inserted into the wrong slot, the Purity operating system will fail to map its internal topology correctly, leading to unstable initialization.
To prevent this, Pure Storage engineering developed a specialized pre-flight validation script specifically for the //XR4 and //CR4 platforms. Before an Implementation Engineer executes the puresetup newarray command to define the management IPs and form the cluster, they must log into the local KVM console as the puresetup user and run cobalt_check.py .
This Python script interrogates the motherboard, scans the physical PCIe lanes, verifies the OCP module firmware, and checks the chassis topology against the expected Bill of Materials (BOM). If the script returns a clean "PASS," the engineer is cleared to run puresetup. (Note: Older generations like the //XR3 used a generic hardware_check.py script, but cobalt_check.py is the specific, required tool for the //XR4 family).
質問 # 35
An Implementation Engineer performs a controller upgrade. What is the command to check I/O health?
- A. pureport list --initiator
- B. purehost monitor --balance
- C. purehost list --all
正解：B
解説：
The command to check I/O health and validate connectivity after a controller upgrade is purehost monitor -- balance .
Following an upgrade (especially after a controller reboot or failover/giveback), it is essential to verify that the host Multipath I/O (MPIO) drivers have re-established connectivity to all paths.
* purehost monitor : Displays real-time performance statistics (IOPS, Bandwidth, Latency) for connected hosts.
* --balance : This specific flag breaks down the metrics per initiator (HBA port) for each host.
* Why it's used: An Implementation Engineer uses this to look for "imbalanced" flow. If one initiator shows high IOPS and another shows zero, it indicates a dead path, a zoning issue, or an MPIO driver that failed to recover the path to the upgraded controller. Options A and B provide static configuration lists (mappings and WWNs) but do not show live I/O flow, making them insufficient for health monitoring.
質問 # 36
An Implementation Engineer is assigned to install a 4X Module 9.1 TB Conversion Kit in a Flash Array Chassis. Why are there only four Direct Flash Modules?
- A. To replace a missing shipment.
- B. To widen an existing write group.
- C. To fill out enclosure bays.
正解：B
解説：
A "4X Module" kit is specifically designed to widen an existing write group (RAID set).
Write Group Geometry: In standard FlashArray//X configurations, DirectFlash Modules (DFMs) operate in "Write Groups" (typically 10 modules wide for a standard data pack). However, to offer more flexible entry points or capacity expansion options, Pure Storage allows configurations that start with smaller write groups (e.g., 6 modules).
Widening: When a customer wants to expand capacity or performance on these smaller configurations without adding a full new 10-pack, they can purchase a widening kit (in this case, 4 modules).
Process: The Implementation Engineer installs these 4 modules into the empty slots. The Purity operating system then logically integrates these new drives into the existing narrow write group, "widening" it to the standard width (e.g., 6 + 4 = 10). This operation redistributes parity and data across the full set of 10 drives, improving performance and efficiency.
質問 # 37
An Implementation Engineer is upgrading a FlashArray//X50R3 to an //X50R4. The array has 10 SAS and 10 DirectFlash modules in the chassis. What type of controller is required to complete the upgrade?
- A. FLASHARRAY//XC50 R4
- B. FLASHARRAY//XC50 R4, SE
- C. FLASHARRAY//XC50 R4, NS
正解：A
解説：
When performing a controller upgrade (Non-Disruptive Upgrade) from an //X50R3 to an //X50R4, the specific hardware configuration of the source array dictates the target bill of materials. The presence of SAS drives in the chassis indicates that the source is a legacy or transitional configuration, as the standard //X R4 platform is optimized for end-to-end NVMe (DirectFlash).
However, the question asks for the specific controller SKU required. In Pure Storage nomenclature for upgrades, the standard controller replacement part is typically the base model code, here FLASHARRAY
//XC50 R4 .
The "XC" designation often refers to the controller component itself in upgrade kits. While special considerations apply to SAS media (which are usually phased out or require specific handling during R4 upgrades since R4 natively drops legacy SAS support on the motherboard), the controller part number itself remains the standard R4 SKU (Option C). Options like "SE" or "NS" (often denoting specific encryption or networking variants) are not the standard identifiers for the base controller upgrade in this context.
=========
質問 # 38
......
Pure Storage Certified FlashArray Implementation Specialist無料更新認定サンプル問題：https://jp.fast2test.com/FlashArray-Implementation-Specialist-premium-file.html
試験本場前にトレンドなPure Storage FlashArray-Implementation-SpecialistのPDF問題集を試そう：https://drive.google.com/open?id=1FjmmlLvP0WHWJH6jtNJnCaEa80Cx6dW-