CCNA Governance Questions

Databricks secrets provide a secure, encrypted store for sensitive credentials such as API keys. They can be referenced in code and in external model endpoint configurations without revealing the secret value. This meets the requirement to keep the OpenAI API key secure and out of code and logs.

Unity Catalog registered models are the correct object for governing machine learning models. They provide a three-level namespace and support fine-grained access control, versioning, and auditing. By registering the fine-tuned model as a Unity Catalog model, the engineer can manage access and track usage, satisfying the governance requirement.

Column masks are the Unity Catalog mechanism designed to transform individual column values based on the caller's group membership while leaving the table itself queryable by everyone. Binding a mask function to prompt_text that checks is_account_group_member('ai_compliance') gives compliance staff the raw text and returns REDACTED to all other users, meeting the requirement on the existing table.

Row filters and column masks in Unity Catalog are applied dynamically based on the identity executing the query. When a vector search index is queried with end-user identity propagation, the source table's policies are evaluated, so sensitive transcript fields are masked and rows are filtered according to group membership. This satisfies the security team's requirement without duplicating policies on the index.

To control who can invoke a model served by Databricks, you grant the EXECUTE privilege on the model version in Unity Catalog. Inference tables are a built-in feature of Model Serving that automatically log request and response data to a Delta table for auditing and monitoring. This combination directly addresses the security team's requirements for access restriction and request logging.

Row filters evaluate the invoking user's identity as part of the query, so placing the filter on the source Delta table means every read, including retrieval reads that feed similarity search, is automatically scoped to allowed rows. This keeps a single governed index and avoids per-department duplication while still enforcing per-user document visibility at query time.

The System Tables (specifically the access_logs table) in Unity Catalog provide detailed audit logs of all interactions with data objects. By querying these tables using SQL, administrators can monitor data access patterns, identify unauthorized attempts to view sensitive data, and fulfill audit requirements. This centralized logging is a cornerstone of the governance transparency provided by Unity Catalog.

Databricks Vector Search enables document-level security by allowing metadata filtering at query time. The engineer can include authorization attributes (such as group memberships) as metadata fields when creating the index, then pass a filter expression in the query that matches the user's attributes. This enforces access control without duplicating the index, aligning with the requirement to keep a single index while restricting retrieval to authorized documents.

Governed tags provide a structured, searchable classification layer in Unity Catalog that can be attached to columns and referenced by policy and discovery tooling. Applying a sensitivity tag to the transcript column gives security a consistent label for the training data, enabling uniform policy enforcement and auditability rather than relying on informal comments or access mechanisms.

Delta Sharing is designed for secure cross-organization data sharing without copying. By creating a share with only the prompt templates and evaluation datasets, the company limits exposure to those assets. The partner accesses the share from their own Databricks account, and the company can revoke access by removing the recipient, satisfying both isolation and revocation needs.

Unity Catalog row-level security and column-level masking allow for dynamic data governance. By applying a masking function using 'current_user_role()' or 'is_account_group_member()', administrators can ensure that users see redacted data without duplicating the underlying storage. This approach centralizes governance policies, simplifies auditing, and ensures that sensitive data exposure is strictly controlled at the query execution time across all compute resources within the Unity Catalog metastore environment.

Model serving endpoints registered in Unity Catalog are secured with the EXECUTE privilege. To allow only the 'genai_users' group to invoke the endpoint, an administrator must grant EXECUTE on the endpoint to that group. This ensures that only authorized users can call the endpoint, meeting the access-control requirement.

To query an external table, the user needs access to the storage location, the catalog, the schema, and the table. The administrator must grant the USAGE privilege on the catalog and schema, the SELECT privilege on the table, and the READ FILES privilege on the external location. This multi-layered approach ensures that data access is both logically and physically controlled.

Registering an MLflow experiment in Unity Catalog makes it a securable object, allowing you to grant privileges to specific groups. Artifacts are stored in a governed location such as a Unity Catalog volume or external location. This provides both access control and governance, meeting the team's requirements.

The Unity Catalog identity model is unified at the account level, meaning that identities are managed consistently across all workspaces. The core components are Users and Groups. By centralizing these identities in the account console, Databricks ensures that permissions are applied uniformly, regardless of which workspace a user is accessing, which is critical for large-scale enterprise governance and audit compliance.

Reading a table in Unity Catalog requires traversing the namespace and holding a data privilege. USE CATALOG on the catalog and USE SCHEMA on the schema make the table addressable, and SELECT on the table, or on the schema for broad coverage, authorizes the read. Together these two statements describe the minimum privilege set that lets the developers query the RAG pipeline's tables without over-granting administrative rights.

Creating a table in Unity Catalog involves a specific permission chain. The user must have USAGE on the catalog, USAGE on the schema, and the CREATE TABLE privilege on the schema. These requirements ensure that governance is maintained at every level of the hierarchy, preventing unauthorized data creation in sensitive or restricted namespaces within the organization's data architecture.

Volumes in Unity Catalog are designed specifically for managing non-tabular data, such as JSON files, CSVs, or machine learning models. By creating a volume, you can govern access to these files using the same security model as tables. This allows for consistent data governance across all types of assets in your environment, not just those formatted as Delta tables.

