あなたへの紹介よりあなたに自分で体験させたほうがいいと思います。弊社のXhs1991で無料でPure StorageのFlashArray-Storage-Professionalソフトのデモを直ちにダウンロードできます。我々豊富な経験があるグループはあなたに一番信頼できるPure StorageのFlashArray-Storage-Professional試験のための資料を提供いたします。我々係員は全日24時間で待っていますから、何か疑問があれば、お問い合わせを期待しています。
| Certification Vendor: | Pure Storage |
|---|---|
| Exam Name: | Pure Certified FlashArray Storage Professional |
| Exam Number: | FASP |
| Real Exam Qty: | 80 |
| Available Languages: | English |
| Exam Format: | Multiple Choice |
| Related Certifications: | Pure Storage FlashArray Architect Professional Pure Storage FlashArray Support Specialist Pure Storage FlashArray Implementation Specialist |
| Exam Duration: | 120 minutes |
| Exam Price: | $300 USD |
| Certificate Validity Period: | 3 years |
| Sample Questions: | Pure Storage FlashArray-Storage-Professional Sample Questions |
| Exam Way: | Online, proctored |
| Pre Condition: | Recommended for new and experienced IT professionals. |
| Official Syllabus URL: | https://academy.purestorage.com/student/page/2164505-certification-fasp |
>> FlashArray-Storage-Professional受験料過去問 <<
現在、どの領域にでも勉強して努力する必要があります。IT業界でも同じです。Pure Storageに関する仕事をしている人たちはさまざまな認証試験に参加して自分の知識を補充し、よく働く必要があります。FlashArray-Storage-Professional試験に合格するのはあなたの能力を証明して、質素を高めることができます。
| トピック | 出題範囲 |
|---|---|
| トピック 1 |
|
| トピック 2 |
|
| トピック 3 |
|
| トピック 4 |
|
| トピック 5 |
|
質問 # 56
A storage administrator is troubleshooting multipathing issues.
What is the CLI command that allows the administrator to sample the I/O balance information at a consistent interval?
正解：C
解説：
Command Purpose: The purehost monitor command is the primary tool in the Pure Storage CLI for observing real-time performance and connectivity health from the perspective of the hosts connected to the FlashArray.
The --balance Flag: When the --balance flag is added, the output shifts from general performance (IOPS, bandwidth, latency) to showing how I/O is distributed across the available paths (controllers and ports). This is critical for identifying "unbalanced" loads, which usually point to misconfigured MPIO (Multi-Path I/O) on the host side (e.g., a host only using one controller's ports).
Interval vs. Repeat:
The --interval flag specifies the time in seconds between each sample. In option C, --interval 15 tells the array to refresh the data every 15 seconds.
The --repeat flag (seen in option A) is used to limit the total number of samples taken before the command exits. However, in standard troubleshooting, the administrator typically wants a consistent stream of data until manually stopped (Ctrl+C).
--resample (seen in option B) is not a valid flag for the purehost monitor command in Purity.
Best Practice: When troubleshooting multipathing, Pure Storage recommends monitoring the balance to ensure that the "Relative I/O" percentage is roughly equal across all active paths. Large discrepancies often indicate that the host's MPIO policy is set to "Failover Only" instead of the recommended "Round Robin" or "Least Queue Depth."
質問 # 57
A FlashArray//C R4 has ports Eth0 and Eth1 connected to a switch using 100Gb/s Direct Attach Copper (DAC) cables. The administrator is unable to configure these ports for iSCSI services.
Why is this occurring?
正解：C
解説：
On the Pure Storage FlashArray//C R4 (as well as the //XL and //E series architectures), the onboard 100Gb/s Ethernet LOM (LAN on Motherboard) ports-specifically eth0 and eth1-are purpose-built and strictly reserved for DirectFlash Shelf (DFS) connectivity.
Pure Storage uses these dedicated 100GbE ports to run NVMe over RoCE (RDMA over Converged Ethernet), effectively extending the array's internal PCIe backplane to additional backend storage shelves. Because these ports are hardcoded exclusively for back-end shelf expansion, the Purity operating environment fundamentally restricts them from being assigned IP addresses for front-end host I/O services. Therefore, an administrator will be completely unable to configure eth0 or eth1 for iSCSI, NVMe/TCP, or Replication. Front-end iSCSI services must instead be configured on the dedicated Host I/O PCIe cards (which typically appear as eth2, eth3, etc., depending on the slot configuration).
Here is why the other options are incorrect:
The ports are designated for Management connectivity (A): On modern FlashArrays, dedicated management ports are typically out-of-band 1GbE/10GbE RJ45 ports (often designated as vir0 or specific management eth ports on older hardware), not the ultra-high-speed 100Gb/s QSFP28 ports.
The DAC cables are not compatible with the array's ports (B): While incompatible cables can prevent a link from coming up physically, the specific reason the administrator cannot configure the ports for iSCSI in the Purity software is due to the port's hardcoded role (DFS), not the physical cable type.
質問 # 58
An on-premises mediator has been deployed. When a pod is stretched and replicating, it is observed that the pod is utilizing the Pure1 Cloud Mediator and not the on-premises mediator.
Why is the on-premises mediator NOT being used by this new pod?
正解：A
解説：
ActiveCluster Mediator Logic: In an ActiveCluster setup, the Mediator is a lightweight component (an "arbiter") that resides at a third site (failure domain). Its job is to break the tie in a "split-brain" scenario (when arrays lose connectivity with each other) to determine which array stays online.
Default Behavior: By default, every FlashArray is configured to use the Pure1 Cloud Mediator. This is a managed service provided by Pure Storage that requires no local infrastructure other than internet access from the array controllers.
On-Premises Mediator Deployment: Organizations that cannot use the Cloud Mediator (due to "dark site" security requirements or lack of reliable internet) can deploy the Pure Storage On-Premises Mediator as a small OVF/VM template.
Configuration at the Pod Level: Simply deploying the On-Premises Mediator VM and connecting the arrays to it at the array level is not enough for existing or new pods to switch automatically. In Purity, the mediator preference is a per-pod attribute.
When a pod is created or stretched, it inherits the default (Cloud).
To use the local mediator, the administrator must explicitly configure the pod to point to the On-Premises Mediator's IP or DNS name. This is done via the CLI using purepod setattr --mediator <address> <pod-name> or through the Pod settings in the GUI.
Why Option C is incorrect: While an A record is necessary for DNS resolution, the prompt implies the mediator is already "deployed" and available. The most common reason it isn't being used is simply that the pod hasn't been told to look there instead of the default Cloud option.
質問 # 59
An administrator is setting up FA File using the FlashArray GUI. The company is an NFS only shop and needs to configure their remote user authentication.
Which of the following GUI locations should the administrator use to configure access?
正解：A
解説：
For FlashArray File Services (FA File), user authentication and mapping depend on the storage protocol being used. In an NFS-only environment, remote user authentication (resolving UNIX UIDs and GIDs to actual usernames and managing access) is typically handled via LDAP or NIS.
To configure this integration in the Purity GUI, the storage administrator must navigate to Settings > Access > Directory Services. This specific section allows the FlashArray to connect to a centralized directory server (such as OpenLDAP or even Active Directory providing LDAP services) to pull the necessary UNIX user and group attributes required for NFS file permissions to function properly.
Here is why the other options are incorrect:
Settings > Access > Create Active Directory Account (A): This specific menu path is used strictly for configuring native Active Directory (AD) computer accounts and joining the domain to support the SMB (Server Message Block) protocol. Since the scenario explicitly states the company is an "NFS only shop," configuring an SMB AD account is not the correct step.
Settings > Access > File System (C): While you manage file-level exports and policies within the Purity file interface, the global configuration for remote user authentication and directory server integration lives under the dedicated Directory Services pane.
質問 # 60
In reviewing space metrics via the Pure Management GUI, a storage manager notices the total reduction rate is much higher than the Data Reduction Rate (DRR).
What is the reason for this?
正解：B
解説：
Understanding Data Reduction Rate (DRR): DRR is a measure of the effectiveness of Purity's deduplication and compression algorithms. It compares the amount of data written by the host to the amount of physical space actually occupied on the flash media after these processes have occurred.
Calculation: $\text{DRR} = (\text{Deduplication} \times \text{Compression})$.
Understanding Total Reduction: The Total Reduction metric is a broader "efficiency" value. It represents the ratio of the Total Provisioned (logical) space to the Physical space used.
The "Thin Provisioning" Factor: The primary difference between these two numbers is Thin Provisioning.
FlashArrays are 100% thin-provisioned by default. If a customer creates a 100TB volume but the host only writes 1TB of data, the "Total Reduction" will be massive because it counts all that unwritten, "virtual" space as "saved." The DRR, however, only looks at the 1TB that was actually written and calculates how well it was compressed and deduped.
Why Option C is incorrect: Both metrics generally account for the efficiency of snapshots. However, snapshots contribute to DRR through deduplication (since they share blocks with the source volume). The massive gap between DRR and Total Reduction is almost always mathematically attributed to the "unwritten" space provided by thin provisioning.
Key Takeaway: If your DRR is 5-to-1 but your Total Reduction is 50-to-1, it means your data is compressing/deduping well, but you have also provisioned a significant amount of volume space that hasn't been written to yet.
質問 # 61
......
FlashArray-Storage-Professional日本語的中対策: https://www.xhs1991.com/FlashArray-Storage-Professional.html