{"id":13801,"date":"2026-09-16T11:02:40","date_gmt":"2026-09-16T11:02:40","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=13801"},"modified":"2026-09-16T11:02:40","modified_gmt":"2026-09-16T11:02:40","slug":"microsoft-dp-700-practice-test-questions-and-exam-dumps-part13-q241-260","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/microsoft-dp-700-practice-test-questions-and-exam-dumps-part13-q241-260\/","title":{"rendered":"Microsoft DP-700 Practice Test Questions and Exam Dumps Part13 Q241-260"},"content":{"rendered":"<h1><\/h1>\n<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<p>&nbsp;<\/p>\n<h3><b>Question 241<\/b><\/h3>\n<p><b>Which Fabric feature provides a centralized view for monitoring data-related jobs and activities?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Semantic model<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Monitoring hub<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">OneLake shortcut<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Dataflow<\/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 Monitoring hub provides a centralized location for reviewing supported Fabric activities and their execution status. Data engineers can use it to identify successful, running, or failed operations and investigate execution details. This is useful when managing production data workloads because problems can occur after a pipeline or notebook has been deployed. Monitoring helps engineers detect issues quickly and understand where processing stopped. It also supports operational troubleshooting by providing information that can be used to investigate failures and recurring execution problems.<\/span><\/p>\n<h3><b>Question 242<\/b><\/h3>\n<p><b>Which SQL command adds new rows to a table?<\/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;\">UPDATE<\/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;\">ALTER<\/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 INSERT statement adds new rows to an existing table. It can be used to add individual records or multiple records depending on the statement and supported syntax. In data engineering, INSERT can be used during loading processes when new records need to be added to a target table. Engineers should ensure that inserted data follows the target schema and does not create unintended duplicates. When loading data incrementally, appropriate keys, deduplication rules, or change-detection mechanisms may be required to maintain data quality.<\/span><\/p>\n<h3><b>Question 243<\/b><\/h3>\n<p><b>Which Fabric workload is most appropriate for complex transformations using PySpark?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Warehouse<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Semantic model<\/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;\">Deployment pipeline<\/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 Fabric notebook is appropriate for complex data transformations using PySpark and Spark-based processing. Notebooks allow engineers to write custom code for cleansing, joining, aggregating, and restructuring large datasets. Spark provides distributed processing capabilities, making notebooks suitable for workloads that may be difficult to implement using only graphical transformations. Engineers can also combine multiple processing steps within a notebook and integrate notebook execution into broader pipeline workflows. This flexibility makes notebooks useful when data engineering requirements go beyond straightforward low-code transformations.<\/span><\/p>\n<h3><b>Question 244<\/b><\/h3>\n<p><b>Which activity can retrieve configuration records from a source before a pipeline begins processing them?<\/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: 4<\/b><\/p>\n<p><b>Explanation<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The Lookup activity retrieves records or values from a supported data source and makes them available for subsequent pipeline processing. It is commonly used to retrieve configuration information, metadata, table names, file paths, or processing rules. The returned values can then be used by activities such as ForEach or conditional logic. This supports reusable and metadata-driven pipeline designs. Instead of hard-coding every source or destination, engineers can store configuration externally and allow the pipeline to determine its processing behavior at runtime.<\/span><\/p>\n<h3><b>Question 245<\/b><\/h3>\n<p><b>Which storage format is commonly used as the underlying format for Delta tables?<\/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;\">XML<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">JSON<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Parquet<\/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;\">Parquet is the underlying file format commonly used by Delta tables. It is a columnar format that provides efficient storage and analytical query performance. Delta Lake adds a transaction log and additional management capabilities on top of the Parquet files, supporting features such as ACID transactions and reliable table operations. This combination is widely used in Lakehouse architectures. The columnar structure also allows analytical engines to read only the required columns, which can reduce unnecessary data access during queries.<\/span><\/p>\n<h3><b>Question 246<\/b><\/h3>\n<p><b>Which approach is best suited to preserving previous versions of changing customer attributes?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Full reload<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Slowly Changing Dimension Type 2<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">File compaction<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Data profiling<\/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;\">Slowly Changing Dimension Type 2 preserves historical versions of dimension records when their attributes change. Instead of replacing the previous record, a new version is added while the old version remains available. Additional information such as effective dates or current-record indicators can identify which version was valid at a specific time. This is useful for customers, products, employees, and other entities whose attributes can change over time. SCD Type 2 allows historical reports to use the appropriate version of the dimension rather than only the current value.<\/span><\/p>\n<h3><b>Question 247<\/b><\/h3>\n<p><b>Which capability allows a Lakehouse to reference existing data without creating another physical copy?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">OneLake shortcut<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Warehouse view<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Semantic model<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Spark session<\/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 OneLake shortcut allows a Fabric Lakehouse to reference data stored in another supported location without physically copying the underlying data. This can reduce duplication and make shared datasets easier to access across workloads. Shortcuts are useful when organizations want to maintain data in an existing location while exposing it through Fabric. They can also simplify data architecture by reducing the need for repeated ingestion solely to make information available to another team or analytical workload. Appropriate permissions and supported source types should still be considered.<\/span><\/p>\n<h3><b>Question 248<\/b><\/h3>\n<p><b>Which SQL clause is used to group rows for aggregate calculations?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">WHERE<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">ORDER BY<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GROUP BY<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">HAVING<\/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;\">GROUP BY organizes rows into groups based on one or more columns and is commonly used with aggregate functions. For example, a sales table can be grouped by product category and then processed with SUM() to calculate total sales for each category. GROUP BY differs from ORDER BY, which sorts results, and WHERE, which filters individual rows before grouping. HAVING can then be used to filter the resulting groups. Understanding the sequence of these clauses is important for writing accurate analytical SQL queries.<\/span><\/p>\n<h3><b>Question 249<\/b><\/h3>\n<p><b>A pipeline needs to execute the same processing logic for every file returned by a metadata query. Which activity should be used?<\/b><\/p>\n<ol>\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;\">Delete<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">If Condition<\/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 ForEach activity is designed to repeat a set of pipeline actions for every item in a collection. In this scenario, a metadata query can return a list of file paths, and ForEach can process each file using the same sequence of activities. This avoids creating separate pipeline branches for every file. It is especially useful in metadata-driven architectures where files may be added or removed over time. Combining Lookup and ForEach creates a flexible pattern for dynamically processing collections of data objects.<\/span><\/p>\n<h3><b>Question 250<\/b><\/h3>\n<p><b>Which practice can reduce the number of small files generated during repeated data writes?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">File compaction<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Increasing duplicates<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Removing partitions<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Converting data to XML<\/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;\">File compaction combines multiple small files into fewer, larger files. Repeated small writes can create many tiny files, increasing metadata overhead and making data processing less efficient. Compaction can improve performance by reducing the number of files that processing engines must open and manage. It is particularly useful in Lakehouse environments where frequent ingestion or transformation operations may produce many small output files. Maintaining appropriate file sizes can improve read performance and reduce unnecessary overhead during analytical processing.<\/span><\/p>\n<h3><b>Question 251<\/b><\/h3>\n<p><b>Which Fabric capability is designed for low-code data transformation?<\/b><\/p>\n<ol>\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;\">Eventstream<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Warehouse<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Git integration<\/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;\">Dataflow Gen2 provides a low-code approach to data ingestion and transformation using a graphical interface. It is useful for common operations such as filtering, changing data types, merging datasets, removing duplicates, and reshaping data. Because it uses a visual transformation experience, it can reduce the amount of custom code required for routine preparation tasks. Dataflow Gen2 is particularly useful when transformations are well suited to Power Query-based operations. More complex processing can instead be implemented with notebooks and Spark.<\/span><\/p>\n<h3><b>Question 252<\/b><\/h3>\n<p><b>Which pipeline feature allows different behavior based on whether an expression evaluates to true or false?<\/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;\">Copy Data<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">If Condition<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Wait<\/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;\">The If Condition activity provides conditional branching in a pipeline. It evaluates an expression and directs execution to the appropriate branch based on whether the result is true or false. This allows pipelines to make runtime decisions instead of following exactly the same sequence every time. For example, a pipeline can check whether new data exists and perform processing only when the condition is satisfied. Conditional activities are useful for creating dynamic workflows and reducing unnecessary processing when certain conditions are not met.<\/span><\/p>\n<h3><b>Question 253<\/b><\/h3>\n<p><b>Which SQL function returns the smallest value in a column?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">SUM()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">MIN()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">AVG()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">MAX()<\/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 MIN() function returns the smallest value from a compatible column or expression. It can be used with numeric values, dates, and other supported data types. For example, MIN() can identify the earliest transaction date or the lowest recorded sales amount. When combined with GROUP BY, it can calculate minimum values separately for different categories. Data engineers should consider filtering conditions and NULL values when interpreting results. Correct query design ensures that the returned minimum value represents the intended set of records.<\/span><\/p>\n<h3><b>Question 254<\/b><\/h3>\n<p><b>Which approach helps a pipeline use different source tables without creating a separate pipeline for each table?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Hard-coded paths<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Manual execution<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Parameterization<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Duplicate workflows<\/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;\">Parameterization allows a reusable pipeline to receive values at runtime, such as source table names, file paths, dates, or processing modes. Instead of creating a separate pipeline for every source table, an engineer can build one workflow and pass the appropriate table name as a parameter. This reduces duplicated logic and simplifies maintenance. Parameterized pipelines are particularly useful in metadata-driven architectures, where configuration determines which objects should be processed. They also make it easier to reuse the same workflow across different environments and datasets.<\/span><\/p>\n<h3><b>Question 255<\/b><\/h3>\n<p><b>Which feature can identify relationships between upstream and downstream data assets?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Data lineage<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">File compression<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Data type conversion<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Notebook scheduling<\/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;\">Data lineage shows relationships between data sources and downstream assets, helping users understand how information flows through the analytical environment. It can be useful for impact analysis when a table or other data item is changed. For example, an engineer can investigate which downstream assets depend on a particular dataset before modifying it. Lineage is also valuable for troubleshooting because it provides context around how data moves through different stages. This helps teams better understand dependencies across their Fabric environment.<\/span><\/p>\n<h3><b>Question 256<\/b><\/h3>\n<p><b>Which statement is used to modify existing records in a table?<\/b><\/p>\n<ol>\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;\">INSERT<\/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;\">SELECT<\/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;\">UPDATE modifies values in existing rows of a table. It is commonly used when source information changes and those changes need to be reflected in the target dataset. A WHERE clause can restrict the operation to specific records. For example, an engineer might update the status of selected customer records based on new source information. UPDATE differs from INSERT, which adds rows, and DELETE, which removes them. Careful filtering is important because an incorrectly written UPDATE statement can modify more records than intended.<\/span><\/p>\n<h3><b>Question 257<\/b><\/h3>\n<p><b>Which architecture organizes data into raw, cleaned, and curated stages?<\/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;\">Flat-file architecture<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Single-table architecture<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Report architecture<\/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;\">Medallion architecture organizes data into multiple processing layers, commonly called Bronze, Silver, and Gold. Bronze generally contains raw data, Silver contains cleaned and transformed information, and Gold contains curated datasets designed for analytical consumption. This separation helps data engineers manage different processing stages and establish clear responsibilities for each layer. It can also make troubleshooting easier because engineers can inspect intermediate results. The architecture is commonly used in Lakehouse-based solutions where raw ingestion and business-ready analytical data need to be managed separately.<\/span><\/p>\n<h3><b>Question 258<\/b><\/h3>\n<p><b>Which method can detect new and changed source records without reprocessing the entire dataset?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Full reload<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Change data capture<\/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;\">File renaming<\/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;\">Change data capture, or CDC, identifies changes made to source data so downstream systems can process only the affected records. Depending on the source system, CDC may capture inserts, updates, and deletes. This supports incremental processing and can significantly reduce the amount of data transferred and transformed during recurring loads. CDC is especially useful for large operational databases where a full reload would be inefficient. The data engineering process must still apply captured changes correctly to the target and maintain appropriate processing checkpoints.<\/span><\/p>\n<h3><b>Question 259<\/b><\/h3>\n<p><b>Which SQL clause sorts query results in ascending or descending order?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">GROUP BY<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">HAVING<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">ORDER BY<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">WHERE<\/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;\">ORDER BY controls the sorting of rows returned by a SQL query. It can sort one or more columns in ascending or descending order. For example, a data engineer can use ORDER BY to display transactions from newest to oldest or products from highest to lowest sales. ORDER BY does not filter rows or calculate aggregates; its purpose is to determine the order of the returned results. When sorting large result sets, engineers should consider whether ordering is actually required because sorting can add processing overhead.<\/span><\/p>\n<h3><b>Question 260<\/b><\/h3>\n<p><b>Which security principle recommends granting users only the permissions they need?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Least privilege<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Full access<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Shared credentials<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Anonymous access<\/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 principle of least privilege means users and services should receive only the permissions necessary to perform their assigned responsibilities. This reduces the potential impact of accidental changes, misuse, or compromised accounts. In Microsoft Fabric, least privilege can be applied through appropriate workspace roles, item permissions, and other supported security controls. For example, a user who only needs to view analytical content may not require permissions to modify or administer the workspace. Regularly reviewing permissions helps ensure access remains appropriate as responsibilities change.<\/span><\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>View Full Microsoft DP-700 Exam Dumps and Practice Test Dumps. &nbsp; Question 241 Which Fabric feature provides a centralized view for monitoring data-related jobs and activities? Semantic model Monitoring hub OneLake shortcut Dataflow Correct Answer: 2 Explanation The Monitoring hub provides a centralized location for reviewing supported Fabric activities and their execution status. Data engineers [&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\/13801"}],"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=13801"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/13801\/revisions"}],"predecessor-version":[{"id":13814,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/13801\/revisions\/13814"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=13801"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=13801"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=13801"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}