HPE2-K45 Sample Questions Answers

You can apply a backup policy at the datastore level, as this is the level at which HPE SimpliVity manages the virtual machines and their backups1. A backup policy consists of one or more rules that specify the destination, frequency, and retention of the backups. You can assign a backup policy to a datastore, and all the virtual machines in that datastore will inherit the backup policy. You can also override the backup policy for individual virtual machines, if needed2. Applying a backup policy at the cluster level (option A), the datacenter level (option B), or the vCenter Server level (option C) is not possible, as these are not the levels at which HPE SimpliVity manages the virtual machines and their backups. These levels are used for organizing and managing the ESXi hosts and the HPE SimpliVity nodes, but not for applying backup policies. References:

• 1: Using HPE SimpliVity Official Certification Study Guide (HPE2-K45), HPE Press, 2019, p. 28.
• 2: HPE SimpliVity OmniStack Interoperability Guide 4.2.0, HPE, 2021, p. 8.

• Register External Store …1

This option allows you to register an HPE StoreOnce Catalyst Store as an external backup target for HPE SimpliVity. This enables you to store VM backups on an HPEStoreOnce system, which is a disk-based backup solution that offers deduplication, compression, encryption, remote replication, and direct application-managed integration2.

To use this option, you need to have an HPE StoreOnce appliance connected to your HPE SimpliVity cluster, and configure a Catalyst Store on it. Then, you can select the All HPE SimpliVity Actions menu, and click Register External Store. You will be prompted to enter the following information:

• The name of the external store
• The IP address or hostname of the HPE StoreOnce appliance
• The name of the Catalyst Store
• The credentials of the Catalyst Store

After you enter the required information, click OK to register the external store1.

 According to the HPE SimpliVity documents and learning resources, the difference between crash consistent and application consistent cloning methods is that the application consistent method ensures that the cloned virtual machine is in a consistent state with respect to the application data and transactions. This means that the application consistent method allows the pending 10 operations to finish before committing them to the database, and flushes the memory buffers and caches to the disk. This ensures that the cloned virtual machine can resume the application without any data loss or corruption. The crash consistent method, on the other hand, does not guarantee that the cloned virtual machine is in a consistent state with respect tothe application data and transactions. This means that the crash consistent method does not wait for the pending 10 operations to finish or flush the memory buffers and caches to the disk. This may result in some data loss or corruption if the cloned virtual machine resumes the application. The crash consistent method is faster than the application consistent method, but less reliable. The other options are incorrect because they are either false or irrelevant. Both methods are not the same, and the difference is not only speed of cloning. The crash consistent method can be used for any virtual machine, not only for those with Fault Tolerance enabled. The application consistent method is available for both Windows and Linux operating systems, not only for Linux. References: Clone a virtual machine; HPE SimpliVity frequently asked questions, page 17; Using HPE SimpliVity Official Certification Study Guide, page 65

 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.

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

 HPE SimpliVity allows customers to connect ESXi compute nodes to HPE SimpliVity datastores without additional license or configuration. This enables customers to leverage the data efficiency and protection features of HPE SimpliVity for their compute-intensive workloads. However, the compute nodes must reside in the same cluster as HPE SimpliVity nodes, and they must be authorized by HPE SimpliVity to access the NFS datastores. The number of compute nodes per cluster is limited by the maximum number of hosts supported by VMware vSphere. References: HPE SimpliVity User Guide; HPE SimpliVity Compute Node Software Installation and Startup Service

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.

According to the HPE SimpliVity documents and learning resources, the best practice for designing an HPE SimpliVity solution is 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. This is because mixing nodes with different drive configurations can result in unbalanced 10 performance and capacity utilization, as well as compatibility issues.Therefore, the recommended option for this design is to create a new cluster with HPE SimpliVity 380 Gen10 H SFF nodes at the remote site, and keep the existing cluster with HPE SimpliVity 380 Gen10 hardware accelerated nodes at the primary site. The other options are incorrect because they do not follow the best practice and can cause performance and capacity problems. References: Using HPE SimpliVity Official Certification Study Guide, page 42; HPE SimpliVity networking explained; HPE SimpliVity Releases

 According to the HPE InfoSight for HPE SimpliVity Getting Started document1, HPE InfoSight provides the following functionality for HPE SimpliVity:

• Monitoring of cluster, node, and virtual machine performance, capacity, and health
• Reporting of system configuration, inventory, and compliance
• Analysis of trends, anomalies, and root causes
• Prediction of future resource needs and potential issues
• Recommendation of best practices and optimization actions

One of the key features of HPE InfoSight is the ability to monitor the latency of virtual machines, which is the time it takes for a request to be processed by the system. Latency is an important indicator of the performance and efficiency of the system, and HPE InfoSight provides detailed and granular data on the latency of each virtual machine, as well as the breakdown of the latency components, such as CPU, memory, network, and storage. HPE InfoSight also provides alerts and notifications when the latency exceedsthe predefined thresholds, and helps to identify and resolve the root causes of the latency issues.

Therefore, the correct answer is D. monitoring of virtual machine latency, as this is one of the functionality that HPE InfoSight provides for HPE SimpliVity. References:

• 1: HPE InfoSight for HPE SimpliVity Getting Started, https://support.hpe.com/hpesc/public/api/document/a00089726en_us?docLocale=en_US