HP HPE2-K45 Practice Test Questions 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.

 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 and database, while the crash consistent method does not guarantee that1. The application consistent method uses the VMware snapshot or the Microsoft Volume Shadow Copy Service (VSS) to quiesce the application and flush the pending I/O operations to the disk before creating the clone, which prevents data corruption or loss2. The crash consistent method does not quiesce the application or flush the pending I/O operations, and creates the clone as if the virtual machine had crashed, which may result in data inconsistency or recovery issues3. The application consistent method is recommended for virtual machines that run database applications, such as SQL Server or Oracle, while the crash consistent method is suitable for virtual machines that run non-database applications, such as web servers or file servers4. The application consistent method is not available only for Linux operating systems (option D), as it also supports Windows Server operating systems that have VMware Tools or VSS installed5. The crash consistent method should not be used only for the virtual machines with Fault Tolerance enabled (option C), as it can be used for any virtual machine that does not require application consistency. Both methods are not the same,and the speed of cloning is not the only difference (option B), as they have different implications for the data integrity and availability of the cloned virtual machine. References:

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

2: Clone a virtual machine - techhub.hpe.com, HPE, 2021, 3.

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

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

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

[6]: Using HPE SimpliVity Official Certification Study Guide (HPE2-K45), HPE Press, 2019, p. 28.

[7]: Clone a virtual machine - techhub.hpe.com, HPE, 2021, 3.

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.

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.

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