Databricks-GenAI-Assoc Assembling and Deploying Apps Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Grant the endpoint access to the entire Unity Catalog.

  Why it's wrong here

  Granting excessive access to the entire catalog violates the principle of least privilege and increases security risks significantly. Access should always be limited to only the specific tables or files required by the model for its operation, ensuring that data exposure is minimized in the event of unauthorized access.

• ✓

  Use a Service Principal with scoped permissions for the model.

  Why this is correct

  Using a dedicated Service Principal with finely-tuned permissions ensures that the serving endpoint can only access the specific data assets required for its tasks. This aligns with security best practices by minimizing risk and ensuring that the model does not have broad access to sensitive corporate information.

• ✗

  Store credentials in plaintext in the model code.

  Why it's wrong here

  Storing credentials in plaintext is a catastrophic security failure that exposes secrets to anyone who can read the code. This is an unacceptable practice and is strictly forbidden in any professional environment. Secrets must always be managed using secure tools like Databricks Secrets or Unity Catalog security features.

• ✗

  Bypass Unity Catalog to use local file system access.

  Why it's wrong here

  Bypassing Unity Catalog undermines the central governance and auditing framework that Databricks provides. It prevents the tracking of data lineage and the enforcement of fine-grained access policies, creating significant security and compliance risks that are unacceptable in enterprise-grade applications handling sensitive data.