Download Implementing Data Engineering Solutions Using Azure Databricks.DP-750.PassLeader.2026-11-17.74q.vcex

Vendor: Microsoft
Exam Code: DP-750
Exam Name: Implementing Data Engineering Solutions Using Azure Databricks
Date: Nov 17, 2026
File Size: 2 MB

How to open VCEX files?

Files with VCEX extension can be opened by ProfExam Simulator.

Demo Questions

Question 1
You have an Azure Databricks workspace that is enabled for Unity Catalog and contains a catalog named Catalog1. Catalog1 contains a table named Transactions. Transactions contains the following columns: 
- transaction_id 
- customer_name 
- email_address 
- credit_card_number 
- transaction_amount 
You need to ensure that business analysts can query all the rows in the Transactions table. The solution must meet the following requirements: 
- Prevent the analysts from seeing the full values in the email_address and credit_card_number columns. 
- Ensure that the analysts can see only the values after the @ character in each email address. 
- Ensure that the analysts can see only the last four digits of each credit card number. 
- Enable the analysts to query the table without errors. 
- Follow the principle of least privilege. 
What should you do? 
  1. Grant the analysts the SELECT permission for the Transactions table and apply column-level encryption. 
  2. Grant the analysts the SELECT permission for columns that do NOT contain sensitive data. 
  3. Grant the analysts the SELECT permission for the Transactions table and implement row-level filters. 
  4. Grant the analysts the SELECT permission for the Transactions table and apply column masks to email_address and credit_card_number. 
Correct answer: D
Explanation:
To protect sensitive customer information while allowing a specific group to run queries, use Unity Catalog's Dynamic Column Masking. This grants the group table access while applying User-Defined Functions (UDFs) to redact the email addresses and credit card numbers dynamically. Here is the exact SQL implementation to apply: 1. Create the masking SQL UDFs Define functions to apply the exact partial masking rules requested. 2. Apply the column masks to the tableAlter the transaction table to attach these UDFs to the respective columns. 3. Grant least privilege permissionsGrant the group the SELECT permission on the table, along with the foundational permissions to access the catalog and schema. Reference: https://docs.databricks.com/aws/en/data-governance/unity-catalog/filters-and-masks
To protect sensitive customer information while allowing a specific group to run queries, use Unity Catalog's Dynamic Column Masking. This grants the group table access while applying User-Defined Functions (UDFs) to redact the email addresses and credit card numbers dynamically. 
Here is the exact SQL implementation to apply: 
1. Create the masking SQL UDFs 
Define functions to apply the exact partial masking rules requested. 
2. Apply the column masks to the tableAlter the transaction table to attach these UDFs to the respective columns. 
3. Grant least privilege permissionsGrant the group the SELECT permission on the table, along with the foundational permissions to access the catalog and schema. 
Reference: 
https://docs.databricks.com/aws/en/data-governance/unity-catalog/filters-and-masks
Question 2
Note: This section contains one or more sets of questions with the same scenario and problem. Each question presents a unique solution to the problem. You must determine whether the solution meets the stated goals. More than one solution in the set might solve the problem. It is also possible that none of the solutions in the set solve the problem. 
After you answer a question in this section, you will NOT be able to return. As a result, these questions do not appear on the Review Screen. 
You have an Azure Databricks workspace named Workspace1 that contains a lakehouse and is enabled for Unity Catalog. 
You have a connection to a Microsoft SQL Server database named DB1. 
You need to expose the schemas and tables of DB1 to meet the following requirements: 
- The schemas and tables can be queried in Databricks. 
- The schemas and tables appear alongside other Unity Catalog objects. 
- The data is NOT copied into Databricks-managed storage. 
Solution: You create a Lakeflow Connect pipeline and connect it to DB1. 
Does this meet the goal? 
  1. Yes 
  2. No 
