最新の2026年03月15日 Portworx-Enterprise-Professional問題集は学習ガイドは試験合格するための秘訣
Portworx-Enterprise-Professional問題集の無料PDFをゲットせよ！最近更新された問題
質問 # 15
How should a Portworx administrator enable the Alertmanager?
- A. Create a secret with the Alertmanager configuration and enable Alertmanager in the StorageCluster object.
- B. Deploy Alertmanager by following the official Alertmanager documentation and integrate it with Portworx by enabling monitoring webhook in the StorageCluster object.
- C. Create a config map with the Alertmanager configuration and enable Alertmanager via the pxctl CLI.
正解：A
解説：
Comprehensive and Detailed Explanation From Exact Extract:
Enabling Alertmanager in Portworx involves creating a Kubernetes Secret containing the Alertmanager configuration (such as alert routing rules and notification channels) and referencing this secret in the Portworx StorageCluster manifest. This integration allows Portworx's monitoring stack to forward alerts to Alertmanager for centralized alert processing and notifications. Unlike ConfigMaps, which are generally used for non-sensitive data, Secrets protect sensitive alert configuration. Enabling Alertmanager via pxctl CLI is not supported as Portworx relies on Kubernetes declarative configuration for monitoring components. Additionally, deploying Alertmanager independently and integrating through webhooks requires manual setup but is not the recommended or integrated approach. Portworx official observability documentation details the secret-based configuration as the standard and secure method to enable and manage Alertmanager within Portworx clusters for robust alert handling【Pure Storage Portworx Monitoring Guide source】.
質問 # 16
Which CRD object can be used to restore an existing ApplicationBackup?
- A. ApplicationRestore
- B. Migration
- C. VolumeSnapshot
正解：A
解説：
Comprehensive and Detailed Explanation From Exact Extract:
The ApplicationRestore Custom Resource Definition (CRD) object in Portworx is specifically designed to restore an application from an existing ApplicationBackup. This object orchestrates the process of recovering a consistent snapshot of an application, including all its associated volumes, in Kubernetes environments. Using ApplicationRestore, administrators can define the source backup, restore location, and any necessary transformations during restoration. This facilitates disaster recovery, migration, or rollback scenarios for complex stateful applications. The Portworx backup and restore documentation clearly defines ApplicationRestore as the controller responsible for application-level recovery operations, ensuring data integrity and consistency throughout the restore workflow【Pure Storage Portworx Backup and Restore Guide source】.
質問 # 17
What are the three severity levels for Portworx alerts?
- A. INFO, WARNING, CRITICAL
- B. INFO, WARNING, ALARM
- C. INFO, WARNING, ERROR
正解：A
解説：
Comprehensive and Detailed Explanation From Exact Extract:
Portworx classifies alerts into three main severity levels to help administrators prioritize response actions. These levels are INFO, WARNING, and CRITICAL. INFO alerts provide informational messages about non-critical events, such as configuration changes or normal operational milestones. WARNING alerts indicate potential issues that could impact performance or availability if left unaddressed, such as increased latency or approaching capacity limits. CRITICAL alerts signal severe problems requiring immediate attention, such as node failures or data corruption risks. This severity categorization supports effective alert management and escalation policies, allowing operational teams to focus on high-impact issues first. The Portworx observability and alerting guide explains these levels in detail and recommends integrating alerts with external monitoring systems for centralized management【Pure Storage Portworx Alerting Guide source】.
質問 # 18
What does an administrator need to do if a drive fails and the pool contains metadata?
- A. Reformat the disk and reuse it.
- B. Delete the pool.
- C. Decommission the node.
正解：C
解説：
Comprehensive and Detailed Explanation From Exact Extract:
If a drive fails and the associated storage pool contains critical metadata, the safest and recommended action is to decommission the entire node. Metadata loss can compromise the integrity of volume allocations and cluster state. Decommissioning the node allows Portworx to safely remove the node from the cluster, replicate data, and redistribute workloads, preventing data loss or corruption. Deleting the pool or reformatting the disk without proper precautions risks losing metadata and causing cluster inconsistencies. Portworx's operational guidelines emphasize that nodes with failed drives holding metadata require careful decommissioning procedures to maintain cluster health and data durability, ensuring data is rebalanced and availability is preserved【Pure Storage Portworx Operations Guide source】.
質問 # 19
What Portworx swap requirement exists on a Portworx-enabled Linux host?
- A. Swap should be disabled.
- B. Portworx does not have a requirement for swap to be enabled or disabled.
- C. Swap should be enabled.
正解：A
解説：
Comprehensive and Detailed Explanation From Exact Extract:
Portworx requires swap to be disabled on Linux hosts where it runs. Disabling swap is necessary because swap usage can cause unpredictable latency and performance degradation for storage operations. Portworx relies on consistent and predictable I/O performance for managing block devices and volumes, which is incompatible with the potential delays caused by swapping memory pages to disk. Additionally, many Kubernetes environments recommend disabling swap to meet Kubernetes scheduler requirements, aligning with Portworx's needs. Portworx installation and system requirements documentation explicitly state that swap should be disabled on nodes running Portworx to ensure cluster stability, optimal performance, and predictable behavior of storage operations【Pure Storage Portworx System Requirements source】.
質問 # 20
Which command could be used to install Portworx on Kubernetes using the PX-Operator?
- A. kubectl apply -f "https://install.portworx.com/<portworx_version>?operator=true&mc=false&kbver=1.25.0&ns=portworx&b=true&kd=type%3Dgp3%2Csize%3D150&s=%2F%2F22type%3Dgp3%2Csize%3D150&c=px-cluster-0584f7fl-b6be-4608-800c-2ac5fb8069e0&stork=true&csi=true&mon=true&tel=false&st=k8s&promop=true"
- B. curl -O px-ag-install.sh -L "https://install.portworx.com/$PXVER/air-gapped?kbver=$KBVER"
- C. kubectl apply -f "https://install.portworx.com/<portworx_version>?comp=pxoperator&kbver=<k8s-version>&ns=portworx"
正解：C
解説：
Comprehensive and Detailed Explanation From Exact Extract:
The officially recommended method to install Portworx with Kubernetes Operator support is using the PX-Operator manifest. This is done by applying the manifest URL with the comp=pxoperator parameter. The command:
kubectl apply -f "https://install.portworx.com/<portworx_version>?comp=pxoperator&kbver=<k8s-version>&ns=portworx" deploys the Portworx Operator, which manages Portworx lifecycle operations such as installation, upgrades, and configuration changes within the Kubernetes cluster. Specifying the Kubernetes version (kbver) and namespace (ns) ensures compatibility and proper scoping. This operator-centric installation enables more efficient management and automation compared to standalone scripts or manual installations. Portworx official operator installation documentation confirms this approach as the best practice for production deployments, streamlining Portworx management in Kubernetes environments【Pure Storage Portworx Operator Installation Guide source】.
質問 # 21
A cluster administrator wants to define an Autopilot rule for Portworx.
What are the 4 main parts of an Autopilot rule?
- A. Replica, I/O profile, Secure, Placement Strategy
- B. Selector, Namespace Selector, Conditions and Actions
- C. Enforcement, Match Expressions, Topology Key and Weight
正解：B
解説：
Comprehensive and Detailed Explanation From Exact Extract:
An Autopilot rule in Portworx consists of four main parts: Selector, Namespace Selector, Conditions, and Actions. The Selector defines the set of volumes or pods the rule applies to, often using labels. Namespace Selector further narrows the scope to specific Kubernetes namespaces, allowing targeted policy application. Conditions specify triggers or thresholds such as capacity utilization, I/O metrics, or time-based schedules. When conditions are met, the Actions section defines automated responses such as volume expansion, migration, or alerting. This modular rule design enables flexible, policy-driven automation for storage management, helping maintain cluster health and performance without manual intervention. The Portworx Autopilot documentation provides detailed schema and examples, emphasizing these components as foundational for dynamic, autonomous cluster operation【Pure Storage Portworx Autopilot Guide source】.
質問 # 22
If a Portworx node is down and the Kubernetes cluster is healthy, which command should be used to check Portworx alerts on a healthy node?
- A. journalctl -Ifu portworx*
- B. kubectl describe node
- C. pxctl alerts show
正解：C
解説：
Comprehensive and Detailed Explanation From Exact Extract:
To check Portworx-specific alerts on a healthy node, administrators use the command pxctl alerts show. This command displays current alerts raised by Portworx, including warnings and critical notifications about storage, nodes, and cluster health. Even if one node is down, alerts from the healthy nodes can provide insights into cluster-wide issues or the status of the affected node. While journalctl displays system and service logs and kubectl describe node shows Kubernetes node info, neither provides aggregated Portworx alert data. The Portworx observability documentation recommends using pxctl alerts show for focused monitoring and alert management, enabling administrators to respond effectively to operational events within the Portworx cluster【Pure Storage Portworx Monitoring Guide source】.
質問 # 23
How would an administrator schedule automatic backups of a volume using Portworx?
- A. Use a cron job to execute pxctl snapshot create.
- B. Execute px backup volume.
- C. Configure and apply schedule policies.
正解：C
解説：
Comprehensive and Detailed Explanation From Exact Extract:
Portworx provides a declarative method to schedule automatic backups by configuring schedule policies within its Backup and DR framework. These policies specify when and how frequently backups should occur, retention rules, and target storage locations. By applying schedule policies, administrators enable Portworx to perform backups automatically without manual intervention or external scripting. Using cron jobs to run pxctl snapshot create is possible but less integrated, error-prone, and not recommended for scalable environments. The command px backup volume is not a valid Portworx CLI command. The Portworx backup documentation encourages using native schedule policies for reliable, maintainable, and policy-driven backup automation, supporting compliance and disaster recovery strategies【Pure Storage Portworx Backup Guide source】.
質問 # 24
What step is necessary to start using encrypted PVCs in Portworx?
- A. Select secret provider.
- B. Configure IO profiles.
- C. StorageClass needs the following parameter: secure: enabled.
正解：A
解説：
Comprehensive and Detailed Explanation From Exact Extract:
Using encrypted Persistent Volume Claims (PVCs) with Portworx requires that an administrator first configure a secret provider responsible for managing the encryption keys. The secret provider could be an external Key Management System (KMS) such as AWS KMS, Google Cloud KMS, Hashicorp Vault, or Kubernetes Secrets. This step is critical because encryption keys are essential to securely encrypt and decrypt data on volumes. Although enabling encryption in the StorageClass via parameters like secure: enabled is necessary to activate encryption on volumes, it is insufficient without a properly configured secret provider to manage the keys. The secret provider ensures keys are securely stored, rotated, and accessed, fulfilling compliance and security requirements. Portworx documentation stresses this as a foundational step to enable encrypted PVCs, highlighting that without a configured secret provider, encrypted volumes cannot be provisioned or used effectively【Pure Storage Portworx Encryption Docs source】.
質問 # 25
Which Portworx component is used to co-locate volumes with pods?
- A. Autopilot
- B. Stork
- C. Volume Placement Strategy
正解：C
解説：
Comprehensive and Detailed Explanation From Exact Extract:
Portworx's Volume Placement Strategy ensures that persistent volumes are co-located with the pods that use them, enhancing performance and reducing latency. This strategy involves applying placement rules and constraints that guide Kubernetes scheduler and Portworx storage operations to place data volumes on nodes close to or the same as the pods. Co-location improves I/O throughput and application responsiveness by minimizing network hops between compute and storage resources. While Autopilot automates scaling and Stork manages storage-aware scheduling, Volume Placement Strategy specifically handles volume location relative to workloads. The Portworx architecture documentation highlights this component as critical for optimizing storage efficiency and workload performance in Kubernetes environments running Portworx storage【Pure Storage Portworx Architecture Docs source】.
質問 # 26
Which command can be used to migrate volumes after cluster pairing is finished?
- A. kubectl cloudmigrate
- B. pxctl cloudmigrate start
- C. strokctl cloudmigrate start
正解：B
解説：
Comprehensive and Detailed Explanation From Exact Extract:
Once two Portworx clusters are paired, for example in disaster recovery setups, data migration between them can be initiated. The command pxctl cloudmigrate start triggers this migration process. It synchronizes volumes, ensuring that data is copied securely and consistently from the source cluster to the destination. This migration is transparent to applications and supports incremental syncs, which helps reduce downtime. The CLI command also provides operational feedback and logs for administrators to monitor progress. Portworx's documentation on disaster recovery workflows emphasizes this command as essential for starting volume migration post-cluster pairing, streamlining data protection and business continuity strategies across multiple sites or cloud regions【Pure Storage Portworx Disaster Recovery Guide source】.
質問 # 27
What command can be used to list all Autopilot rule objects in all namespaces in a Portworx cluster?
- A. kubectl describe autopilotrules
- B. kubectl get autopilotruleobjects --all-namespaces
- C. pxctl list autopilotrules
正解：C
解説：
Comprehensive and Detailed Explanation From Exact Extract:
The command pxctl list autopilotrules is used to list all Autopilot rule objects across namespaces within a Portworx cluster. Autopilot rules define automated policies for storage operations like scaling and volume migration. This CLI command queries the Portworx control plane to retrieve and display all configured Autopilot rules, regardless of the Kubernetes namespace they reside in. Using kubectl commands alone is insufficient because Autopilot rules are managed internally by Portworx and may not correspond directly to Kubernetes resources. Official Portworx CLI documentation confirms pxctl list autopilotrules as the primary command for comprehensive Autopilot rule enumeration, enabling administrators to audit and manage storage automation policies efficiently【Pure Storage Portworx Autopilot Guide source】.
質問 # 28
When utilizing volume encryption, what is a supported external key manager?
- A. Static keys stored in an S3 bucket
- B. Microsoft Key Management Services
- C. Hashicorp Vault
正解：C
解説：
Comprehensive and Detailed Explanation From Exact Extract:
Hashicorp Vault is a widely supported external Key Management System (KMS) integrated with Portworx for volume encryption. It offers robust capabilities including secure key generation, storage, rotation, and access control, making it well-suited for managing encryption keys in enterprise environments. Integrating Portworx with Hashicorp Vault enables automated and secure key retrieval during volume provisioning and use, ensuring compliance with security policies and regulations. Unlike static keys stored in S3 buckets, which lack dynamic security controls, Hashicorp Vault provides granular policy enforcement and audit logging. Microsoft Key Management Services (KMS) is not currently supported as an external KMS for Portworx encryption. Portworx security documentation emphasizes Hashicorp Vault's importance in maintaining secure key lifecycle management for encrypted volumes, highlighting it as the preferred KMS solution in multi-cloud and hybrid environments【Pure Storage Portworx Security Guide source】.
質問 # 29
What happens if the spec.csi.enabled flag is set to false in the Portworx StorageCluster spec?
- A. CSI will not be installed for the storage cluster.
- B. The cluster will fail to deploy if CSI is disabled.
- C. CSI will be installed, but it will not be used.
正解：A
解説：
Comprehensive and Detailed Explanation From Exact Extract:
The spec.csi.enabled flag in the Portworx StorageCluster specification dictates whether the Container Storage Interface (CSI) driver is deployed within the Kubernetes environment. Setting this flag to false means that the CSI driver will not be installed or enabled, effectively disabling the CSI functionality. The CSI driver is responsible for dynamic volume provisioning, attachment, and lifecycle management in Kubernetes clusters. Disabling CSI might be necessary in environments relying on legacy volume plugins or specific operational requirements. When CSI is disabled, Portworx will not support dynamic provisioning or other CSI-dependent features, which could limit functionality for Kubernetes storage operations. Portworx operator documentation explicitly states that disabling CSI omits the CSI driver installation, advising users to carefully consider the impact before setting this flag to false, especially in production environments requiring CSI functionality【Pure Storage Portworx Operator Docs source】.
質問 # 30
Which command shows a summary of the Portworx cluster status?
- A. kubectl get pxstatus
- B. pxctl cluster status
- C. helm list --px
正解：B
解説：
Comprehensive and Detailed Explanation From Exact Extract:
The command pxctl cluster status provides a concise summary of the Portworx cluster's health and operational status. This includes node states, storage pool information, volume statuses, and quorum information. It is the primary CLI command for administrators to quickly assess cluster health and detect any issues affecting storage availability or performance. helm list --px is a Helm package management command unrelated to cluster status, and kubectl get pxstatus is not a valid Kubernetes or Portworx command. Portworx documentation recommends pxctl cluster status as an essential monitoring command during routine operations and troubleshooting to ensure the cluster is functioning properly and that all nodes are communicating and healthy【Pure Storage Portworx CLI Guide source】
質問 # 31
When is a volume considered "Public"?
- A. When guest access is enabled
- B. When a volume is owned by system.admin
- C. When the volume does not have any ownership associated with it
正解：A
解説：
Comprehensive and Detailed Explanation From Exact Extract:
In Portworx, a volume is considered "Public" when guest access is enabled. Guest access allows users and applications without explicit Portworx authentication credentials to access the volume. This setting is typically used in less restrictive environments where access control is relaxed, but it reduces security by exposing data to potentially unauthorized entities. Public volumes can be accessed by any entity with network connectivity and basic permissions, which is why enabling guest access is carefully controlled in secure deployments. Portworx documentation on security models and access controls stresses that public volumes should be used sparingly and monitored closely due to the elevated risk of data exposure and compliance violations【Pure Storage Portworx Security Guide source】.
質問 # 32
What is a benefit of using Autopilot in Portworx environments?
- A. It automates the expansion of storage volumes based on predefined rules.
- B. It facilitates the migration of containers across clusters.
- C. Provides enhanced security features for data protection.
正解：A
解説：
Comprehensive and Detailed Explanation From Exact Extract:
Autopilot is a key feature in Portworx designed to automate operational tasks such as capacity management and volume resizing. One of its primary benefits is automating the expansion of storage volumes based on predefined rules and thresholds. This means that when a volume approaches its storage limit, Autopilot can automatically trigger volume expansion without manual intervention, ensuring applications have uninterrupted access to storage resources. This automation reduces operational overhead, eliminates manual errors, and helps maintain application performance and availability. While Autopilot doesn't directly handle container migration or security enhancements, its dynamic volume management capabilities play a critical role in operational efficiency and business continuity. The Portworx documentation highlights Autopilot as a tool for intelligent, policy-driven storage management that adapts to workload demands in real time【Pure Storage Portworx Autopilot Guide source】.
質問 # 33
......
最新Portworx-Enterprise-Professional試験問題集には高得点で一発合格：https://jp.fast2test.com/Portworx-Enterprise-Professional-premium-file.html
Portworx-Enterprise-Professional認定試験問題集には77練習テスト問題はこちら：https://drive.google.com/open?id=1p88xJH9weppKQngzBN_W_O2QIuGFW8q-