Free Practice Questions for HP HPE2-K45 Exam

 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 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

 According to the HPE SimpliVity documents and learning resources, the HPE SimpliVity 380 Gen10 is the only model that can be equipped with the HPE mniStack Accelerator card. The HPE mniStack Accelerator card is a PCIe-based card that provides hardware acceleration for data compression and deduplication. It also enables the HPE SimpliVity RapidDR feature, which automates and simplifies disaster recovery operations. The other models, such as the HPE SimpliVity 2600, the HPE SimpliVity 380 Gen10 H, and the HPE SimpliVity 325 Gen10, do not support the HPE mniStack Accelerator card. They rely on software-based data efficiency and backup features. References: Using HPE SimpliVity Official Certification Study Guide, page 29; HPE SimpliVity networking explained; HPE SimpliVity Releases

Compute nodes are x86 servers that run ESXi and consume the HPE SimpliVity datastores for storage. They provide additional CPU and memory resources to the environment without requiring additional SimpliVity licenses. However, they must reside in the same cluster as HPE SimpliVity nodes, as this is a requirement for the SimpliVity Data Virtualization Platform (DVP) to function properly. The number of compute nodes that can be connected per SimpliVity node is not limited to 5, but depends on the available network bandwidth and storage capacity. Additional license is not required to connect ESXi nodes to SimpliVity datastores, as this is a native capability of the SimpliVity DVP. Connecting ESXi compute nodes is not possible only when VMFS datastores are configured at SimpliVity Federation level, as this is not a prerequisite for the SimpliVity DVP. References: Using HPE SimpliVity Official Certification Study Guide, page 29, section 2.2. Preparing Compute Nodes to Use SimpliVity DVP, section “Preparing Compute Nodes to Use SimpliVity DVP”. HPE SimpliVity 380 Gen10 Node, section “Features”.

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

A stretched cluster is a configuration that allows two or more HPE SimpliVity clusters to span across different physical locations, while maintaining a single logical cluster and asingle management interface. A stretched cluster provides high availability, disaster recovery, and workload mobility for the virtual machines (VMs) running on the HPE SimpliVity platform12.

A VDI infrastructure is a virtualization solution that delivers desktops and applications to end users from a centralized data center. VDI infrastructure can use different types of VMs, such as linked clones or full clones, to provide the desktops and applications to the end users. Linked clones are VMs that share a common base image and consume less storage space, while full clones are VMs that have their own independent copies of the base image and consume more storage space34.

According to the HPE Reference Architecture for VMware Horizon on HPE SimpliVity document, both linked clones and full clones are supported on a stretched cluster. The document states that "HPE SimpliVity supports both linked clones and full clones on a stretched cluster. Linked clones are recommended for better storage efficiency and performance. Full clones can be used for persistent desktops that require more customization and personalization."5 The document also provides the design considerations and best practices for deploying VDI infrastructure on HPE SimpliVity stretched cluster, such as the network requirements, the VM placement, the backup and restore policies, and the failover and failback scenarios.

References:

1: HPE SimpliVity Stretched Cluster Guide 2: HPE SimpliVity Stretched Cluster 3: What is VDI (Virtual Desktop Infrastructure)? - VMware 4: What is a Linked Clone? - Definition from Techopedia 5: HPE Reference Architecture for VMware Horizon on HPE SimpliVity : [HPE SimpliVity Data Virtualization Platform] : [HPE SimpliVity Intelligent Workload Optimizer] : [HPE SimpliVity Federation Design and Scaling Guide]

 According to the HPE SimpliVity Solution Design Guide1, Lanamark is a cloud-based service that collects and analyzes data from customer environments to support the solution design process. Lanamark can collect data from various sources, such as vCenter Server, Hyper-V, XenServer, physical servers, and storage arrays. However, if the customer environment is not connected to the internet, Lanamark Snap can be used to collect the data offline and then upload it manually to the Lanamark portal. Lanamark Snap is a portable tool that can be downloaded from the Lanamark portal and run on any Windows workstation that has access to the customer environment. Lanamark Snap can connect to the vCenter Server and collect the performance data from the ESXi hosts and virtual machines. Lanamark Snap can also collect data from other sources, such as physical servers and storage arrays, by using agents or scripts. Lanamark Snap saves the collected data in a compressed file that can be uploaded to the Lanamark portal for analysis and reporting.

Therefore, the correct answer is D. Download Lanamark Snap and use it to collect the data, and then upload manually to the Lanamark portal, as this is the best option to collect data from an ESXi infrastructure that is not connected to the internet. References:

1: HPE SimpliVity Solution Design Guide, https://h20195.www2.hpe.com/v2/getdocument.aspx?docname=a00019351enw, page 15-16

The best way to migrate virtual machines from the existing infrastructure to HPE SimpliVity is to share HPE SimpliVity datastores with standard ESXi hosts, and migrate the virtual machines using VMware vSphere® Storage vMotion®1. This method allows the virtual machines to be moved to the HPE SimpliVity datastores without any downtime or impact on the performance. The HPE SimpliVity datastores are automatically created and managed by the HPE SimpliVity Virtual Controller, and they can be shared with any ESXi host that is in the same vCenter Server® as the HPE SimpliVity cluster2. Connecting VMFS datastores holding the virtual machine files to HPE SimpliVity nodes, and migrating the virtual machines (option A) is not a supported method, as the HPE SimpliVity nodes do not have direct access to the VMFS datastores, and they can only use the HPE SimpliVity datastores3. Mapping VMFS datastores holding the virtual machine files as an RDM to HPE SimpliVity nodes, and migrating the virtual machines (option C) is not a supported method, as the HPE SimpliVity nodes do not support RDM devices, and they can only use the HPE SimpliVity datastores4. Adding ESXi system to the HPE SimpliVity cluster, and migrating the virtual machines to HPE SimpliVity datastores (option D) is not a recommended method, as it requires the ESXi system to be converted to an HPE SimpliVity node, which involves installing the HPE OmniStack software and the HPE SimpliVity Virtual Controller, and reconfiguring the network settings. This method may cause downtime and data loss, and it is only advised for specific scenarios, such as replacing a failed node or expanding the cluster. References:

1: Using HPE SimpliVity Official Certification Study Guide (HPE2-K45), HPE Press, 2019, p. 29.

2: HPE SimpliVity OmniStack Interoperability Guide 4.2.0, HPE, 2021, p. 8.

3: HPE SimpliVity 380 Gen10 Node Data sheet, HPE, 2019, p. 5.

4: HPE SimpliVity OmniStack Interoperability Guide 4.2.0, HPE, 2021, p. 9.

[5]: HPE SimpliVity 380 Gen10 Node Installation and Startup Service, HPE, 2019, p. 3.

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.