Correct answer: B
Explanation:
Correct: * You create a foreign catalog in Catalog Explorer. You should create a Foreign Catalog using Lakehouse Federation. Data Copying: Lakehouse Federation queries data directly in the source SQL Server without moving or copying it. Seamless Integration: The database schemas and tables appear right inside Unity Catalog alongside your other data objects.Real-time Access: It provides immediate access to live SQL Server data. Incorrect: * You create a Databricks access connector. * You create a Lakeflow Connect pipeline and connect it to DB1. Data Copying: Lakeflow Connect is an ingestion tool that physically replicates and copies data into Databricks-managed storage (Delta tables). Storage Costs: It violates your requirement to keep data out of Databricks storage. * You create a new native catalog in Unity Catalog. Note: To expose the external SQL Server database in Unity Catalog without copying the data, you must use Lakehouse Federation. Here are the step-by-step actions you need to take: 1. Create a Connection Create a securable object in Unity Catalog that specifies the path and credentials to access the SQL Server database. Go to Catalog Explorer or use SQL. Select External Data > Connections. Create a connection using the SQL Server connection details (URL, host, port, and database credentials). *-> 2. Create a Foreign Catalog Create a specific type of catalog in Unity Catalog that mirrors the external database. Use the CREATE FOREIGN CATALOG SQL command or the Catalog Explorer UI. Link this foreign catalog directly to the connection you created in step 1. 3. Query the DataOnce the foreign catalog is created, Unity Catalog automatically syncs the schemas and tables from SQL Server. Reference: https://docs.databricks.com/gcp/en/database-objects/
Correct: 
* You create a foreign catalog in Catalog Explorer. 
You should create a Foreign Catalog using Lakehouse Federation. 
Data Copying: Lakehouse Federation queries data directly in the source SQL Server without moving or copying it. 
Seamless Integration: The database schemas and tables appear right inside Unity Catalog alongside your other data objects.Real-time Access: It provides immediate access to live SQL Server data. 
Incorrect: 
* You create a Databricks access connector. 
* You create a Lakeflow Connect pipeline and connect it to DB1. 
Data Copying: Lakeflow Connect is an ingestion tool that physically replicates and copies data into Databricks-managed storage (Delta tables). 
Storage Costs: It violates your requirement to keep data out of Databricks storage. 
* You create a new native catalog in Unity Catalog. 
Note: 
To expose the external SQL Server database in Unity Catalog without copying the data, you must use Lakehouse Federation. 
Here are the step-by-step actions you need to take: 
1. Create a Connection 
Create a securable object in Unity Catalog that specifies the path and credentials to access the SQL Server database. 
Go to Catalog Explorer or use SQL. 
Select External Data > Connections. 
Create a connection using the SQL Server connection details (URL, host, port, and database credentials). 
*-> 2. Create a Foreign Catalog 
Create a specific type of catalog in Unity Catalog that mirrors the external database. 
Use the CREATE FOREIGN CATALOG SQL command or the Catalog Explorer UI. 
Link this foreign catalog directly to the connection you created in step 1. 
3. Query the DataOnce the foreign catalog is created, Unity Catalog automatically syncs the schemas and tables from SQL Server. 
Reference: 
https://docs.databricks.com/gcp/en/database-objects/
Question 3
Note: This section contains one or more sets of questions with the same scenario and problem. Each question presents a unique solution to the problem. You must determine whether the solution meets the stated goals. More than one solution in the set might solve the problem. It is also possible that none of the solutions in the set solve the problem. 
After you answer a question in this section, you will NOT be able to return. As a result, these questions do not appear on the Review Screen. 
You have an Azure Databricks workspace named Workspace1 that contains a lakehouse and is enabled for Unity Catalog. 
You have a connection to a Microsoft SQL Server database named DB1. 
You need to expose the schemas and tables of DB1 to meet the following requirements: 
- The schemas and tables can be queried in Databricks. 
- The schemas and tables appear alongside other Unity Catalog objects. 
- The data is NOT copied into Databricks-managed storage. 
Solution: You create a Databricks access connector. 
Does this meet the goal? 
  1. Yes 
  2. No 
