多くの人は、Pure StorageインターネットでFlashArray-Storage-Professional学習準備を購入するとプライバシーが明らかになることを心配することがよくあります。 一部の人々は、一部のWebサイトPure Certified FlashArray Storage Professionalで製品を購入した後、匿名のSMS広告やテレマーケティングに悩まされることがよくあります。 しかし、プラットフォームでFlashArray-Storage-Professionalテスト資料を購入すると、このような状況Pure Certified FlashArray Storage Professionalは決して起こりません。 ここでは、顧客のプライバシーと購入情報をしっかりと保護し、顧客情報の開示は行わないことを厳soleに約束します。 FlashArray-Storage-Professional準備トレントをFlashArray-Storage-Professional購入すると、購入情報を入力するJapancert専任の営業担当者がいます。 取引終了後、すべての顧客情報を保持および破棄する専門スタッフもいます。
| Certification Vendor: | Pure Storage |
|---|---|
| Exam Name: | Pure Certified FlashArray Storage Professional |
| Exam Number: | FASP |
| Related Certifications: | Pure Storage FlashArray Support Specialist Pure Storage FlashArray Implementation Specialist Pure Storage FlashArray Architect Professional |
| Real Exam Qty: | 80 |
| Exam Price: | $300 USD |
| Exam Format: | Multiple Choice |
| Certificate Validity Period: | 3 years |
| Available Languages: | English |
| Exam Duration: | 120 minutes |
| 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試験復習 <<
あなたは弊社の商品を買ったら一年間に無料でアップサービスが提供されたFlashArray-Storage-Professional認定試験に合格するまで利用しても喜んでいます。もしテストの内容が変われば、すぐにお客様に伝えます。弊社はあなた１００％FlashArray-Storage-Professional合格率を保証いたします。
| トピック | 出題範囲 |
|---|---|
| トピック 1 |
|
| トピック 2 |
|
| トピック 3 |
|
| トピック 4 |
|
| トピック 5 |
|
質問 # 33
What happens when you demote the original source pod?
正解：A
解説：
ActiveCluster and Pod Roles: In a Pure Storage ActiveCluster or ActiveDR environment, a Pod is a management container for volumes. To move workloads or perform a planned failover between two arrays, you use the Promote and Demote commands.
The Reversal Process: When you have two pods in a replication relationship (Source and Target), data flows from the Promoted (Active/Source) pod to the Demoted (Passive/Target) pod.
When you Demote the current source, it transitions from a "read-write" state to a "read-only" (passive) state.
If the other pod in the pair is then Promoted, Purity automatically intelligently reverses the direction of replication. The array that was previously receiving data now begins sending incremental updates back to the original source.
Continuous Protection: This design ensures that you don't have to manually tear down and recreate replication schedules every time you switch production sites. The system tracks the metadata changes and ensures that only the delta (changed blocks) are sent in the new direction.
Why Option C is incorrect: If replication were simply paused, the two sites would quickly drift out of sync, making it impossible to fail back without a full baseline resync.
Why Option A is incorrect: Demoting a pod does not delete any data; it simply changes the access characteristics and replication role. The data remains fully intact on the storage media.
質問 # 34
What is the best practice for configuring VMFS UNMAP for ESXi 6.7 or later?
正解：A
解説：
What is UNMAP?: UNMAP (SCSI command 0x42) is the mechanism that allows a host (like ESXi) to inform the storage array that specific blocks of data are no longer in use (e.g., after a VM is deleted or moved). This is critical for Pure Storage because it allows the array to reclaim that space and maintain high data reduction ratios.
Evolution in ESXi: In versions prior to 6.5, UNMAP was a manual process executed via the CLI. Starting with ESXi 6.7, VMware introduced Automatic Space Reclamation, which runs in the background.
The Pure Storage Recommendation: Pure Storage recommends setting the reclamation priority to Auto with Low Priority.
Low Priority: This ensures that the UNMAP commands are sent to the FlashArray at a steady, manageable rate (roughly up to 25 MB/s to 100 MB/s depending on the Purity version). Because FlashArrays are built on a high-performance metadata engine, "Low Priority" is more than sufficient to keep up with even high-churn environments without causing any contention for active application I/O.
Why avoid High Priority (Option B)?: Setting it to high priority or using a fixed high-burst rate can lead to "bursty" SCSI traffic. While the FlashArray can handle the load, it is considered a best practice to keep background maintenance tasks like space reclamation at a lower priority to ensure the "Big Three" (latency, bandwidth, IOPS) for production workloads remain optimized.
Verification: You can verify that UNMAP is working by looking at the Data Reduction metrics in the Purity GUI or Pure1. If the "Thin Provisioning" or "Reclaimed" numbers are increasing after file deletions, the host is correctly communicating its freed space to the array.
質問 # 35
What is indicated by the Fibre Channel (FC) hosts in the following output?
正解：C
解説：
Purity Active/Active Architecture: Pure Storage FlashArrays use an Active/Active controller architecture. Under normal operating conditions, both controllers (CT0 and CT1) are healthy and independently serve I/O through their respective physical Fibre Channel ports.
The Scenario (Controller Failover): The output provided shows that the host initiator is seeing target WWNs associated with both CT0 and CT1, but the "Target" column indicates they are all being reached via the paths currently managed by one controller or through a specific failover mechanism.
Virtual WWNs and Transparency: In a controller failover or maintenance scenario, Pure Storage utilizes a feature where the WWNs of the "failed" or "offline" controller are logically moved to or presented by the "surviving" controller. This ensures that the host's MPIO (Multi-path I/O) software does not see a permanent "Path Down" error for those specific WWNs, but rather a transition.
Analyzing the Output: When you see CT1 port WWNs (e.g., 52:4A:93:78:55:2D:E3:10) appearing in the connectivity table in a way that implies they are being routed or presented through the physical infrastructure of CT0, it indicates that the array is in a state where one controller is assuming the identity/connectivity of the other. This is a key troubleshooting indicator that the array is likely undergoing a controller reboot, a Purity upgrade, or has experienced a controller hardware failure.
Why A and B are incorrect: * Option A: Multipathing software on the host handles path failures, but it wouldn't cause the array to report WWNs in this specific "cross-presented" manner in a connectivity log.
Option B: If there were a total outage on CT1 without this presentation mechanism, the paths would simply show as "Disconnected" or be missing from the initiator's view entirely.
質問 # 36
If an NFS client can mount the FA File export shares with the IP address, but not the fully qualified domain name, what is most likely causing the issue?
正解：A
解説：
When an NFS client successfully mounts an export using the target's IP address, it proves that the fundamental network connectivity (routing, firewalls) and the storage protocol layer (NFS export policies, host access permissions) are functioning correctly.
However, if the exact same mount attempt fails when using the Fully Qualified Domain Name (FQDN) of the FlashArray file service, the issue lies entirely with name resolution. The Domain Name System (DNS) is responsible for translating human-readable FQDNs into the IP addresses required for network communication. If the client cannot reach the DNS server, or if the DNS server lacks the correct A or AAAA records for the FlashArray's file Virtual IP (VIP) addresses, the client won't be able to resolve the name to the IP, causing the mount command to fail.
Here is why the other options are incorrect:
Issue with the Active Directory (AD) controller (A): Active Directory is primarily used for directory services, user authentication, and authorization (such as mapping permissions for SMB or NFSv4). While AD environments usually include DNS, an "AD controller issue" in the context of storage protocols usually points to permission denials, not host name resolution failures. Furthermore, since the mount works via IP, basic access is already validated.
Issue with the OpenLDAP (C): Similar to AD, OpenLDAP provides directory services for user mappings (UID/GID) and authentication. It does not perform FQDN-to-IP resolution.
質問 # 37
A new array is directly connected to a host with Direct Attach Copper (DAC) cables. The link does not come up.
Which document can be used to help identify the issue?
正解：A
解説：
When physical links fail to establish-especially when using Direct Attach Copper (DAC) cables or Twinax-the most common culprit is a hardware compatibility mismatch. Pure Storage arrays have specific requirements for optics and cabling to ensure optimal signal integrity and performance.
The FlashArray Transceiver and Cable Support article (available on the Pure Storage Support portal) is the authoritative, verified resource for this scenario. It provides a comprehensive, constantly updated compatibility matrix detailing exactly which vendor DAC cables (e.g., Cisco, Brocade, Arista) and transceivers are officially validated and supported for use with specific FlashArray models and port types. If an unsupported DAC cable is used, the switch or host bus adapter (HBA) on the array might simply refuse to bring the link up.
Here is why the other options are incorrect for this specific issue:
The FlashArray User Guide (A): This guide is excellent for day-to-day administration (volume creation, host grouping, etc.) but is too broad to contain granular, constantly updating hardware compatibility matrices for specific cables.
The Port Usage and Definitions article (C): This document explains the logical and physical purpose of the ports on the back of the controllers (e.g., defining which ports are used for management, replication, or host connectivity), but it does not dictate hardware transceiver or cable interoperability.
質問 # 38
......
FlashArray-Storage-Professional日本語認定対策: https://www.japancert.com/FlashArray-Storage-Professional.html