Databricks Data Engineer Associate Question 491
Select 3You are tasked with setting up a secure connection between an external application and your Databricks workspace for automated data processing. To accomplish this, you decide to use a service principal. Which of the following steps are required to define and configure a service principal in Databricks?
- A
Create the service principal in your cloud provider and assign the necessary IAM permissions.
- B
Generate a personal access token (PAT) for the service principal within the Databricks workspace.
- C
Add the service principal to Databricks using the Databricks CLI or REST API.
- D
Assign the service principal a Databricks workspace role, such as Admin or Contributor.
- E
Configure the service principal to automatically rotate its credentials within Databricks.
Show answer and explanation
Correct answers: A, C, D
Explanation
To define and configure a service principal for Databricks, you need to create it in your cloud provider, assign necessary IAM permissions, add it to Databricks, and assign it a workspace role. Service principals do not use personal access tokens, and their credential rotation is managed externally, not within Databricks.
- A. Correct.
Correct: A service principal must first be created in your cloud provider (e.g., Azure AD or AWS IAM) and provided with necessary IAM permissions to access resources securely.
- B. Incorrect.
Incorrect: Service principals do not use personal access tokens (PATs) for authentication. Instead, they use application secrets or certificates for authentication.
- C. Correct.
Correct: The service principal needs to be added to Databricks, which can be done using the Databricks CLI or REST API.
- D. Correct.
Correct: Once the service principal is added to Databricks, it must be assigned an appropriate workspace role (e.g., Admin, Contributor) to define its permissions within the Databricks workspace.
- E. Incorrect.
Incorrect: Credential rotation is not configured directly within Databricks for service principals. Credential management and rotation are handled outside Databricks, typically in the cloud provider or a secret management system.