Correct answer: B
Explanation:
Correct: * You create a foreign catalog in Catalog Explorer. You should create a Foreign Catalog using Lakehouse Federation. Data Copying: Lakehouse Federation queries data directly in the source SQL Server without moving or copying it. Seamless Integration: The database schemas and tables appear right inside Unity Catalog alongside your other data objects.Real-time Access: It provides immediate access to live SQL Server data. Incorrect: * You create a Databricks access connector. * You create a Lakeflow Connect pipeline and connect it to DB1. Data Copying: Lakeflow Connect is an ingestion tool that physically replicates and copies data into Databricks-managed storage (Delta tables). Storage Costs: It violates your requirement to keep data out of Databricks storage. * You create a new native catalog in Unity Catalog. Note: To expose the external SQL Server database in Unity Catalog without copying the data, you must use Lakehouse Federation. Here are the step-by-step actions you need to take: 1. Create a Connection Create a securable object in Unity Catalog that specifies the path and credentials to access the SQL Server database. Go to Catalog Explorer or use SQL. Select External Data > Connections. Create a connection using the SQL Server connection details (URL, host, port, and database credentials). *-> 2. Create a Foreign Catalog Create a specific type of catalog in Unity Catalog that mirrors the external database. Use the CREATE FOREIGN CATALOG SQL command or the Catalog Explorer UI. Link this foreign catalog directly to the connection you created in step 1. 3. Query the DataOnce the foreign catalog is created, Unity Catalog automatically syncs the schemas and tables from SQL Server. Reference: https://docs.databricks.com/gcp/en/database-objects/
Correct: 
* You create a foreign catalog in Catalog Explorer. 
You should create a Foreign Catalog using Lakehouse Federation. 
Data Copying: Lakehouse Federation queries data directly in the source SQL Server without moving or copying it. 
Seamless Integration: The database schemas and tables appear right inside Unity Catalog alongside your other data objects.Real-time Access: It provides immediate access to live SQL Server data. 
Incorrect: 
* You create a Databricks access connector. 
* You create a Lakeflow Connect pipeline and connect it to DB1. 
Data Copying: Lakeflow Connect is an ingestion tool that physically replicates and copies data into Databricks-managed storage (Delta tables). 
Storage Costs: It violates your requirement to keep data out of Databricks storage. 
* You create a new native catalog in Unity Catalog. 
Note: 
To expose the external SQL Server database in Unity Catalog without copying the data, you must use Lakehouse Federation. 
Here are the step-by-step actions you need to take: 
1. Create a Connection 
Create a securable object in Unity Catalog that specifies the path and credentials to access the SQL Server database. 
Go to Catalog Explorer or use SQL. 
Select External Data > Connections. 
Create a connection using the SQL Server connection details (URL, host, port, and database credentials). 
*-> 2. Create a Foreign Catalog 
Create a specific type of catalog in Unity Catalog that mirrors the external database. 
Use the CREATE FOREIGN CATALOG SQL command or the Catalog Explorer UI. 
Link this foreign catalog directly to the connection you created in step 1. 
3. Query the DataOnce the foreign catalog is created, Unity Catalog automatically syncs the schemas and tables from SQL Server. 
Reference: 
https://docs.databricks.com/gcp/en/database-objects/
Question 4
Note: This section contains one or more sets of questions with the same scenario and problem. Each question presents a unique solution to the problem. You must determine whether the solution meets the stated goals. More than one solution in the set might solve the problem. It is also possible that none of the solutions in the set solve the problem. 
After you answer a question in this section, you will NOT be able to return. As a result, these questions do not appear on the Review Screen. 
You have an Azure Databricks workspace named Workspace1 that contains a lakehouse and is enabled for Unity Catalog. 
You have a connection to a Microsoft SQL Server database named DB1. 
You need to expose the schemas and tables of DB1 to meet the following requirements: 
- The schemas and tables can be queried in Databricks. 
- The schemas and tables appear alongside other Unity Catalog objects. 
- The data is NOT copied into Databricks-managed storage. 
Solution: You create a foreign catalog in Catalog Explorer. 
Does this meet the goal? 
  1. Yes 
  2. No 
