← Back to exam page

HPE2-N68 – Using HPE Containers

Loading demo links...

Showing 1–3 of 4 questions

Question 1

A Tenant Member plans to use KubeDirettor to deploy a Spark 2.4.5 cluster. You need to give cluster members access to data stored in a volume In Ezmeral Data Fabric. What are two required steps?

Select all that apply, then click Submit answer.

  • ○

    A Tenant Admin must add another role to the Spark 2.4.5 application for the dtap sidecar.

  • ○

    The Tenant Member must specify the "hpecp.hpe.com/dtap: hadoop2" pod label under each role when running the cluster.

  • ○

    The Tenant Member must create an FS mount to the volume's mount path.

  • ○

    A Tenant Admin must create a DataTap to the volume's mount path.

  • ○

    The Tenant Member must reference the Data Fabric namespace when running the cluster.


Question 2

You have an Ezmeral Container Platform solution running v5.2 software. The platform manages several Kubernetes clusters. You need to upgrade the software. What type of behavior should you expect during the upgrade?

Select an option, then click Submit answer.

  • ○

    Existing services continue to run with minimal disruption, but users cannot add new services in the Web Ul.

  • ○

    All services on the cluster will be down for about an hour, as will the Web Ul.

  • ○

    Users can access EPIC features, but services running on the Kubernetes cluster will be unavailable.

  • ○

    Users can access the Web Ul. But external clients will not be able to reach services on the cluster.


Question 3

What is an advantage of HPE Ezmerai Container Platform as compared to engineered

Kubernetes distributions such as Red Hat OpenShift?

Select an option, then click Submit answer.

  • ○

    It keeps better pace with the latest Kubernetes versions and provides a flexible choice in which versions each cluster runs.

  • ○

    It enables customers to run containerized workloads on-prem while most engineered Kubernetes solutions are cloud only.

  • ○

    It is designed to run stateless and stateful apps while most engineered Kubernetes solutions are optimized for stateful apps only.

  • ○

    It provides a lower TCby using an upfront payment model as opposed to software subscriptions.