{"id":18502,"date":"2026-09-22T07:33:12","date_gmt":"2026-09-22T07:33:12","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=18502"},"modified":"2026-09-22T07:33:12","modified_gmt":"2026-09-22T07:33:12","slug":"microsoft-dp-750-practice-test-questions-and-exam-dumps-part9-q161-180","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/microsoft-dp-750-practice-test-questions-and-exam-dumps-part9-q161-180\/","title":{"rendered":"Microsoft DP-750 Practice Test Questions and Exam Dumps Part9 Q161-180"},"content":{"rendered":"<h2><b>View Full <\/b><a href=\"https:\/\/www.examlabs.com\/dp-750-exam-dumps\"><b>Microsoft DP-750 Exam Dumps<\/b><\/a><b> and Practice Test Dumps.<\/b><\/h2>\n<p>&nbsp;<\/p>\n<h3><b>Question 161<\/b><\/h3>\n<p><b>Which Azure Databricks capability provides a centralized governance model for catalogs, schemas, tables, views, and volumes?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Unity Catalog<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Spark UI<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Git folders<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Cluster logs<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Unity Catalog provides centralized governance and access control for data assets across Azure Databricks. It supports a consistent permission model for catalogs, schemas, tables, views, volumes, external locations, and other supported securable objects. Administrators can assign privileges to users, groups, and service principals according to organizational requirements. Unity Catalog also supports data discovery and auditing capabilities that help organizations manage governed data environments. Spark UI is primarily used to inspect Spark execution, Git folders support source-control workflows, and cluster logs provide operational information. Therefore, Unity Catalog is the appropriate capability when centralized governance and access management are required across multiple data assets.<\/span><\/p>\n<h3><b>Question 162<\/b><\/h3>\n<p><b>Which Delta Lake operation can conditionally update, insert, or delete records based on whether source and target rows match?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">VACUUM<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">OPTIMIZE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">MERGE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DESCRIBE<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">MERGE provides conditional synchronization between a source dataset and a target Delta table. It evaluates a specified matching condition and can execute different actions depending on the result. Matching records can be updated, unmatched records can be inserted, and appropriate conditions can also support deletes. This makes MERGE useful for change data capture, incremental processing, and maintaining current-state datasets. VACUUM removes obsolete files, OPTIMIZE reorganizes physical data files, and DESCRIBE provides metadata information. Therefore, MERGE is the appropriate Delta Lake operation when a pipeline needs to apply multiple conditional changes to a target table based on source data.<\/span><\/p>\n<h3><b>Question 163<\/b><\/h3>\n<p><b>Which Unity Catalog object is used to provide governed access to files stored in cloud storage?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Table<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Volume<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">View<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Materialized view<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A volume provides governed access to files through Unity Catalog. It is useful for non-tabular data such as CSV files, JSON documents, images, machine-learning artifacts, and other file-based content. Volumes allow organizations to apply centralized permissions and governance to files while keeping those assets within the Databricks data-management framework. A table represents structured tabular data, a view stores reusable query logic, and a materialized view maintains query-derived results. Therefore, a volume is the appropriate Unity Catalog object when users need controlled access to files rather than only relational table data.<\/span><\/p>\n<h3><b>Question 164<\/b><\/h3>\n<p><b>Which Structured Streaming feature helps recover a query&#8217;s progress after a failure?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Watermark<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Schema evolution<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Checkpoint<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Partition pruning<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A checkpoint stores progress and state information associated with a Structured Streaming query. If the streaming workload stops because of a failure or is restarted, the checkpoint allows processing to resume using the previously recorded state rather than starting from the beginning. This is especially important for reliable streaming pipelines that use stateful transformations or require consistent incremental processing. Watermarks manage late-arriving events and state retention, schema evolution handles changes in data structure, and partition pruning is a query-performance optimization. Therefore, checkpointing is the feature specifically intended to preserve streaming progress and support recovery after interruptions.<\/span><\/p>\n<h3><b>Question 165<\/b><\/h3>\n<p><b>Which architecture pattern uses Bronze, Silver, and Gold layers for progressive data refinement?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Medallion architecture<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Star schema<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Client-server architecture<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Hub-and-spoke architecture<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The medallion architecture organizes data into progressively refined layers, typically called Bronze, Silver, and Gold. Bronze commonly contains raw or minimally processed source data. Silver applies cleaning, validation, standardization, and deduplication to create reliable datasets. Gold contains curated and business-ready data intended for analytics, reporting, and downstream consumption. This layered approach helps separate ingestion from transformation and business use while improving maintainability and traceability. A star schema is a dimensional modeling pattern, while client-server and hub-and-spoke describe different architectural concepts. Therefore, the medallion architecture is the appropriate pattern for progressively refining raw data into trusted analytical datasets.<\/span><\/p>\n<h3><b>Question 166<\/b><\/h3>\n<p><b>Which Unity Catalog privilege is used to access a schema namespace?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SELECT<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">MODIFY<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">CREATE TABLE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">USE SCHEMA<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 4<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">USE SCHEMA provides access to a schema namespace in Unity Catalog. A user generally needs this privilege in addition to the appropriate catalog-level access and privileges on the specific object being accessed. SELECT provides permission to read data, MODIFY allows supported data changes, and CREATE TABLE allows table creation when the necessary permissions are available. Unity Catalog uses hierarchical access controls, meaning permissions at different levels work together rather than independently. Therefore, when the requirement is specifically to access a schema namespace so that its contained objects can be used, USE SCHEMA is the relevant privilege.<\/span><\/p>\n<h3><b>Question 167<\/b><\/h3>\n<p><b>Which feature allows sensitive values in a column to be transformed or hidden for users without sufficient access?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Partition pruning<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Column masking<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Auto Loader<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">File compaction<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Column masking provides fine-grained protection for sensitive values stored in columns. A masking policy can return the original value to authorized users while returning a transformed or obscured value to users who should not have direct access to the sensitive information. This approach allows organizations to maintain a shared dataset while applying different visibility rules based on authorization. Partition pruning and file compaction are primarily performance-related techniques, while Auto Loader handles incremental file ingestion. Therefore, column masking is the appropriate feature when the requirement is to protect sensitive column values without necessarily removing the underlying records from the table.<\/span><\/p>\n<h3><b>Question 168<\/b><\/h3>\n<p><b>Which operation can reduce the number of small files in a Delta table by reorganizing its physical data layout?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">MERGE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">VACUUM<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">OPTIMIZE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GRANT<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">OPTIMIZE improves the physical organization of Delta table data and can compact many small files into fewer, larger files. Small-file accumulation is common in workloads that perform frequent incremental writes or many small streaming batches. Excessive numbers of small files can increase file-management overhead and negatively affect query performance. OPTIMIZE addresses this physical layout problem while preserving the logical contents of the table. MERGE changes records, VACUUM removes obsolete files, and GRANT manages permissions. Therefore, OPTIMIZE is the appropriate operation when the primary goal is to compact small files and improve the physical organization of a Delta table.<\/span><\/p>\n<h3><b>Question 169<\/b><\/h3>\n<p><b>Which feature is designed to detect and incrementally process new files arriving in cloud storage?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Auto Loader<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Time travel<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Cluster policy<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Materialized view<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Auto Loader provides scalable incremental file ingestion from cloud storage. It tracks discovered files and processes newly arriving files without requiring the pipeline to repeatedly process the entire directory. This makes Auto Loader particularly useful for continuously growing file-based sources and large-scale ingestion workloads. It can also integrate with Structured Streaming and provide supported schema inference and schema evolution capabilities. Time travel provides access to historical Delta table versions, cluster policies govern compute configuration, and materialized views maintain query-derived results. Therefore, Auto Loader is the appropriate feature when a data engineering pipeline needs to discover and process new files as they arrive.<\/span><\/p>\n<h3><b>Question 170<\/b><\/h3>\n<p><b>Which Delta Lake feature allows users to query historical versions of a table?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Schema evolution<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Time travel<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Data skipping<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Auto Loader<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Delta Lake time travel allows users to access earlier versions of a table by specifying a historical version or timestamp, subject to the availability of transaction history and required data files. It is useful for auditing, troubleshooting, reproducing historical analyses, and investigating how data changed over time. The Delta transaction log records changes to the table and supports this historical access. Schema evolution handles structural changes, data skipping helps improve query performance, and Auto Loader provides incremental file ingestion. Therefore, time travel is the appropriate Delta Lake capability when a data engineer needs to inspect or query a previous state of a table.<\/span><\/p>\n<h3><b>Question 171<\/b><\/h3>\n<p><b>Which feature helps a streaming workload manage records that arrive after their expected event time?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Watermark<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Catalog<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Volume<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">External location<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A watermark helps Structured Streaming manage late-arriving records by establishing an event-time threshold. It allows the streaming engine to determine how long state should be retained while waiting for delayed events. This is especially useful for stateful operations such as aggregations, joins, and deduplication. Once the watermark progresses sufficiently, older state can eventually be removed according to the semantics of the operation, helping control memory and processing requirements. Catalogs organize data namespaces, volumes provide governed file access, and external locations represent governed cloud storage paths. Therefore, watermarking is the appropriate feature for managing late-arriving events in streaming workloads.<\/span><\/p>\n<h3><b>Question 172<\/b><\/h3>\n<p><b>Which Databricks capability allows multiple tasks to be executed according to defined dependencies and schedules?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Unity Catalog<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Delta Sharing<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Lakeflow Jobs<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">External location<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Lakeflow Jobs provides workflow orchestration capabilities for Databricks workloads. Data engineers can define multiple tasks, establish dependencies, configure schedules or triggers, and specify retry behavior. This allows complex data pipelines to execute automatically in a controlled sequence. For example, an ingestion task can complete before a transformation task begins, followed by validation or reporting tasks. Unity Catalog provides data governance, Delta Sharing enables secure data sharing, and external locations govern cloud storage paths. Therefore, Lakeflow Jobs is the appropriate Databricks capability for orchestrating multiple data engineering tasks and defining how those tasks should execute.<\/span><\/p>\n<h3><b>Question 173<\/b><\/h3>\n<p><b>Which approach is most appropriate for preventing duplicate target records when a pipeline is rerun?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Increase cluster memory<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Use idempotent processing<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Disable Delta transactions<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Remove data-quality checks<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Idempotent processing allows a pipeline to be executed repeatedly without creating unintended duplicate effects. A common design uses stable business keys, deduplication logic, MERGE operations, and appropriate state or checkpoint management. This becomes especially important when a job retries after failure or when source systems may deliver the same records more than once. Increasing cluster memory addresses resource capacity but does not prevent duplicates. Disabling Delta transactions reduces reliability, while removing data-quality checks can allow invalid or duplicated data into downstream datasets. Therefore, idempotent processing is the appropriate design principle for ensuring that rerunning a workload does not unintentionally create duplicate business records.<\/span><\/p>\n<h3><b>Question 174<\/b><\/h3>\n<p><b>Which operation removes obsolete files from a Delta table according to its retention configuration?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">VACUUM<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">MERGE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">OPTIMIZE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SELECT<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">VACUUM removes obsolete data files that are no longer required by a Delta table according to its configured retention rules. It is a storage-maintenance operation that can help reduce unnecessary cloud-storage usage. VACUUM should be used carefully because older files may be required for historical table versions and time-travel queries. MERGE modifies records based on matching conditions, OPTIMIZE reorganizes and compacts files, and SELECT reads data. Therefore, VACUUM is the appropriate operation when a data engineer needs to clean up obsolete Delta files while following the table&#8217;s retention configuration.<\/span><\/p>\n<h3><b>Question 175<\/b><\/h3>\n<p><b>Which Unity Catalog object provides the highest level in the standard catalog-schema-object namespace?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Schema<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Table<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Catalog<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Volume<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A catalog is the highest level in the standard Unity Catalog namespace hierarchy. The hierarchy generally consists of catalog, schema, and object. A catalog can contain multiple schemas, while schemas can contain tables, views, volumes, and other supported objects. This hierarchy provides organizations with a structured way to organize and govern data assets according to business domains, environments, or organizational boundaries. A schema is a level below the catalog, while tables and volumes are objects contained within schemas. Therefore, the catalog is the appropriate object when referring to the highest level of the Unity Catalog namespace.<\/span><\/p>\n<h3><b>Question 176<\/b><\/h3>\n<p><b>Which Spark operation can explicitly change the number of partitions while redistributing data across the cluster?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">CACHE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">VACUUM<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">REPARTITION<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GRANT<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">REPARTITION redistributes records across Spark partitions and allows the number of partitions to be explicitly specified. Because repartitioning generally involves a shuffle, records may move between executors, which can introduce additional processing and network overhead. It can nevertheless be useful when a workload needs greater parallelism or a different partition distribution for subsequent transformations. CACHE stores computed results for reuse, VACUUM removes obsolete Delta files, and GRANT manages access permissions. Therefore, REPARTITION is the appropriate Spark operation when a data engineer needs to change partition count while redistributing the dataset across the cluster.<\/span><\/p>\n<h3><b>Question 177<\/b><\/h3>\n<p><b>Which capability can apply custom processing logic to each micro-batch produced by a Structured Streaming query?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">foreachBatch<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">OPTIMIZE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SHOW GRANTS<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">USE CATALOG<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 4<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">foreachBatch allows custom processing logic to run for each micro-batch generated by a Structured Streaming query. It is useful when a streaming workload needs to perform operations that are easier to express using batch-oriented APIs. For example, a pipeline can use foreachBatch to execute custom transformations or apply a Delta MERGE for each micro-batch. OPTIMIZE manages Delta table file organization, SHOW GRANTS displays Unity Catalog permissions, and USE CATALOG changes the active catalog namespace. Therefore, foreachBatch is the appropriate feature when custom processing needs to be applied independently to every micro-batch of a streaming workload.<\/span><\/p>\n<h3><b>Question 178<\/b><\/h3>\n<p><b>Which feature helps administrators control allowed compute configurations for users in Azure Databricks?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Auto Loader<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Cluster policy<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Time travel<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Materialized view<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Cluster policies allow administrators to define and restrict configuration settings for Databricks compute resources. Policies can control supported settings such as runtime versions, node types, autoscaling limits, and other compute parameters. This helps organizations standardize resource configurations and enforce operational or governance requirements. Auto Loader is used for incremental file ingestion, time travel provides historical Delta table access, and materialized views maintain query-derived results. Cluster policies therefore address compute governance rather than data ingestion or query storage. They are useful when administrators need to prevent unsuitable configurations and provide users with controlled options for creating Databricks compute resources.<\/span><\/p>\n<h3><b>Question 179<\/b><\/h3>\n<p><b>Which Unity Catalog capability can be used to inspect privileges assigned to a securable object?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">MERGE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SHOW GRANTS<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">OPTIMIZE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">VACUUM<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">SHOW GRANTS provides information about privileges assigned to supported Unity Catalog securable objects. Data engineers and administrators can use it to inspect which users, groups, or service principals have been granted particular permissions. This is useful for troubleshooting authorization issues, verifying governance configurations, and reviewing access assignments. MERGE modifies Delta table records, OPTIMIZE reorganizes Delta data files, and VACUUM removes obsolete files. Therefore, SHOW GRANTS is the appropriate capability when the requirement is to inspect existing permissions on a Unity Catalog object and understand which principals have access.<\/span><\/p>\n<h3><b>Question 180<\/b><\/h3>\n<p><b>Which technique allows a query engine to skip unnecessary partitions when filtering on a partitioning column?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Column masking<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Schema evolution<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Partition pruning<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Time travel<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Partition pruning allows the query engine to avoid scanning partitions that cannot contain records matching the query filter. For example, if a Delta table is partitioned by date and a query filters for a specific date, unrelated date partitions can potentially be skipped. This reduces the amount of data read and processed, which can improve query performance and reduce unnecessary I\/O. Column masking controls sensitive values, schema evolution handles changes to data structures, and time travel provides access to historical table versions. Therefore, partition pruning is the appropriate optimization technique when query filters align with the table&#8217;s partitioning strategy.<\/span><\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>View Full Microsoft DP-750 Exam Dumps and Practice Test Dumps. &nbsp; Question 161 Which Azure Databricks capability provides a centralized governance model for catalogs, schemas, tables, views, and volumes? Unity Catalog Spark UI Git folders Cluster logs Correct Answer: 1 Explanation Unity Catalog provides centralized governance and access control for data assets across Azure Databricks. [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1648,1647],"tags":[],"_links":{"self":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/18502"}],"collection":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/comments?post=18502"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/18502\/revisions"}],"predecessor-version":[{"id":18503,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/18502\/revisions\/18503"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=18502"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=18502"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=18502"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}