Correct answer: A
Explanation:
Correct: * You create a foreign catalog in Catalog Explorer. You should create a Foreign Catalog using Lakehouse Federation. Data Copying: Lakehouse Federation queries data directly in the source SQL Server without moving or copying it. Seamless Integration: The database schemas and tables appear right inside Unity Catalog alongside your other data objects.Real-time Access: It provides immediate access to live SQL Server data. Incorrect: * You create a Databricks access connector. * You create a Lakeflow Connect pipeline and connect it to DB1. Data Copying: Lakeflow Connect is an ingestion tool that physically replicates and copies data into Databricks-managed storage (Delta tables). Storage Costs: It violates your requirement to keep data out of Databricks storage. * You create a new native catalog in Unity Catalog. Note: To expose the external SQL Server database in Unity Catalog without copying the data, you must use Lakehouse Federation. Here are the step-by-step actions you need to take: 1. Create a Connection Create a securable object in Unity Catalog that specifies the path and credentials to access the SQL Server database. Go to Catalog Explorer or use SQL. Select External Data > Connections. Create a connection using the SQL Server connection details (URL, host, port, and database credentials). *-> 2. Create a Foreign Catalog Create a specific type of catalog in Unity Catalog that mirrors the external database. Use the CREATE FOREIGN CATALOG SQL command or the Catalog Explorer UI. Link this foreign catalog directly to the connection you created in step 1. 3. Query the DataOnce the foreign catalog is created, Unity Catalog automatically syncs the schemas and tables from SQL Server. Reference: https://docs.databricks.com/gcp/en/database-objects/
Correct: 
* You create a foreign catalog in Catalog Explorer. 
You should create a Foreign Catalog using Lakehouse Federation. 
Data Copying: Lakehouse Federation queries data directly in the source SQL Server without moving or copying it. 
Seamless Integration: The database schemas and tables appear right inside Unity Catalog alongside your other data objects.Real-time Access: It provides immediate access to live SQL Server data. 
Incorrect: 
* You create a Databricks access connector. 
* You create a Lakeflow Connect pipeline and connect it to DB1. 
Data Copying: Lakeflow Connect is an ingestion tool that physically replicates and copies data into Databricks-managed storage (Delta tables). 
Storage Costs: It violates your requirement to keep data out of Databricks storage. 
* You create a new native catalog in Unity Catalog. 
Note: 
To expose the external SQL Server database in Unity Catalog without copying the data, you must use Lakehouse Federation. 
Here are the step-by-step actions you need to take: 
1. Create a Connection 
Create a securable object in Unity Catalog that specifies the path and credentials to access the SQL Server database. 
Go to Catalog Explorer or use SQL. 
Select External Data > Connections. 
Create a connection using the SQL Server connection details (URL, host, port, and database credentials). 
*-> 2. Create a Foreign Catalog 
Create a specific type of catalog in Unity Catalog that mirrors the external database. 
Use the CREATE FOREIGN CATALOG SQL command or the Catalog Explorer UI. 
Link this foreign catalog directly to the connection you created in step 1. 
3. Query the DataOnce the foreign catalog is created, Unity Catalog automatically syncs the schemas and tables from SQL Server. 
Reference: 
https://docs.databricks.com/gcp/en/database-objects/
Question 5
Note: This section contains one or more sets of questions with the same scenario and problem. Each question presents a unique solution to the problem. You must determine whether the solution meets the stated goals. More than one solution in the set might solve the problem. It is also possible that none of the solutions in the set solve the problem. 
After you answer a question in this section, you will NOT be able to return. As a result, these questions do not appear on the Review Screen. 
You have an Azure Databricks workspace named Workspace1 that contains a lakehouse and is enabled for Unity Catalog. 
You have a connection to a Microsoft SQL Server database named DB1. 
You need to expose the schemas and tables of DB1 to meet the following requirements: 
- The schemas and tables can be queried in Databricks. 
- The schemas and tables appear alongside other Unity Catalog objects. 
- The data is NOT copied into Databricks-managed storage. 
Solution: You create a new native catalog in Unity Catalog. 
Does this meet the goal? 
  1. Yes 
  2. No 
