{"id":13828,"date":"2026-09-16T11:11:46","date_gmt":"2026-09-16T11:11:46","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=13828"},"modified":"2026-09-16T11:11:46","modified_gmt":"2026-09-16T11:11:46","slug":"microsoft-dp-700-practice-test-questions-and-exam-dumps-part14-q261-280","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/microsoft-dp-700-practice-test-questions-and-exam-dumps-part14-q261-280\/","title":{"rendered":"Microsoft DP-700 Practice Test Questions and Exam Dumps Part14 Q261-280"},"content":{"rendered":"<h2><b>View Full <\/b><a href=\"https:\/\/www.examlabs.com\/dp-700-exam-dumps\"><b>Microsoft DP-700 Exam Dumps<\/b><\/a><b> and Practice Test Dumps.<\/b><\/h2>\n<h3><b>Question 261<\/b><\/h3>\n<p><b>Which Fabric capability allows developers to track changes to notebooks and other supported items over time?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Eventstream<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Git integration<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Dataflow Gen2<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Monitoring hub<\/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;\">Git integration provides source control capabilities for supported Fabric items. It allows developers to track changes, collaborate on development work, and maintain different versions of their project assets. This is useful when multiple engineers work on the same data solution because changes can be reviewed and managed systematically. Git-based workflows can also support development and deployment processes by allowing teams to work with branches and synchronize changes. Proper source control helps reduce accidental overwrites and provides a history of modifications made during development.<\/span><\/p>\n<h3><b>Question 262<\/b><\/h3>\n<p><b>Which operation removes all rows from a table while keeping the table structure?<\/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;\">UPDATE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">TRUNCATE TABLE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">ALTER TABLE<\/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;\">TRUNCATE TABLE removes all rows from a table while retaining the table definition and structure. It is useful when a table needs to be emptied before a complete reload. Unlike DELETE, which can remove selected rows using a WHERE clause, TRUNCATE is intended to remove the table&#8217;s rows as a whole. Data engineers should use it carefully because it can remove the entire current dataset. The appropriate behavior and permissions can also vary depending on the specific Fabric workload and table implementation.<\/span><\/p>\n<h3><b>Question 263<\/b><\/h3>\n<p><b>What is the main purpose of a surrogate key in a dimension table?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Provide a system-generated identifier<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Store descriptive text<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Calculate aggregates<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Partition files<\/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 surrogate key is a generated identifier used to uniquely identify records in a dimension table. It is generally independent of the source system&#8217;s natural business key. Surrogate keys are particularly useful in dimensional models because they can support multiple historical versions of the same business entity. For example, when a customer&#8217;s attributes change under an SCD Type 2 design, a new surrogate key can identify the new version. This approach separates analytical relationships from source-system identifiers and provides greater flexibility for historical data management.<\/span><\/p>\n<h3><b>Question 264<\/b><\/h3>\n<p><b>Which pipeline activity pauses execution for a specified period?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Lookup<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Wait<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">ForEach<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Copy Data<\/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;\">The Wait activity pauses pipeline execution for a specified amount of time before continuing to the next step. It can be useful when a workflow must allow time for an external process, resource, or system condition to become ready. For example, a pipeline may wait before checking whether a downstream file has arrived. Wait does not itself retrieve or transform data. It is primarily a workflow-control feature and can be combined with other activities to create more controlled orchestration patterns when timing requirements exist.<\/span><\/p>\n<h3><b>Question 265<\/b><\/h3>\n<p><b>Which optimization reduces the amount of data scanned by filtering on partition columns?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Data duplication<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Row insertion<\/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;\">Schema expansion<\/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 a query engine to skip partitions that cannot contain the requested data. When a query filters on a column used for partitioning, the engine can limit its work to relevant partitions instead of scanning the entire dataset. This can improve query performance and reduce unnecessary data access. Effective partitioning depends on choosing useful partition columns and avoiding excessive numbers of partitions. Data engineers should consider common query patterns when designing partitions so that filters can take advantage of partition elimination.<\/span><\/p>\n<h3><b>Question 266<\/b><\/h3>\n<p><b>Which feature is commonly used to process real-time event data in Microsoft Fabric?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Eventstream<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Lookup<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">CTAS<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Stored procedure<\/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;\">Eventstream is designed to ingest and process streaming event data in Microsoft Fabric. It can connect to supported event sources and route or transform streaming information for downstream consumption. This makes it useful for scenarios such as monitoring operational events, application activity, sensor information, or other continuously arriving data. Unlike traditional batch pipelines, streaming workloads process events as they arrive or with minimal delay. Engineers can combine Eventstream with other Fabric capabilities to build solutions that capture and analyze real-time information.<\/span><\/p>\n<h3><b>Question 267<\/b><\/h3>\n<p><b>A pipeline should continue only after another activity completes successfully. Which dependency condition should be used?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">On success<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">On failure<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">On completion<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">On skipped<\/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 On success dependency condition allows a downstream pipeline activity to run only when the preceding activity finishes successfully. This is useful when later processing depends on the successful completion of an earlier step. For example, a transformation activity can be configured to execute only after a Copy Data activity successfully loads the required source data. Dependency conditions help engineers control workflow execution and prevent dependent activities from running when prerequisites have failed. Other conditions can be used when workflows need to respond to failures or completion regardless of outcome.<\/span><\/p>\n<h3><b>Question 268<\/b><\/h3>\n<p><b>Which command creates a new table from the results of a query?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">INSERT<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">CTAS<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DELETE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">UPDATE<\/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;\">CTAS, or CREATE TABLE AS SELECT, creates a new table using the result of a SELECT query. It is useful when engineers need to create a table from transformed, filtered, or aggregated data. For example, a curated table can be created from a source dataset by selecting only required columns and applying transformations. CTAS can simplify table creation because the query defines the resulting data set. Engineers should still consider the target schema, data types, storage characteristics, and workload requirements when using this approach.<\/span><\/p>\n<h3><b>Question 269<\/b><\/h3>\n<p><b>What does data profiling primarily help engineers identify?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Pipeline schedules<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Workspace roles<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Data quality characteristics<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Git branches<\/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;\">Data profiling examines a dataset to understand its quality and characteristics. It can reveal issues such as missing values, unexpected data types, duplicate records, unusual distributions, and inconsistent values. Profiling is often performed before or during data transformation so engineers can identify problems before they reach downstream analytical datasets. It can also help determine appropriate cleansing and validation rules. By understanding the actual structure and quality of incoming data, engineers can design transformations that better match the requirements of the target data model.<\/span><\/p>\n<h3><b>Question 270<\/b><\/h3>\n<p><b>Which Fabric component is primarily designed for storing structured analytical data using SQL?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Eventstream<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Notebook<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Dataflow Gen2<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Warehouse<\/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;\">A Fabric Warehouse is designed for structured analytical data and provides a SQL-based environment for querying and managing data. It is particularly suitable for relational workloads, dimensional models, and analytical queries that use T-SQL. Data engineers can create tables, views, and other supported database objects and use SQL to transform or analyze information. A Warehouse differs from a Lakehouse because the Warehouse emphasizes a relational SQL experience, while a Lakehouse provides both file-based storage and analytical access through multiple processing approaches.<\/span><\/p>\n<h3><b>Question 271<\/b><\/h3>\n<p><b>Which concept defines the level of detail represented by each row in a fact table?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Table schema<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Grain<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">File format<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Data type<\/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;\">The grain of a fact table defines exactly what one row represents. For example, a sales fact table might have a grain of one row per product per transaction, while another could represent one row per daily product summary. Defining grain clearly is essential because it determines how measures should be stored and aggregated. An unclear grain can lead to duplicated values or incorrect analytical results. Before designing a fact table, data engineers should identify the business event and determine the precise level of detail required.<\/span><\/p>\n<h3><b>Question 272<\/b><\/h3>\n<p><b>Which object can provide a reusable SQL query without storing a separate copy of the underlying data?<\/b><\/p>\n<ol>\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;\">File<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Shortcut<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Partition<\/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 view is a virtual representation of a query that can be used as a reusable SQL object. Instead of storing another physical copy of the query results, a view generally stores the query definition and retrieves data according to that definition. Views can simplify access to complex queries, expose selected columns, and provide a consistent interface for downstream users. They can also help separate users from underlying table structures. Engineers should still consider query performance and supported capabilities when designing views for frequently used workloads.<\/span><\/p>\n<h3><b>Question 273<\/b><\/h3>\n<p><b>Which approach is most appropriate for handling records that fail data-quality validation?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Ignore all records<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Delete the source<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Quarantine invalid records<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Disable validation<\/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;\">Quarantining invalid records separates problematic data from valid data while preserving the failed records for investigation. This approach is preferable to silently discarding data because engineers can review the errors, identify their causes, and potentially correct and reprocess the records later. A quarantine area may contain information about the validation failure, processing time, or source record. This pattern is useful in production pipelines where data quality issues must be managed without stopping every valid record from progressing through the workflow.<\/span><\/p>\n<h3><b>Question 274<\/b><\/h3>\n<p><b>Which feature can expose pipeline values dynamically at runtime?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Static SQL<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Dynamic content<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Fixed schema<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Manual execution<\/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;\">Dynamic content allows pipeline expressions and activity values to be evaluated during execution rather than being fixed in advance. It can be used with parameters, variables, activity outputs, and other runtime information. For example, a pipeline can dynamically construct a file path based on a processing date or use a value returned by a Lookup activity. This makes workflows more reusable and adaptable. Dynamic content is especially valuable in metadata-driven pipelines where runtime values determine which files, tables, or processing steps should be used.<\/span><\/p>\n<h3><b>Question 275<\/b><\/h3>\n<p><b>Which design helps prevent duplicate records when the same batch is processed more than once?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Idempotent processing<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Random partitioning<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Manual sorting<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Full duplication<\/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;\">Idempotent processing is designed so that processing the same input more than once does not create unintended duplicate results. This is important in data pipelines because retries, failures, or reruns can cause the same batch to be submitted multiple times. Techniques such as merge operations, unique business keys, checkpoints, and controlled overwrite strategies can help achieve idempotent behavior. Designing pipelines this way improves reliability because an operational retry can recover from a failure without corrupting the target dataset or creating duplicate business records.<\/span><\/p>\n<h3><b>Question 276<\/b><\/h3>\n<p><b>Which operation combines matching records from two datasets based on a related condition?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">JOIN<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DROP<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SORT<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">TRUNCATE<\/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 JOIN combines rows from two or more datasets using a related condition, commonly based on matching key columns. Joins are fundamental to data engineering because information is frequently distributed across separate fact, dimension, and operational tables. Different join types determine which records are retained when matches are missing. For example, an inner join returns matching records, while a left join preserves rows from the left dataset. Engineers should choose the appropriate join type and verify key uniqueness to avoid unintended row multiplication.<\/span><\/p>\n<h3><b>Question 277<\/b><\/h3>\n<p><b>Which capability can promote Fabric items between development and production environments?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Data profiling<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Deployment pipelines<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Eventstream<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">OneLake shortcut<\/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;\">Deployment pipelines help organize the promotion of supported Fabric content between development, test, and production stages. This supports a more controlled release process than manually recreating items in each environment. Teams can develop and validate changes before promoting them to a production stage. Deployment workflows can also reduce configuration mistakes and improve consistency between environments. Engineers should still review environment-specific settings, connections, parameters, and dependencies because not every configuration value should necessarily remain identical across development and production.<\/span><\/p>\n<h3><b>Question 278<\/b><\/h3>\n<p><b>Which method can make a pipeline process multiple tables using metadata rather than hard-coded activities?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Metadata-driven design<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Manual copying<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Static scheduling<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Duplicate pipelines<\/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 metadata-driven design stores information about sources, destinations, processing rules, or other configuration separately from the pipeline logic. The pipeline reads this metadata and dynamically determines which objects to process. For example, one reusable pipeline can use a configuration table containing source and destination table names instead of having separate activities for every table. This approach reduces duplication and simplifies maintenance. It is especially useful when the number of tables changes frequently because new processing targets can often be added through configuration rather than redesigning the pipeline.<\/span><\/p>\n<h3><b>Question 279<\/b><\/h3>\n<p><b>Which storage format is column-oriented and commonly used for analytical workloads in a Lakehouse?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">CSV<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">TXT<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Parquet<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">XML<\/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;\">Parquet is a column-oriented storage format commonly used for analytical workloads in Lakehouse environments. Because data is organized by columns, analytical engines can often read only the columns required by a query instead of scanning every field. Parquet also supports efficient compression and encoding techniques, helping reduce storage and data movement requirements. Fabric Lakehouse tables commonly use Parquet-based storage together with Delta Lake capabilities. Choosing an appropriate file format is an important part of designing efficient analytical data storage and processing workflows.<\/span><\/p>\n<h3><b>Question 280<\/b><\/h3>\n<p><b>What should an engineer use to investigate why a pipeline activity failed?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Run history and error details<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Table grain<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Surrogate key<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">File format<\/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;\">Pipeline run history and error details provide information needed to investigate failed activities. Engineers can review the execution status, identify the activity that failed, and inspect available error messages or related execution information. This helps determine whether the problem came from a source connection, invalid configuration, transformation issue, authentication failure, or another cause. Reviewing the actual execution details is more reliable than guessing from the pipeline design alone. After identifying the cause, engineers can correct the configuration or logic and rerun the affected workflow.<\/span><\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>View Full Microsoft DP-700 Exam Dumps and Practice Test Dumps. Question 261 Which Fabric capability allows developers to track changes to notebooks and other supported items over time? Eventstream Git integration Dataflow Gen2 Monitoring hub Correct Answer: 2 Explanation Git integration provides source control capabilities for supported Fabric items. It allows developers to track changes, [&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\/13828"}],"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=13828"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/13828\/revisions"}],"predecessor-version":[{"id":13829,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/13828\/revisions\/13829"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=13828"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=13828"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=13828"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}