Free HP HPE2-K45 Practice Exam with Questions & Answers

 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

The Persistent Storage layer is the lowest layer of the HPE SimpliVity Data Visualization Platform. It is responsible for storing and tracking all data and metadata on the HPE SimpliVity nodes. It uses a distributed file system that spans across all nodes in a cluster, and provides high availability, scalability, and performance. The Persistent Storage layer also integrates with the HPE OmniStack Accelerator Card, which enables accelerated data efficiency, global unified management, and built-in data protection12. References: HPE SimpliVity Data Virtualization Platform technical white paper, SimpliVity Data Virtualization Platform Architecture - YouTube

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

 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

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

 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 Video - How to Delete a HPE SimpliVity Datastore1, one of the possible causes of the failure to delete an existing datastore is that the management network for a host is disconnected. This prevents the communication between the HPE SimpliVity federation and the vSphere Web Client, and thus the deletion operation cannot be performed. To check the management network status, the video suggests clicking Hosts from the vSphere Web Client inventory panel, double-clicking the host to check, clicking the Manage tab, and then the Networking subtab. The other options are not correct because:

• The datastore being marked as read-only is not a likely cause of the failure to delete it. The HPE SimpliVity Administration Guide2 states that the datastore must be writable before deleting it, and that the HPE SimpliVity federation will automatically change the datastore to writable mode when deleting it.
• The FC connection between the host and array failing is not a likely cause of the failure to delete the datastore. The HPE SimpliVity federation does not use FC connections to access the datastores, but rather uses NFS or SMB protocols over Ethernet networks2.
• The datastore not being added to the scope is not a likely cause of the failure to delete it. The HPE SimpliVity federation does not require the datastore to be added to the scope to delete it, as long as the datastore is visible in the vSphere Web Client1. References: 1: HPE SimpliVity Video - How to Delete a HPE SimpliVity Datastore2: HPE SimpliVity Administration Guide (A00019350ENW), pages 105-107.

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

According to the HPE SimpliVity documents and learning resources, each datastore in an HPE SimpliVity cluster is presented to the HPE SimpliVity nodes as a VMFS datastore. A VMFS datastore is a VMware-specific file system that allows multiple ESXi hosts to access the same storage device concurrently. HPE SimpliVity uses VMFS datastores to store virtual machine files and provide shared storage to all virtual machines on the hosts. HPE SimpliVity does not use vSAN, NFS, or vVol as the datastore type. References: Using HPE SimpliVity Official Certification Study Guide, page 41; SimpliVity Video - How to Create a HPE SimpliVity Datastore

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]