Correct answer: B
Explanation:
Correct: * You create a foreign catalog in Catalog Explorer. You should create a Foreign Catalog using Lakehouse Federation. Data Copying: Lakehouse Federation queries data directly in the source SQL Server without moving or copying it. Seamless Integration: The database schemas and tables appear right inside Unity Catalog alongside your other data objects.Real-time Access: It provides immediate access to live SQL Server data. Incorrect: * You create a Databricks access connector. * You create a Lakeflow Connect pipeline and connect it to DB1. Data Copying: Lakeflow Connect is an ingestion tool that physically replicates and copies data into Databricks-managed storage (Delta tables). Storage Costs: It violates your requirement to keep data out of Databricks storage. * You create a new native catalog in Unity Catalog. Note: To expose the external SQL Server database in Unity Catalog without copying the data, you must use Lakehouse Federation. Here are the step-by-step actions you need to take: 1. Create a Connection Create a securable object in Unity Catalog that specifies the path and credentials to access the SQL Server database. Go to Catalog Explorer or use SQL. Select External Data > Connections. Create a connection using the SQL Server connection details (URL, host, port, and database credentials). *-> 2. Create a Foreign Catalog Create a specific type of catalog in Unity Catalog that mirrors the external database. Use the CREATE FOREIGN CATALOG SQL command or the Catalog Explorer UI. Link this foreign catalog directly to the connection you created in step 1. 3. Query the DataOnce the foreign catalog is created, Unity Catalog automatically syncs the schemas and tables from SQL Server. Reference: https://docs.databricks.com/gcp/en/database-objects/
Correct: 
* You create a foreign catalog in Catalog Explorer. 
You should create a Foreign Catalog using Lakehouse Federation. 
Data Copying: Lakehouse Federation queries data directly in the source SQL Server without moving or copying it. 
Seamless Integration: The database schemas and tables appear right inside Unity Catalog alongside your other data objects.Real-time Access: It provides immediate access to live SQL Server data. 
Incorrect: 
* You create a Databricks access connector. 
* You create a Lakeflow Connect pipeline and connect it to DB1. 
Data Copying: Lakeflow Connect is an ingestion tool that physically replicates and copies data into Databricks-managed storage (Delta tables). 
Storage Costs: It violates your requirement to keep data out of Databricks storage. 
* You create a new native catalog in Unity Catalog. 
Note: 
To expose the external SQL Server database in Unity Catalog without copying the data, you must use Lakehouse Federation. 
Here are the step-by-step actions you need to take: 
1. Create a Connection 
Create a securable object in Unity Catalog that specifies the path and credentials to access the SQL Server database. 
Go to Catalog Explorer or use SQL. 
Select External Data > Connections. 
Create a connection using the SQL Server connection details (URL, host, port, and database credentials). 
*-> 2. Create a Foreign Catalog 
Create a specific type of catalog in Unity Catalog that mirrors the external database. 
Use the CREATE FOREIGN CATALOG SQL command or the Catalog Explorer UI. 
Link this foreign catalog directly to the connection you created in step 1. 
3. Query the DataOnce the foreign catalog is created, Unity Catalog automatically syncs the schemas and tables from SQL Server. 
Reference: 
https://docs.databricks.com/gcp/en/database-objects/
Question 6
You have an Azure Databricks workspace that uses serverless compute. 
You need to ingest data by using Lakeflow Jobs. New records must be processed as soon as they become available. 
Which type of job trigger should you use for the ingestion? 
  1. manual 
  2. file arrival 
  3. scheduled 
  4. continuous 
Correct answer: D
Explanation:
The best trigger type for this scenario is the Continuous trigger. Immediate Processing: The Continuous trigger mode processes new records as soon as they arrive at the configured data sources. This matches your requirement to ingest and process records without waiting for an artificial time interval. Native Serverless Support: When paired with serverless compute, Lakeflow Jobs efficiently manage resources by automatically scaling up or down according to the real-time stream volume. Built-in Fault Tolerance: Continuous pipelines on Databricks automatically handle failures by retrying with an exponential backoff policy, keeping your automated ingestion operational 24/7 without manual intervention. Reference: https://docs.databricks.com/aws/en/jobs/continuous
The best trigger type for this scenario is the Continuous trigger. 
Immediate Processing: The Continuous trigger mode processes new records as soon as they arrive at the configured data sources. This matches your requirement to ingest and process records without waiting for an artificial time interval. 
Native Serverless Support: When paired with serverless compute, Lakeflow Jobs efficiently manage resources by automatically scaling up or down according to the real-time stream volume. 
Built-in Fault Tolerance: Continuous pipelines on Databricks automatically handle failures by retrying with an exponential backoff policy, keeping your automated ingestion operational 24/7 without manual intervention. 
Reference: 
https://docs.databricks.com/aws/en/jobs/continuous
Question 7
You have an Azure Databricks workspace that is enabled for Unity Catalog and contains a managed Delta table named Sales. 
Sales stores transaction data and contains the following columns: 
- transaction_id (string) 
- transaction_date (date) 
- amount (decimal) 
You need to implement the following data quality requirements by using table-level data quality enforcement: 
- amount must be greater than 0. 
- transaction_id must never be null. 
- Invalid records must be rejected when data is written to the Sales table. 
What should you do? 
  1. Use a SELECT statement with WHERE conditions to validate the data before querying. 
  2. Create a view that filters out rows where transaction_id is null or amount is less than or equal to 0. 
  3. Add a NOT NULL constraint to transaction_id and a CHECK constraint to amount. 
  4. Configure row-level security (RLS) where transaction_id is null or amount is less than or equal to 0. 