Audit logs in system tables capture all access and query events, including those against Vector Search indexes. They record the user, action, and timestamp, enabling the engineer to audit who queried the index and when. This is the appropriate Unity Catalog feature for meeting the security team's auditing requirement.

Registered models in Unity Catalog are invoked under the EXECUTE privilege, which authorizes a principal to call the model without granting ownership or modification rights. Granting EXECUTE to the application's identity, alongside any needed USE CATALOG and USE SCHEMA to resolve the path, provides least-privilege inference access for the downstream application.

Unity Catalog lineage automatically tracks the flow of data through notebooks, jobs, and models, including the training dataset used to produce a model version. This gives the governance team an auditable, automated trace from model to data. Manual methods such as tags or comments are not reliable for compliance.

The 'metastores.list' command allows administrators to view all Unity Catalog metastores that the current user has permission to see within their Databricks account. This is essential for managing multiple metastores in a complex, multi-region architecture. Understanding which metastores exist and their properties is the first step in ensuring that data governance policies are consistently applied across all regional footprints.

An External Location in Unity Catalog acts as a secure bridge between Databricks and a specific path in cloud storage (e.g., S3 or ADLS). By using a Storage Credential, the external location allows data engineers to manage storage access at a high level. This simplifies data governance by abstracting cloud-specific permissions into Databricks-native access controls.

A Storage Credential serves as a secure container for the cloud-provider credentials required to access external storage locations. By separating the credential from the data objects, Unity Catalog allows administrators to manage access to cloud storage in a centralized, governed way without exposing secrets to individual users. This is a fundamental security practice that prevents credential leakage.

Inference tables logged by Databricks Model Serving are Delta tables that can be stored in Unity Catalog. Using a managed table in a Unity Catalog schema allows the team to apply Unity Catalog governance features such as grants, column masks, and row filters to protect sensitive data. This ensures that the inference logs are subject to the same security policies as other data assets, providing centralized governance and auditability.

Unity Catalog column masks are designed to dynamically redact column values based on the user's identity or group membership. By applying a mask function to PHI columns, the healthcare company can ensure that unauthorized users see redacted values while authorized users see the actual data. This enforcement occurs at the data layer, preventing PHI leakage even if the LLM is manipulated, and it applies to all queries against the table.

To invoke a model registered in Unity Catalog, a user must have the EXECUTE privilege on that model. Granting EXECUTE to the genai_team group ensures that only its members can call the model endpoint, aligning with the requirement to restrict access. Other privileges like SELECT, USE, or CREATE do not authorize model invocation.

Delta Sharing is an open-protocol standard that allows organizations to share data with users regardless of whether they have a Databricks account. It enables secure, read-only data sharing across different platforms and cloud environments. This is essential for organizations that need to collaborate with partners, vendors, or external clients while maintaining centralized control and auditability within Unity Catalog.

Dynamic column masking in Unity Catalog enables the data scientist to see masked values for sensitive columns based on their group membership. By applying a column mask that checks group membership, the raw values are hidden from unauthorized users while still allowing the data scientist to read the table for fine-tuning.

Unity Catalog dynamic data masking allows administrators to apply functions to columns that redact or obfuscate data based on the user's role or group membership. By using SQL functions like mask_email or custom UDFs within a masking policy, the data remains consistent at the physical layer while presenting transformed values at query time. This ensures compliance with privacy regulations without creating multiple copies of datasets.

In Unity Catalog, users require the USAGE privilege on all parent objects—the catalog and the schema—to access a table. While the user has USAGE on the catalog and SELECT on the tables, they lack the USAGE privilege on the 'sales' schema. Without explicit USAGE permission on the schema, the user cannot traverse the hierarchy to reference the tables, causing a permission denied error.

Meeting the governance objectives requires both an enforcement mechanism and an evidence trail. Fine-grained privileges on the relevant catalogs, schemas, tables, and models enforce least-privilege access to sensitive prompt data, while Unity Catalog audit logs record which principals accessed those governed objects, providing the traceability that production compliance reviews demand.

Foundation Model APIs are surfaced as Unity Catalog functions in the system.ai schema, so access is controlled with Unity Catalog privileges, chiefly EXECUTE on the relevant model function, plus the usual USE CATALOG and USE SCHEMA on system.ai. Directing the security team to those grants gives an auditable, centralized view of exactly which users and service principals can invoke each pay-per-token model.

A column mask on the sensitive note text column enforces redaction for unauthorized identities at query time, which is auditable. By having the RAG application consume a derived embeddings table instead of raw text, the application retains functionality while raw PHI remains protected. This keeps governance within Unity Catalog and satisfies the auditor's requirement.

OAuth machine-to-machine authentication lets an application present a service principal's client ID and secret to the Databricks OAuth token endpoint and receive an access token with a limited lifetime. The application has its own Unity Catalog identity, permissions can be granted to that principal on the registered model and serving endpoint, and token refresh happens automatically. This is the supported pattern for non-interactive workloads that must avoid long-lived secrets.

Unity Catalog privileges on the Vector Search index and source table provide fine-grained access control, ensuring only authorized users can retrieve data. Inference tables for the Foundation Model API automatically log requests and responses, including user identity, creating an audit trail. Together, these features meet the access-control and auditability requirements for the RAG application.