HPE2-K45 Exam Dumps : Using HPE SimpliVity

• HPE SimpliVity 380 Gen10 LFF H and HPE SimpliVity 380 Gen10 SFF H nodes are two types of HPE SimpliVity nodes that differ in their form factor, storage capacity, and performance. LFF stands for large form factor, which means that the node has 3.5-inch hard disk drives (HDDs) and can support up to 40 TB of raw storage capacity. SFF stands for small form factor, which means that the node has 2.5-inch solid state drives (SSDs) and can support up to 23.4 TB of raw storage capacity12.
• HPE SimpliVity nodes can be grouped into clusters, which are logical units of compute and storage resources that share the same configuration and policies. HPE SimpliVity clusters can be further grouped into federations, which are collections of clusters that span across different physical locations and provide unified management and data protection34.
• For this setup, the recommended design is to put SFF and LFF nodes in separate clusters, but within the same federation. According to the HPE SimpliVity Federation Design and Scaling Guide document, the following reasons support this recommendation:

References:

1: HPE SimpliVity 380 Gen10 LFF H Node Data sheet 2: HPE SimpliVity 380 Gen10 SFF H Node Data sheet 3: HPE SimpliVity Data Virtualization Platform 4: HPE SimpliVity Federation Design and Scaling Guide : [HPE SimpliVity 380 Gen10 Node Data sheet - PSNow] : [HPE SimpliVity 380 Gen10 Node | HPE Store US] : [HPE SimpliVity Intelligent Workload Optimizer] : [HPE SimpliVity with HPE StoreOnce Reference Architecture] : [HPE SimpliVity Stretched Cluster Guide] : [HPE SimpliVity Remote RapidDR Software Installation and Startup Service]

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.

The correct answer is A. All VMs on the node restart in a node where the replica resides. This is because HPE SimpliVity uses a replication factor (RF) of 2 or 3 to ensure that each virtual machine (VM) has one or two copies of its data on different nodes in the cluster. If an HPE OmniStack Virtual Controller (VC) fails, the VMs on that node lose access to their primary data, but they can still access their replica data on another node. The vSphere HA feature detects the VC failure and restarts the VMs on the node where the replica resides, ensuring data availability and continuity1.

The other options are not correct. Option B is incorrect because HPE SimpliVity Intelligent Workload Optimizer (IWO) is a feature that balances the VMs across the cluster based on CPU and memory utilization, not on VC failures2. Option C is incorrect because the IP address of the VC does not fail over to another node, but remains associated with the failed node. The VMs on the failed node are restarted on another node with a different VC IP address3. Option D is incorrect because the VMs on the node do not go on standby mode, but are restarted on another node to resume their operations.

References: 1: HPE SimpliVity frequently asked questions 2: HPE SimpliVity Intelligent Workload Optimizer 3: HPE SimpliVity 380 Gen10 Node User Guide