Correct answer: C
Explanation:
To enforce these table-level data quality rules and automatically reject any invalid write operations in Azure Databricks, you must configure NOT NULL and CHECK constraints on the Delta table using standard SQL commands. In Delta Lake, these constraints are enforced instantly on write. If an incoming record violates any of them, the entire transaction fails, and the invalid records are rejected. 1. Enforce transaction_id Cannot Be Null Add a NOT NULL constraint to the transaction_id column. This blocks any write attempt containing a null identifier. ALTER TABLE sales_data ALTER COLUMN transaction_id SET NOT NULL; 2. Enforce amount Must Be Greater Than 0 Add a CHECK constraint to the table to validate that the amount values strictly exceed zero. ALTER TABLE sales_data ADD CONSTRAINT check_amount_positive CHECK (amount > 0); Reference: https://docs.databricks.com/aws/en/tables/constraints
To enforce these table-level data quality rules and automatically reject any invalid write operations in Azure Databricks, you must configure NOT NULL and CHECK constraints on the Delta table using standard SQL commands. 
In Delta Lake, these constraints are enforced instantly on write. If an incoming record violates any of them, the entire transaction fails, and the invalid records are rejected. 
1. Enforce transaction_id Cannot Be Null 
Add a NOT NULL constraint to the transaction_id column. This blocks any write attempt containing a null identifier. 
ALTER TABLE sales_data ALTER COLUMN transaction_id SET NOT NULL; 
2. Enforce amount Must Be Greater Than 0 
Add a CHECK constraint to the table to validate that the amount values strictly exceed zero. 
ALTER TABLE sales_data ADD CONSTRAINT check_amount_positive CHECK (amount > 0); 
Reference: 
https://docs.databricks.com/aws/en/tables/constraints
Question 8
You have an Azure Databricks workspace that is enabled for Unity Catalog and contains two Delta tables named Table1 and Table2 of the same data type. 
Table1 contains a column named Column1. Table2 contains a column named Column2. 
You run the following query. 
SELECT Colum1 
FROM Table1 
GROUP BY Column1 
HAVING COUNT(*) > 1 
INTERSECT 
SELECT Column2 
FROM Table2 
GROUP BY Column2 
HAVING COUNT(*) > 1; 
What occurs when you run the query? 
  1. Values appear in both tables more than once. 
  2. Values appear in either table more than once. 
  3. Values appear in Table2 but NOT Table1. 
  4. Values appear in Table1 more than once. 
Correct answer: A
Explanation:
The query will output a single column containing only the values that are duplicated within Table1 and also duplicated within Table2. Duplicates Isolated First: The GROUP BY and HAVING COUNT(*) > 1 clauses filter each table independently to find only their duplicate rows. Matching Values Found: The INTERSECT operator compares the filtered results of both tables. Shared Values Returned: Only values that exist in both filtered datasets are included in the final output. Automatic Distinct Filtering: INTERSECT automatically removes any duplicate values from the final result set, ensuring each matching value appears exactly once. Column Naming: The output column will inherit its name from the first SELECT statement (Column1). Reference: https://quizlet.com/study-guides/inf3707-chapter-4-data-retrieval-from-2-or-more-tables-6ec17b26-76a8-4c33-8fa7-18d64154512d 
The query will output a single column containing only the values that are duplicated within Table1 and also duplicated within Table2. 
Duplicates Isolated First: The GROUP BY and HAVING COUNT(*) > 1 clauses filter each table independently to find only their duplicate rows. 
Matching Values Found: The INTERSECT operator compares the filtered results of both tables. 
Shared Values Returned: Only values that exist in both filtered datasets are included in the final output. 
Automatic Distinct Filtering: INTERSECT automatically removes any duplicate values from the final result set, ensuring each matching value appears exactly once. 
Column Naming: The output column will inherit its name from the first SELECT statement (Column1). 
Reference: 
https://quizlet.com/study-guides/inf3707-chapter-4-data-retrieval-from-2-or-more-tables-6ec17b26-76a8-4c33-8fa7-18d64154512d 
Question 9
You have an Azure Databricks workspace that contains multiple all-purpose clusters. 
You discover that some clusters remain idle for long periods after users finish their work. 
You need to reduce compute costs without affecting active workloads. 
What should you do? 
  1. Enable autoscaling. 
  2. Convert the clusters into job clusters. 
  3. Use spot instances. 
  4. Configure automatic termination. 
