HPE2-K45 Questions and Answers

 According to the HPE SimpliVity REST API Reference Guide1, the svtcli account is a local emergency account that can be used to access HPE SimpliVity data using REST API whenthe hypervisor-based user is unavailable. This account can only perform a limited set of operations, such as getting information about hosts, clusters, backups, datastores, and virtual machines, and restoring backups of virtual machines. The svtcli account can request an authentication token using the emergency grant type, which is valid for 10 minutes of inactivity or 24 hours of continuous activity. The other options are not correct because:

• The svtcli account is not used when two or more VCs are not available. In that case, the federation management is transferred to the remaining VCs2.
• The svtcli account is not used when the hypervisor-based user is unavailable. In that case, the emergency grant type is used to access the REST API using the svtcli account1.
• The svtcli account is not used for daily management tasks performed using CLI. For that purpose, the hypervisor-based user is used, which has full access to the CLI commands3. References: 1: HPE SimpliVity REST API Reference Guide (A00019351ENW), pages 9-10, 14-152: HPE SimpliVity Administration Guide (A00019350ENW), page 303: HPE SimpliVity CLI Reference Guide (A00019352ENW), page 9.

According to the HPE SimpliVity Video - How to Delete a HPE SimpliVity Datastore1, one of the possible causes of the failure to delete an existing datastore is that the management network for a host is disconnected. This prevents the communication between the HPE SimpliVity federation and the vSphere Web Client, and thus the deletion operation cannot be performed. To check the management network status, the video suggests clicking Hosts from the vSphere Web Client inventory panel, double-clicking the host to check, clicking the Manage tab, and then the Networking subtab. The other options are not correct because:

• The datastore being marked as read-only is not a likely cause of the failure to delete it. The HPE SimpliVity Administration Guide2 states that the datastore must be writable before deleting it, and that the HPE SimpliVity federation will automatically change the datastore to writable mode when deleting it.
• The FC connection between the host and array failing is not a likely cause of the failure to delete the datastore. The HPE SimpliVity federation does not use FC connections to access the datastores, but rather uses NFS or SMB protocols over Ethernet networks2.
• The datastore not being added to the scope is not a likely cause of the failure to delete it. The HPE SimpliVity federation does not require the datastore to be added to the scope to delete it, as long as the datastore is visible in the vSphere Web Client1. References: 1: HPE SimpliVity Video - How to Delete a HPE SimpliVity Datastore2: HPE SimpliVity Administration Guide (A00019350ENW), pages 105-107.

The Intelligent Workload Optimizer is a feature of HPE SimpliVity that automatically balances the virtual machine workloads across the nodes in a cluster, based on the CPU, memory, and storage utilization1. This feature helps to improve the performance and efficiency of the cluster, and to avoid hotspots and bottlenecks. The Intelligent Workload Optimizer can be configured to run periodically or on demand, and it can also take into account the affinity and anti-affinity rules for the virtual machines2. The Resource Balancer (option A) is a feature of HPE SimpliVity that automatically balances the storage capacity across the nodes in a cluster, based on the free space and deduplication ratio3. This feature helps to optimize the storage utilization and availability of the cluster, and to avoid capacity issues and data loss. The Resource Balancer does not balance the virtual machine workloads or the I/O traffic. The Management Virtual Appliance (option B) is a component of HPE SimpliVity that provides the management interface and functionality for the cluster, such as backup, restore, clone, move, and federation operations4. The Management Virtual Appliance does not balance the virtual machine workloads or the I/O traffic. The Arbiter (option C) is a component of HPE SimpliVity that provides the quorum service for the cluster, ensuring data consistency and availability in the event of a node or site failure5. The Arbiter does not balance the virtual machine workloads or the I/O traffic. References:

• 1: Using HPE SimpliVity Official Certification Study Guide (HPE2-K45), HPE Press, 2019, p. 83.
• 2: HPE SimpliVity 380 Gen10 Node Data sheet, HPE, 2019, p. 4.
• 3: Using HPE SimpliVity Official Certification Study Guide (HPE2-K45), HPE Press, 2019, p. 84.
• 4: Using HPE SimpliVity Official Certification Study Guide (HPE2-K45), HPE Press, 2019, p. 81.
• 5: Using HPE SimpliVity Official Certification Study Guide (HPE2-K45), HPE Press, 2019, p. 82.

The Persistent Storage layer is the lowest layer of the HPE SimpliVity Data Visualization Platform. It is responsible for storing and tracking all data and metadata on the HPE SimpliVity nodes. It uses a distributed file system that spans across all nodes in a cluster, and provides high availability, scalability, and performance. The Persistent Storage layer also integrates with the HPE OmniStack Accelerator Card, which enables accelerated data efficiency, global unified management, and built-in data protection12. References: HPE SimpliVity Data Virtualization Platform technical white paper, SimpliVity Data Virtualization Platform Architecture - YouTube

HPE SimpliVity 2600 is a compact solution optimized for edge and remote office, branch office (ROBO) environments. It is available on HPE Apollo 2000 servers, which are designed for high-density computing and can fit up to four nodes in a 2U chassis. HPE SimpliVity 2600 provides enterprise-grade data protection and resiliency for virtualized workloads, as well as simplified management and scalability. It is ideal for customers who have very limited rack space and need a hyperconverged solution that can deliver high performance and efficiency. References: HPE SimpliVity 2600 - Product Information Reference, HPE SimpliVity 2600 | HPE Store US, Introducing Our New High-Density Hyperconverged Solution: HPE SimpliVity 2600

HPE SimpliVity provides storage HA by creating two copies of each virtual machine data across different nodes in a cluster. This ensures that the virtual machines can continue to run even if one node fails. However, this also consumes twice the storage capacity for each virtual machine. For development virtual machines that do not require storage HA, the customer can save storage capacity by creating a single-replica datastore for these virtual machines. A single-replica datastore is a datastore that has only one copy of the virtual machine data on one node. This reduces the storage consumption by 50%, but also increases the risk of data loss and unavailability in case of node failure. Therefore, the customer should carefully weigh the trade-offs between storage efficiency and data protection when using a single-replica datastore. References: HPE SimpliVity Data Virtualization Platform; HPE SimpliVity User Guide

According to the HPE SimpliVity documents and learning resources, mixing nodes with different drive configurations within a cluster is not recommended, as it can result in unbalanced 10 performance and capacity utilization. This is because the HPE SimpliVity nodes use a distributed file system that replicates data across all nodes in the cluster, and the data efficiency and backup features depend on the consistent performance of the underlying storage devices. Therefore, it is best to use nodes with the same drive configuration and capacity within a cluster, and avoid mixing All-flash and hybrid nodes, or nodes with different drive types, sizes, or speeds. The other options are incorrect because they are either false or irrelevant. Mixing nodes with different drive configuration does not require an additional license, nor is it available only for AMD-based nodes. Mixing All-flash and hybrid nodes in the same cluster is not supported, as it can causeperformance and capacity issues. References: Using HPE SimpliVity Official Certification Study Guide, page 42; HPE SimpliVity networking explained; HPE SimpliVity Releases