HPE2-K45 Exam Dumps - Using HPE SimpliVity

Hyper Protected is one of the four pillars of HPE SimpliVity’s value proposition, along with Hyper Simple, Hyper Efficient, and Hyper Manageable. Hyper Protected refers to the ability of HPE SimpliVity to provide built-in data protection and disaster recovery for virtual machines (VMs) with unprecedented speed and efficiency. HPE SimpliVity can backup or restore 1TB VM in less than 1 minute, thanks to its unique data architecture that deduplicates, compresses, and optimizes data at inception, and its global federated management that enables policy-based automation across multiple sites. Restoring individual files from a VM backup, defining a storage policy using RAID 6 or RAID 60 to protect the VM, and integrating with Veeam to provide an external backup solution are not specific to HPE SimpliVity’s Hyper Protected capability, and can be done by other solutions as well. References: Using HPE SimpliVity Official Certification Study Guide, page 11, section 1.2. SimpliVity Hyperconverged, section “Hyper Protected”. HPE SimpliVity 380 Gen10 Node, section “Features”. SimpliVity HyperGuarantee, section “Remain online and recoverable — always”.

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

According to the HPE SimpliVity Administration Guide1, one of the possible solutions to avoid the potential problem of CPU intensive applications impacting the performance of other virtual machines is to deploy the CPU intensive virtual machines on HPE SimpliVity, and configure for them CPU affinity parameter. This parameter allows you to specify which physical CPU cores are used by a virtual machine, and thus isolate the CPU intensive workloads from the rest of the virtual machines. This way, you can still leverage the HPE SimpliVity features, such as data efficiency, backup and restore, and federation management, for these virtual machines. The other options are not correct because:

• Presenting HPE SimpliVity datastores to external ESXi system that will house the CPU intensive virtual machines is not a recommended solution, as it will reduce the data efficiency and availability benefits of HPE SimpliVity, and introduce additional complexity and overhead in managing the external ESXi system1.
• Adding an external ESXi cluster to HPE SimpliVity Federation, and enabling Intelligent Workload Optimizer is not a recommended solution, as it will require additional hardware and software costs, and may not guarantee the optimal performance of the CPU intensive virtual machines, as the Intelligent Workload Optimizer is based on heuristics and not on strict rules2.
• Adding an external ESXi system to HPE SimpliVity cluster, and enabling DRS functionality for CPU intensive virtual machines is not a recommended solution, as it will violate the HPE SimpliVity cluster requirements, and may cause issues with the HPE SimpliVity federation and data protection features1. References: 1: HPE SimpliVity Administration Guide (A00019350ENW), pages 23, 25, 28, 32, 342: HPE SimpliVity Intelligent Workload Optimizer User Guide (A00019354ENW), pages 5, 7, 9.

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.

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 HPE SimpliVity OmniStack Interoperability Guide is a document that provides the information about the supported hardware and software components for the HPE SimpliVity solution, such as the HPE SimpliVity nodes, the VMware ESXi hosts, the VMware vCenter Server, the HPE OmniStack software, the HPE SimpliVity Arbiter, and the guestoperating systems1. The guide also provides the compatibility matrix and the configuration guidelines for the HPE SimpliVity solution. The ESXi version (option B) and the guest OS version (option C) are two items that can be found in the HPE SimpliVity OmniStack Interoperability Guide, as they are essential for the proper functioning and performance of the HPE SimpliVity solution. The guide lists the supported ESXi versions for each HPE SimpliVity node model and HPE OmniStack software version, as well as the supported guest OS versions for each HPE SimpliVity node model1. The GPU accelerators (option A), the vSphere license (option D), and the processor model (option E) are not items that can be found in the HPE SimpliVity OmniStack Interoperability Guide, as they are not relevant or required for the HPE SimpliVity solution. The GPU accelerators are not supported by the HPE SimpliVity solution, as they are not compatible with the HPE SimpliVity nodes2. The vSphere license is not specified by the HPE SimpliVity solution, as it depends on the customer’s choice and needs3. The processor model is not listed by the HPE SimpliVity solution, as it is already determined by the HPE SimpliVity node model4. References:

• 1: HPE SimpliVity OmniStack Interoperability Guide 4.2.0, HPE, 2021, pp. 1-25.
• 2: HPE SimpliVity 380 Gen10 Node Data sheet, HPE, 2019, p. 5.
• 3: Using HPE SimpliVity Official Certification Study Guide (HPE2-K45), HPE Press, 2019, p. 27.
• 4: Using HPE SimpliVity Official Certification Study Guide (HPE2-K45), HPE Press, 2019, p. 17.

 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

The Total Data Stored metric in HPE InfoSight for HPE SimpliVity represents the total amount of data that is stored on the HPE SimpliVity cluster for a given VM. This includes the VM data, which is the actual size of the VM on the datastore, as well as the local backups and remote backups, which are the copies of the VM data that are stored on the same or different clusters for data protection purposes1. The Total Data Stored metric is calculated before deduplication and compression, which are the data efficiency features of HPE SimpliVity that reduce the physical storage consumption2.

The VM Storage Usage metric in vCenter represents the amount of storage space that is allocated to a VM on a datastore. This metric does not include the backups of the VM data, as they are not visible to vCenter. The VM Storage Usage metric is also calculated after deduplication and compression, which means that it reflects the actual storage consumption of the VM data on the datastore3.

Therefore, the Total Data Stored metric is significantly higher than the VM Storage Usage metric because it includes more data elements and it does not account for the data efficiency features of HPE SimpliVity.

References: 1: HPE SimpliVity frequently asked questions 2: The technology enabling HPE SimpliVity data efficiency 3: [VMware vSphere Documentation]

• HPE SimpliVity RapidDR is a disaster recovery orchestration tool that automates and simplifies the recovery process of VMs protected by HPE SimpliVity backups. It can be used in the event of disaster to efficiently restore VMs across the primary and secondary sites, which consist of multiple HPE SimpliVity nodes12.
• HPE SimpliVity RapidDR requires VMware vCenter Server, a centralized management platform for VMware vSphere environments, to perform the recovery operations. VMware vCenter Server is licensed per instance, which means that each vCenter Server installation requires a separate license3 .
• To reduce the vCenter Server license cost, a customer can use only a single vCenter Server instance to manage the HPE SimpliVity federation, which is a group of HPE SimpliVity clusters that share the same configuration and policies. This deployment scenario is possible when the federation is managed centrally, which means that all the HPE SimpliVity nodes are registered to the same vCenter Server instance, regardless of their physical location .
• The other options are not valid for reducing the vCenter Server license cost. The number of VMs covered by a single recovery plan does not affect the vCenter Server license requirement, as long as the VMs are managed by the same vCenter Server instance. Enabling Enhanced Linked Mode for vCenter allows multiple vCenter Server instances to share information and provide a single pane of glass view, but it does not eliminate the need for separate licenses for each vCenter Server instance. Disabling Intelligent Workload Optimizer, a feature that balances the VM workload across the HPE SimpliVity cluster, has no impact on the vCenter Server license requirement.

References:

1: HPE SimpliVity RapidDR 2: HPE SimpliVity RapidDR - Starter License - 25 VMs - CDW 3: VMware vCenter Server - VMware : VMware vCenter Server Licensing, Pricing and Packaging : [HPE SimpliVity Federation Design and Scaling Guide] : [HPE SimpliVity with HPE StoreOnce Reference Architecture] : [HPE SimpliVity Data Virtualization Platform] : [HPE SimpliVity Intelligent Workload Optimizer] : [HPE SimpliVity Stretched Cluster Guide] : [HPE SimpliVity Remote RapidDR Software Installation and Startup Service]