Correct answer: D
Explanation:
To reduce compute costs from idle clusters without impacting active workloads, you must configure Auto-Termination and use Cluster Policies. Core Remedies *-> Auto-Termination: Set a strict inactivity timeout (e.g., 20–30 minutes) on all-purpose clusters to automatically shut them down when idle. Cluster Policies: Enforce maximum auto-termination limits across the workspace so users cannot disable or set excessively long idle timeouts. Single User Access Mode: Use this mode where possible, as it tracks idleness more accurately than Shared mode by monitoring the specific user's activity. Reference: https://medium.com/@sujathamudadla1213/databricks-lakehouse-platform-describe-how-clusters-are-terminated-and-the-impact-of-terminating-a-b6236689fd2e 
To reduce compute costs from idle clusters without impacting active workloads, you must configure Auto-Termination and use Cluster Policies. 
Core Remedies 
*-> Auto-Termination: Set a strict inactivity timeout (e.g., 20–30 minutes) on all-purpose clusters to automatically shut them down when idle. 
Cluster Policies: Enforce maximum auto-termination limits across the workspace so users cannot disable or set excessively long idle timeouts. 
Single User Access Mode: Use this mode where possible, as it tracks idleness more accurately than Shared mode by monitoring the specific user's activity. 
Reference: 
https://medium.com/@sujathamudadla1213/databricks-lakehouse-platform-describe-how-clusters-are-terminated-and-the-impact-of-terminating-a-b6236689fd2e 
Question 10
You have an Azure Databricks workspace. 
You have an Apache Spark Structured Streaming job named Job1 that processes data 
continuously and fails periodically due to transient errors. 
You need to ensure that Job1 meets the following requirements: 
- Resumes processing from the point that Job1 failed 
- Minimizes how long it takes to restart Job1 
- Minimizes the costs to restart Job1 
What should you do? 
  1. Decrease the retry interval. 
  2. Increase the minimum number of nodes in the cluster. 
  3. Add an alert and manually restart Job1. 
  4. Implement checkpointing. 
Correct answer: D
Explanation:
You must use checkpointing. Checkpointing is the native Apache Spark mechanism designed specifically to handle failures in Structured Streaming jobs. It saves the exact execution state and progress to cloud storage (like Azure Data Lake Storage), allowing the job to resume precisely where it left off without data loss. Resumes from Failure Point: The checkpoint directory stores the stream offsets. When restarted, Spark reads these offsets to pick up exactly where it failed. Minimizes Restart Time: By saving the state, Spark does not need to recompute historical streaming data or re-evaluate the entire stream architecture from scratch. Minimizes Restart Costs: It prevents the reprocessing of duplicate data, saving valuable cluster compute time and reducing cloud infrastructure costs. Reference: https://www.linkedin.com/posts/shilpa-das-ln_what-is-checkpointing-in-spark-checkpointing-activity-7297113790393815041-AhPg 
You must use checkpointing. 
Checkpointing is the native Apache Spark mechanism designed specifically to handle failures in Structured Streaming jobs. It saves the exact execution state and progress to cloud storage (like Azure Data Lake Storage), allowing the job to resume precisely where it left off without data loss. 
Resumes from Failure Point: The checkpoint directory stores the stream offsets. When restarted, Spark reads these offsets to pick up exactly where it failed. 
Minimizes Restart Time: By saving the state, Spark does not need to recompute historical streaming data or re-evaluate the entire stream architecture from scratch. 
Minimizes Restart Costs: It prevents the reprocessing of duplicate data, saving valuable cluster compute time and reducing cloud infrastructure costs. 
Reference: 
https://www.linkedin.com/posts/shilpa-das-ln_what-is-checkpointing-in-spark-checkpointing-activity-7297113790393815041-AhPg 
HOW TO OPEN VCE FILES

Use VCE Exam Simulator to open VCE files
Avanaset

HOW TO OPEN VCEX FILES

Use ProfExam Simulator to open VCEX files
ProfExam Screen

ProfExam
ProfExam at a 20% markdown

You have the opportunity to purchase ProfExam at a 20% reduced price

Get Now!