HPE2-N68 practice question 3 of 10

You have an Ezmejal Container Platform solution that manages an internally created Kubernetes cluster. The cluster uses AD for Its authentication…

Full set: 40 questions
You have an Ezmejal Container Platform solution that manages an internally created Kubernetes cluster. The cluster uses AD for Its authentication settings, and users can successfully log into the platform with their domain credentials. You have created a Tenant on the cluster which has the "AI/ML project" setting enabled on it. You have also created a Notebook cluster within that project. However, users receive an error when they try to log into the Notebook endpoint (Jupyter Hub) with their domain credentials. What should you check?
Answer options
A: That the users have a manually created external account that assigns them to the Cluster Admin role in the cluster
B: That the Notebook cluster has a "cluster" connection to the AD server hostname
C: That the users have a manually created external account that assigns them to the Admin status in the AI/ML Project
D: That the Notebook cluster has a "secret" connection with this value: "hpecp-ext-auth-secret" Correct answer
Correct Answer:
D. That the Notebook cluster has a "secret" connection with this value: "hpecp-ext-auth-secret"
Explanation

When HPE Ezmeral Container Platform is configured with an external authentication provider like Active Directory (AD), it creates a Kubernetes secret named hpecp-ext-auth-secret. This secret contains the necessary OAuth2 client information. For applications deployed within a tenant, such as a Jupyter Notebook cluster, to use the platform's single sign-on (SSO) capabilities, they must be explicitly linked to this secret. If the Notebook cluster is created without this "secret" connection, its JupyterHub instance will not be configured to authenticate users against the platform's AD, resulting in login failures, even if users can access the main platform UI.

Why Incorrect

A. Assigning the "Cluster Admin" role is excessive, poses a significant security risk, and is not the standard procedure for granting application access to end-users.
B. Applications within the platform leverage the central authentication service. They do not require a direct, separate "cluster" connection to the AD server itself.
C. The "Admin" status within an AI/ML Project is for managing the project, not for using the resources within it. Standard users typically have a "Member" role.

References

1. HPE Ezmeral Container Platform 5.3 Administrator Guide: In the section "Configuring External User Authentication," the guide details the creation of the hpecp-ext-auth-secret when an external authentication group is configured. It states, "When you configure external user authentication, HPE Ezmeral Container Platform creates a Kubernetes secret named hpecp-ext-auth-secret... This secret can be used to configure applications to use the same authentication as the platform." (Reference: Chapter on Security, Section on External User Authentication).

2. HPE Ezmeral Container Platform 5.3 Tenant Storage and User Management: The documentation on creating and managing tenants and clusters explains how to attach secrets to Kubernetes clusters. When creating a Notebook cluster, the "Connections" setting is used to link secrets. The guide specifies adding hpecp-ext-auth-secret as a "secret" type connection to enable SSO for the notebook. (Reference: Chapter on Tenant Administration, Section on Creating Kubernetes Clusters).

3. HPE Ezmeral Runtime Enterprise Documentation (formerly Ezmeral Container Platform): In the tutorial "Setting up an AI/ML Project," the steps for creating a Jupyter Notebook cluster explicitly show adding a "Connection" of type "Secret" and selecting hpecp-ext-auth-secret from the dropdown list to enable authentication for external users. This step is crucial for the described scenario to work correctly. (Reference: Official HPE Ezmeral Runtime Enterprise Tutorials and How-To Guides).

Scroll to Top