Microsoft Fabric Data Engineer DP-700 Notebook, Spark And T-SQL Troubleshooting Practice Test

 

Topic 12 covers notebook, spark and t-sql troubleshooting for Microsoft DP-700 practice. Study each scenario and select the best answer. For broader exam preparation, review the Microsoft DP-700 Exam Dumps page.

Question 1

After a recent change in an IoT operations solution, the team determines that the notebook fails with a missing package that is already approved in a Fabric environment. Which implementation should be selected?

  1. Attach the notebook to the environment that contains the required library
  2. Publish the environment after changing libraries
  3. Use a compatible Spark runtime in the attached environment
  4. Remove an incompatible custom package version
  5. Restart the Spark session after a runtime/library change when required

Correct Answer: A

Correct Answer

Answer A is correct because the notebook must run with the environment that provides its dependencies. This directly addresses the relevant Fabric behavior while preserving the other stated constraints.

Incorrect Answers

Answer B is incorrect because this action is appropriate when the library was added to the environment definition but notebook sessions still do not see it. Specifically, environment changes must be published before they become the live configuration, which does not resolve the decisive condition in this scenario.

Answer C is incorrect because this action is appropriate when the notebook code or library requires a runtime version different from the workspace default. Specifically, runtime compatibility is controlled through the environment/workspace Spark configuration, which does not resolve the decisive condition in this scenario.

Answer D is incorrect because this action is appropriate when the session fails only after a newly added package overrides a platform-compatible dependency. Specifically, the conflicting package version should be corrected rather than increasing compute, which does not resolve the decisive condition in this scenario.

Answer E is incorrect because this action is appropriate when the environment is updated but the active session still has the previous process state. Specifically, a fresh session loads the current runtime and library configuration, which does not resolve the decisive condition in this scenario.

Question 2

A Fabric engineering team is reviewing a product usage analytics pipeline. The library was added to the environment definition but notebook sessions still do not see it Which action is most appropriate?

  1. Remove an incompatible custom package version
  2. Restart the Spark session after a runtime/library change when required
  3. Attach the notebook to the environment that contains the required library
  4. Publish the environment after changing libraries
  5. Use a compatible Spark runtime in the attached environment

Correct Answer: D

Correct Answer

Answer D is correct because environment changes must be published before they become the live configuration. This directly addresses the relevant Fabric behavior while preserving the other stated constraints.

Incorrect Answers

Answer A is incorrect because this action is appropriate when the session fails only after a newly added package overrides a platform-compatible dependency. Specifically, the conflicting package version should be corrected rather than increasing compute, which does not resolve the decisive condition in this scenario.

Answer B is incorrect because this action is appropriate when the environment is updated but the active session still has the previous process state. Specifically, a fresh session loads the current runtime and library configuration, which does not resolve the decisive condition in this scenario.

Answer C is incorrect because this action is appropriate when the notebook fails with a missing package that is already approved in a Fabric environment. Specifically, the notebook must run with the environment that provides its dependencies, which does not resolve the decisive condition in this scenario.

Answer E is incorrect because this action is appropriate when the notebook code or library requires a runtime version different from the workspace default. Specifically, runtime compatibility is controlled through the environment/workspace Spark configuration, which does not resolve the decisive condition in this scenario.

Question 3

A data engineer must correct a design for a customer-analytics environment. The decisive requirement is that the notebook code or library requires a runtime version different from the workspace default. Which choice best addresses it?

  1. Publish the environment after changing libraries
  2. Use a compatible Spark runtime in the attached environment
  3. Remove an incompatible custom package version
  4. Restart the Spark session after a runtime/library change when required
  5. Attach the notebook to the environment that contains the required library

Correct Answer: B

Correct Answer

Answer B is correct because runtime compatibility is controlled through the environment/workspace Spark configuration. This directly addresses the relevant Fabric behavior while preserving the other stated constraints.

Incorrect Answers

Answer A is incorrect because this action is appropriate when the library was added to the environment definition but notebook sessions still do not see it. Specifically, environment changes must be published before they become the live configuration, which does not resolve the decisive condition in this scenario.

Answer C is incorrect because this action is appropriate when the session fails only after a newly added package overrides a platform-compatible dependency. Specifically, the conflicting package version should be corrected rather than increasing compute, which does not resolve the decisive condition in this scenario.

Answer D is incorrect because this action is appropriate when the environment is updated but the active session still has the previous process state. Specifically, a fresh session loads the current runtime and library configuration, which does not resolve the decisive condition in this scenario.

Answer E is incorrect because this action is appropriate when the notebook fails with a missing package that is already approved in a Fabric environment. Specifically, the notebook must run with the environment that provides its dependencies, which does not resolve the decisive condition in this scenario.

Question 4

For an internal finance data estate, the organization has fixed the following constraint: the session fails only after a newly added package overrides a platform-compatible dependency. Which action best satisfies the requirement?

  1. Restart the Spark session after a runtime/library change when required
  2. Attach the notebook to the environment that contains the required library
  3. Publish the environment after changing libraries
  4. Use a compatible Spark runtime in the attached environment
  5. Remove an incompatible custom package version

Correct Answer: E

Correct Answer

Answer E is correct because the conflicting package version should be corrected rather than increasing compute. This directly addresses the relevant Fabric behavior while preserving the other stated constraints.

Incorrect Answers

Answer A is incorrect because this action is appropriate when the environment is updated but the active session still has the previous process state. Specifically, a fresh session loads the current runtime and library configuration, which does not resolve the decisive condition in this scenario.

Answer B is incorrect because this action is appropriate when the notebook fails with a missing package that is already approved in a Fabric environment. Specifically, the notebook must run with the environment that provides its dependencies, which does not resolve the decisive condition in this scenario.

Answer C is incorrect because this action is appropriate when the library was added to the environment definition but notebook sessions still do not see it. Specifically, environment changes must be published before they become the live configuration, which does not resolve the decisive condition in this scenario.

Answer D is incorrect because this action is appropriate when the notebook code or library requires a runtime version different from the workspace default. Specifically, runtime compatibility is controlled through the environment/workspace Spark configuration, which does not resolve the decisive condition in this scenario.

Question 5

During an operational design review for a multi-team Fabric deployment, engineers confirm that the environment is updated but the active session still has the previous process state. What should they do?

  1. Use a compatible Spark runtime in the attached environment
  2. Remove an incompatible custom package version
  3. Restart the Spark session after a runtime/library change when required
  4. Attach the notebook to the environment that contains the required library
  5. Publish the environment after changing libraries

Correct Answer: C

Correct Answer

Answer C is correct because a fresh session loads the current runtime and library configuration. This directly addresses the relevant Fabric behavior while preserving the other stated constraints.

Incorrect Answers

Answer A is incorrect because this action is appropriate when the notebook code or library requires a runtime version different from the workspace default. Specifically, runtime compatibility is controlled through the environment/workspace Spark configuration, which does not resolve the decisive condition in this scenario.

Answer B is incorrect because this action is appropriate when the session fails only after a newly added package overrides a platform-compatible dependency. Specifically, the conflicting package version should be corrected rather than increasing compute, which does not resolve the decisive condition in this scenario.

Answer D is incorrect because this action is appropriate when the notebook fails with a missing package that is already approved in a Fabric environment. Specifically, the notebook must run with the environment that provides its dependencies, which does not resolve the decisive condition in this scenario.

Answer E is incorrect because this action is appropriate when the library was added to the environment definition but notebook sessions still do not see it. Specifically, environment changes must be published before they become the live configuration, which does not resolve the decisive condition in this scenario.

Question 6

After a recent change in a real-time telemetry service, the team determines that the driver runs out of memory while planning/collecting metadata and executors remain healthy. Which implementation should be selected?

  1. Increase driver memory when the driver is the failing process
  2. Increase executor memory or reduce partition size when executors spill or fail
  3. Repartition skewed data before the wide transformation
  4. Reduce unnecessary collect() operations to the driver
  5. Right-size the workload instead of using the largest available pool by default

Correct Answer: A

Correct Answer

Answer A is correct because driver sizing targets the actual failing component. This directly addresses the relevant Fabric behavior while preserving the other stated constraints.

Incorrect Answers

Answer B is incorrect because this action is appropriate when worker tasks run out of memory on large partitions while the driver is stable. Specifically, executor-side tuning addresses the task-memory boundary, which does not resolve the decisive condition in this scenario.

Answer C is incorrect because this action is appropriate when one task processes most rows and delays the whole Spark stage. Specifically, better partition distribution reduces the straggler caused by skew, which does not resolve the decisive condition in this scenario.

Answer D is incorrect because this action is appropriate when the notebook brings a large distributed dataset into driver memory and crashes. Specifically, keeping data distributed avoids driver-memory exhaustion, which does not resolve the decisive condition in this scenario.

Answer E is incorrect because this action is appropriate when the notebook is small but oversized compute delays concurrency and wastes capacity. Specifically, resource sizing should match workload needs rather than maximize allocation, which does not resolve the decisive condition in this scenario.

Question 7

A Fabric engineering team is reviewing a global manufacturing data product. Worker tasks run out of memory on large partitions while the driver is stable Which action is most appropriate?

  1. Reduce unnecessary collect() operations to the driver
  2. Right-size the workload instead of using the largest available pool by default
  3. Increase driver memory when the driver is the failing process
  4. Increase executor memory or reduce partition size when executors spill or fail
  5. Repartition skewed data before the wide transformation

Correct Answer: D

Correct Answer

Answer D is correct because executor-side tuning addresses the task-memory boundary. This directly addresses the relevant Fabric behavior while preserving the other stated constraints.

Incorrect Answers

Answer A is incorrect because this action is appropriate when the notebook brings a large distributed dataset into driver memory and crashes. Specifically, keeping data distributed avoids driver-memory exhaustion, which does not resolve the decisive condition in this scenario.

Answer B is incorrect because this action is appropriate when the notebook is small but oversized compute delays concurrency and wastes capacity. Specifically, resource sizing should match workload needs rather than maximize allocation, which does not resolve the decisive condition in this scenario.

Answer C is incorrect because this action is appropriate when the driver runs out of memory while planning/collecting metadata and executors remain healthy. Specifically, driver sizing targets the actual failing component, which does not resolve the decisive condition in this scenario.

Answer E is incorrect because this action is appropriate when one task processes most rows and delays the whole Spark stage. Specifically, better partition distribution reduces the straggler caused by skew, which does not resolve the decisive condition in this scenario.

Question 8

A data engineer must correct a design for a governed self-service analytics domain. The decisive requirement is that one task processes most rows and delays the whole Spark stage. Which choice best addresses it?

  1. Increase executor memory or reduce partition size when executors spill or fail
  2. Repartition skewed data before the wide transformation
  3. Reduce unnecessary collect() operations to the driver
  4. Right-size the workload instead of using the largest available pool by default
  5. Increase driver memory when the driver is the failing process

Correct Answer: B

Correct Answer

Answer B is correct because better partition distribution reduces the straggler caused by skew. This directly addresses the relevant Fabric behavior while preserving the other stated constraints.

Incorrect Answers

Answer A is incorrect because this action is appropriate when worker tasks run out of memory on large partitions while the driver is stable. Specifically, executor-side tuning addresses the task-memory boundary, which does not resolve the decisive condition in this scenario.

Answer C is incorrect because this action is appropriate when the notebook brings a large distributed dataset into driver memory and crashes. Specifically, keeping data distributed avoids driver-memory exhaustion, which does not resolve the decisive condition in this scenario.

Answer D is incorrect because this action is appropriate when the notebook is small but oversized compute delays concurrency and wastes capacity. Specifically, resource sizing should match workload needs rather than maximize allocation, which does not resolve the decisive condition in this scenario.

Answer E is incorrect because this action is appropriate when the driver runs out of memory while planning/collecting metadata and executors remain healthy. Specifically, driver sizing targets the actual failing component, which does not resolve the decisive condition in this scenario.

Question 9

For a financial reporting workspace, the organization has fixed the following constraint: the notebook brings a large distributed dataset into driver memory and crashes. Which action best satisfies the requirement?

  1. Right-size the workload instead of using the largest available pool by default
  2. Increase driver memory when the driver is the failing process
  3. Increase executor memory or reduce partition size when executors spill or fail
  4. Repartition skewed data before the wide transformation
  5. Reduce unnecessary collect() operations to the driver

Correct Answer: E

Correct Answer

Answer E is correct because keeping data distributed avoids driver-memory exhaustion. This directly addresses the relevant Fabric behavior while preserving the other stated constraints.

Incorrect Answers

Answer A is incorrect because this action is appropriate when the notebook is small but oversized compute delays concurrency and wastes capacity. Specifically, resource sizing should match workload needs rather than maximize allocation, which does not resolve the decisive condition in this scenario.

Answer B is incorrect because this action is appropriate when the driver runs out of memory while planning/collecting metadata and executors remain healthy. Specifically, driver sizing targets the actual failing component, which does not resolve the decisive condition in this scenario.

Answer C is incorrect because this action is appropriate when worker tasks run out of memory on large partitions while the driver is stable. Specifically, executor-side tuning addresses the task-memory boundary, which does not resolve the decisive condition in this scenario.

Answer D is incorrect because this action is appropriate when one task processes most rows and delays the whole Spark stage. Specifically, better partition distribution reduces the straggler caused by skew, which does not resolve the decisive condition in this scenario.

Question 10

During an operational design review for a healthcare operations workspace, engineers confirm that the notebook is small but oversized compute delays concurrency and wastes capacity. What should they do?

  1. Repartition skewed data before the wide transformation
  2. Reduce unnecessary collect() operations to the driver
  3. Right-size the workload instead of using the largest available pool by default
  4. Increase driver memory when the driver is the failing process
  5. Increase executor memory or reduce partition size when executors spill or fail

Correct Answer: C

Correct Answer

Answer C is correct because resource sizing should match workload needs rather than maximize allocation. This directly addresses the relevant Fabric behavior while preserving the other stated constraints.

Incorrect Answers

Answer A is incorrect because this action is appropriate when one task processes most rows and delays the whole Spark stage. Specifically, better partition distribution reduces the straggler caused by skew, which does not resolve the decisive condition in this scenario.

Answer B is incorrect because this action is appropriate when the notebook brings a large distributed dataset into driver memory and crashes. Specifically, keeping data distributed avoids driver-memory exhaustion, which does not resolve the decisive condition in this scenario.

Answer D is incorrect because this action is appropriate when the driver runs out of memory while planning/collecting metadata and executors remain healthy. Specifically, driver sizing targets the actual failing component, which does not resolve the decisive condition in this scenario.

Answer E is incorrect because this action is appropriate when worker tasks run out of memory on large partitions while the driver is stable. Specifically, executor-side tuning addresses the task-memory boundary, which does not resolve the decisive condition in this scenario.

Question 11

After a recent change in a logistics monitoring solution, the team determines that the notebook code uses an unqualified table name but the session is attached to the wrong data item. Which implementation should be selected?

  1. Attach or reference the correct Lakehouse before reading the table
  2. Correct the OneLake path after the source folder was moved
  3. Grant the executing identity access to the target data
  4. Use the table shortcut or copied local table when the external file layout is not directly queryable as expected
  5. Validate schema before selecting renamed columns

Correct Answer: A

Correct Answer

Answer A is correct because the notebook context must point to the intended Lakehouse/table. This directly addresses the relevant Fabric behavior while preserving the other stated constraints.

Incorrect Answers

Answer B is incorrect because this action is appropriate when the code reads a path that no longer exists following a data-layout change. Specifically, the path reference must track the current OneLake location, which does not resolve the decisive condition in this scenario.

Answer C is incorrect because this action is appropriate when the path exists but the notebook receives an authorization error. Specifically, data access requires appropriate workspace/item/OneLake permissions for the execution identity, which does not resolve the decisive condition in this scenario.

Answer D is incorrect because this action is appropriate when the notebook expects a registered Delta table but only a raw external folder is referenced. Specifically, the data must be exposed in a table-compatible form for table semantics, which does not resolve the decisive condition in this scenario.

Answer E is incorrect because this action is appropriate when the notebook reads the dataset but fails when referencing a column removed upstream. Specifically, transformation logic must align to the current source schema, which does not resolve the decisive condition in this scenario.

Question 12

A Fabric engineering team is reviewing a regional supply-chain platform. The code reads a path that no longer exists following a data-layout change Which action is most appropriate?

  1. Use the table shortcut or copied local table when the external file layout is not directly queryable as expected
  2. Validate schema before selecting renamed columns
  3. Attach or reference the correct Lakehouse before reading the table
  4. Correct the OneLake path after the source folder was moved
  5. Grant the executing identity access to the target data

Correct Answer: D

Correct Answer

Answer D is correct because the path reference must track the current OneLake location. This directly addresses the relevant Fabric behavior while preserving the other stated constraints.

Incorrect Answers

Answer A is incorrect because this action is appropriate when the notebook expects a registered Delta table but only a raw external folder is referenced. Specifically, the data must be exposed in a table-compatible form for table semantics, which does not resolve the decisive condition in this scenario.

Answer B is incorrect because this action is appropriate when the notebook reads the dataset but fails when referencing a column removed upstream. Specifically, transformation logic must align to the current source schema, which does not resolve the decisive condition in this scenario.

Answer C is incorrect because this action is appropriate when the notebook code uses an unqualified table name but the session is attached to the wrong data item. Specifically, the notebook context must point to the intended Lakehouse/table, which does not resolve the decisive condition in this scenario.

Answer E is incorrect because this action is appropriate when the path exists but the notebook receives an authorization error. Specifically, data access requires appropriate workspace/item/OneLake permissions for the execution identity, which does not resolve the decisive condition in this scenario.

Question 13

A data engineer must correct a design for a shared business intelligence platform. The decisive requirement is that the path exists but the notebook receives an authorization error. Which choice best addresses it?

  1. Correct the OneLake path after the source folder was moved
  2. Grant the executing identity access to the target data
  3. Use the table shortcut or copied local table when the external file layout is not directly queryable as expected
  4. Validate schema before selecting renamed columns
  5. Attach or reference the correct Lakehouse before reading the table

Correct Answer: B

Correct Answer

Answer B is correct because data access requires appropriate workspace/item/OneLake permissions for the execution identity. This directly addresses the relevant Fabric behavior while preserving the other stated constraints.

Incorrect Answers

Answer A is incorrect because this action is appropriate when the code reads a path that no longer exists following a data-layout change. Specifically, the path reference must track the current OneLake location, which does not resolve the decisive condition in this scenario.

Answer C is incorrect because this action is appropriate when the notebook expects a registered Delta table but only a raw external folder is referenced. Specifically, the data must be exposed in a table-compatible form for table semantics, which does not resolve the decisive condition in this scenario.

Answer D is incorrect because this action is appropriate when the notebook reads the dataset but fails when referencing a column removed upstream. Specifically, transformation logic must align to the current source schema, which does not resolve the decisive condition in this scenario.

Answer E is incorrect because this action is appropriate when the notebook code uses an unqualified table name but the session is attached to the wrong data item. Specifically, the notebook context must point to the intended Lakehouse/table, which does not resolve the decisive condition in this scenario.

Question 14

For an enterprise lakehouse program, the organization has fixed the following constraint: the notebook expects a registered Delta table but only a raw external folder is referenced. Which action best satisfies the requirement?

  1. Validate schema before selecting renamed columns
  2. Attach or reference the correct Lakehouse before reading the table
  3. Correct the OneLake path after the source folder was moved
  4. Grant the executing identity access to the target data
  5. Use the table shortcut or copied local table when the external file layout is not directly queryable as expected

Correct Answer: E

Correct Answer

Answer E is correct because the data must be exposed in a table-compatible form for table semantics. This directly addresses the relevant Fabric behavior while preserving the other stated constraints.

Incorrect Answers

Answer A is incorrect because this action is appropriate when the notebook reads the dataset but fails when referencing a column removed upstream. Specifically, transformation logic must align to the current source schema, which does not resolve the decisive condition in this scenario.

Answer B is incorrect because this action is appropriate when the notebook code uses an unqualified table name but the session is attached to the wrong data item. Specifically, the notebook context must point to the intended Lakehouse/table, which does not resolve the decisive condition in this scenario.

Answer C is incorrect because this action is appropriate when the code reads a path that no longer exists following a data-layout change. Specifically, the path reference must track the current OneLake location, which does not resolve the decisive condition in this scenario.

Answer D is incorrect because this action is appropriate when the path exists but the notebook receives an authorization error. Specifically, data access requires appropriate workspace/item/OneLake permissions for the execution identity, which does not resolve the decisive condition in this scenario.

Question 15

During an operational design review for a regulated retail analytics platform, engineers confirm that the notebook reads the dataset but fails when referencing a column removed upstream. What should they do?

  1. Grant the executing identity access to the target data
  2. Use the table shortcut or copied local table when the external file layout is not directly queryable as expected
  3. Validate schema before selecting renamed columns
  4. Attach or reference the correct Lakehouse before reading the table
  5. Correct the OneLake path after the source folder was moved

Correct Answer: C

Correct Answer

Answer C is correct because transformation logic must align to the current source schema. This directly addresses the relevant Fabric behavior while preserving the other stated constraints.

Incorrect Answers

Answer A is incorrect because this action is appropriate when the path exists but the notebook receives an authorization error. Specifically, data access requires appropriate workspace/item/OneLake permissions for the execution identity, which does not resolve the decisive condition in this scenario.

Answer B is incorrect because this action is appropriate when the notebook expects a registered Delta table but only a raw external folder is referenced. Specifically, the data must be exposed in a table-compatible form for table semantics, which does not resolve the decisive condition in this scenario.

Answer D is incorrect because this action is appropriate when the notebook code uses an unqualified table name but the session is attached to the wrong data item. Specifically, the notebook context must point to the intended Lakehouse/table, which does not resolve the decisive condition in this scenario.

Answer E is incorrect because this action is appropriate when the code reads a path that no longer exists following a data-layout change. Specifically, the path reference must track the current OneLake location, which does not resolve the decisive condition in this scenario.

Question 16

After a recent change in an IoT operations solution, the team determines that the login connects to the SQL endpoint but receives permission denied on a specific table. Which implementation should be selected?

  1. Grant the required SELECT permission on the object
  2. Correct the schema-qualified object name
  3. Create or refresh the intended view after a dependent column change
  4. Use a supported T-SQL feature or alternative pattern
  5. Resolve a conflicting data type conversion before the insert

Correct Answer: A

Correct Answer

Answer A is correct because object authorization is the direct cause when connectivity succeeds but SELECT is denied. This directly addresses the relevant Fabric behavior while preserving the other stated constraints.

Incorrect Answers

Answer B is incorrect because this action is appropriate when the query references dbo.Sales but the table is in a different schema. Specifically, the object identifier must match the actual schema and name, which does not resolve the decisive condition in this scenario.

Answer C is incorrect because this action is appropriate when a view fails because an underlying column was renamed or removed. Specifically, the view definition must be updated to the current dependency schema, which does not resolve the decisive condition in this scenario.

Answer D is incorrect because this action is appropriate when the parser rejects syntax that is not supported in the Fabric SQL workload being used. Specifically, unsupported syntax requires a supported equivalent rather than retries, which does not resolve the decisive condition in this scenario.

Answer E is incorrect because this action is appropriate when the statement reaches the target but fails converting a source value into the destination column type. Specifically, the data or mapping must be converted to a compatible target type, which does not resolve the decisive condition in this scenario.

Question 17

A Fabric engineering team is reviewing a product usage analytics pipeline. The query references dbo.Sales but the table is in a different schema Which action is most appropriate?

  1. Use a supported T-SQL feature or alternative pattern
  2. Resolve a conflicting data type conversion before the insert
  3. Grant the required SELECT permission on the object
  4. Correct the schema-qualified object name
  5. Create or refresh the intended view after a dependent column change

Correct Answer: D

Correct Answer

Answer D is correct because the object identifier must match the actual schema and name. This directly addresses the relevant Fabric behavior while preserving the other stated constraints.

Incorrect Answers

Answer A is incorrect because this action is appropriate when the parser rejects syntax that is not supported in the Fabric SQL workload being used. Specifically, unsupported syntax requires a supported equivalent rather than retries, which does not resolve the decisive condition in this scenario.

Answer B is incorrect because this action is appropriate when the statement reaches the target but fails converting a source value into the destination column type. Specifically, the data or mapping must be converted to a compatible target type, which does not resolve the decisive condition in this scenario.

Answer C is incorrect because this action is appropriate when the login connects to the SQL endpoint but receives permission denied on a specific table. Specifically, object authorization is the direct cause when connectivity succeeds but SELECT is denied, which does not resolve the decisive condition in this scenario.

Answer E is incorrect because this action is appropriate when a view fails because an underlying column was renamed or removed. Specifically, the view definition must be updated to the current dependency schema, which does not resolve the decisive condition in this scenario.

Question 18

A data engineer must correct a design for a customer-analytics environment. The decisive requirement is that a view fails because an underlying column was renamed or removed. Which choice best addresses it?

  1. Correct the schema-qualified object name
  2. Create or refresh the intended view after a dependent column change
  3. Use a supported T-SQL feature or alternative pattern
  4. Resolve a conflicting data type conversion before the insert
  5. Grant the required SELECT permission on the object

Correct Answer: B

Correct Answer

Answer B is correct because the view definition must be updated to the current dependency schema. This directly addresses the relevant Fabric behavior while preserving the other stated constraints.

Incorrect Answers

Answer A is incorrect because this action is appropriate when the query references dbo.Sales but the table is in a different schema. Specifically, the object identifier must match the actual schema and name, which does not resolve the decisive condition in this scenario.

Answer C is incorrect because this action is appropriate when the parser rejects syntax that is not supported in the Fabric SQL workload being used. Specifically, unsupported syntax requires a supported equivalent rather than retries, which does not resolve the decisive condition in this scenario.

Answer D is incorrect because this action is appropriate when the statement reaches the target but fails converting a source value into the destination column type. Specifically, the data or mapping must be converted to a compatible target type, which does not resolve the decisive condition in this scenario.

Answer E is incorrect because this action is appropriate when the login connects to the SQL endpoint but receives permission denied on a specific table. Specifically, object authorization is the direct cause when connectivity succeeds but SELECT is denied, which does not resolve the decisive condition in this scenario.

Question 19

For an internal finance data estate, the organization has fixed the following constraint: the parser rejects syntax that is not supported in the Fabric SQL workload being used. Which action best satisfies the requirement?

  1. Resolve a conflicting data type conversion before the insert
  2. Grant the required SELECT permission on the object
  3. Correct the schema-qualified object name
  4. Create or refresh the intended view after a dependent column change
  5. Use a supported T-SQL feature or alternative pattern

Correct Answer: E

Correct Answer

Answer E is correct because unsupported syntax requires a supported equivalent rather than retries. This directly addresses the relevant Fabric behavior while preserving the other stated constraints.

Incorrect Answers

Answer A is incorrect because this action is appropriate when the statement reaches the target but fails converting a source value into the destination column type. Specifically, the data or mapping must be converted to a compatible target type, which does not resolve the decisive condition in this scenario.

Answer B is incorrect because this action is appropriate when the login connects to the SQL endpoint but receives permission denied on a specific table. Specifically, object authorization is the direct cause when connectivity succeeds but SELECT is denied, which does not resolve the decisive condition in this scenario.

Answer C is incorrect because this action is appropriate when the query references dbo.Sales but the table is in a different schema. Specifically, the object identifier must match the actual schema and name, which does not resolve the decisive condition in this scenario.

Answer D is incorrect because this action is appropriate when a view fails because an underlying column was renamed or removed. Specifically, the view definition must be updated to the current dependency schema, which does not resolve the decisive condition in this scenario.

Question 20

During an operational design review for a multi-team Fabric deployment, engineers confirm that the statement reaches the target but fails converting a source value into the destination column type. What should they do?

  1. Create or refresh the intended view after a dependent column change
  2. Use a supported T-SQL feature or alternative pattern
  3. Resolve a conflicting data type conversion before the insert
  4. Grant the required SELECT permission on the object
  5. Correct the schema-qualified object name

Correct Answer: C

Correct Answer

Answer C is correct because the data or mapping must be converted to a compatible target type. This directly addresses the relevant Fabric behavior while preserving the other stated constraints.

Incorrect Answers

Answer A is incorrect because this action is appropriate when a view fails because an underlying column was renamed or removed. Specifically, the view definition must be updated to the current dependency schema, which does not resolve the decisive condition in this scenario.

Answer B is incorrect because this action is appropriate when the parser rejects syntax that is not supported in the Fabric SQL workload being used. Specifically, unsupported syntax requires a supported equivalent rather than retries, which does not resolve the decisive condition in this scenario.

Answer D is incorrect because this action is appropriate when the login connects to the SQL endpoint but receives permission denied on a specific table. Specifically, object authorization is the direct cause when connectivity succeeds but SELECT is denied, which does not resolve the decisive condition in this scenario.

Answer E is incorrect because this action is appropriate when the query references dbo.Sales but the table is in a different schema. Specifically, the object identifier must match the actual schema and name, which does not resolve the decisive condition in this scenario.

Question 21

After a recent change in a real-time telemetry service, the team determines that aggregate totals double after a new join and the lookup side contains multiple matches per key. Which implementation should be selected?

  1. Fix the join predicate that multiplies fact rows
  2. Handle nulls explicitly in the business expression
  3. Use a window function instead of GROUP BY when detail rows must remain
  4. Apply the filter before aggregation when the metric definition excludes those rows
  5. Define deterministic ordering for top/latest-row logic

Correct Answer: A

Correct Answer

Answer A is correct because the nonunique join creates row multiplication and must be constrained to the intended relationship.

Incorrect Answers

Answer B is incorrect because this action is appropriate when rows with missing values produce unexpected null results in a calculation. Specifically, the query must define the intended null behavior rather than rely on implicit propagation, which does not resolve the decisive condition in this scenario.

Answer C is incorrect because this action is appropriate when the current query collapses rows but the output requires each row plus a partition-level calculation. Specifically, window functions preserve row detail while computing partition context, which does not resolve the decisive condition in this scenario.

Answer D is incorrect because this action is appropriate when the query aggregates all data and filters groups afterward, producing the wrong business population. Specifically, row filtering must happen at the stage required by the metric definition, which does not resolve the decisive condition in this scenario.

Answer E is incorrect because this action is appropriate when multiple rows share the same timestamp and the query returns nondeterministic winners. Specifically, a complete ordering rule is required when ties are possible, which does not resolve the decisive condition in this scenario.

Question 22

A Fabric engineering team is reviewing a global manufacturing data product. Rows with missing values produce unexpected null results in a calculation Which action is most appropriate?

  1. Apply the filter before aggregation when the metric definition excludes those rows
  2. Define deterministic ordering for top/latest-row logic
  3. Fix the join predicate that multiplies fact rows
  4. Handle nulls explicitly in the business expression
  5. Use a window function instead of GROUP BY when detail rows must remain

Correct Answer: D

Correct Answer

Answer D is correct because the query must define the intended null behavior rather than rely on implicit propagation.

Incorrect Answers

Answer A is incorrect because this action is appropriate when the query aggregates all data and filters groups afterward, producing the wrong business population. Specifically, row filtering must happen at the stage required by the metric definition, which does not resolve the decisive condition in this scenario.

Answer B is incorrect because this action is appropriate when multiple rows share the same timestamp and the query returns nondeterministic winners. Specifically, a complete ordering rule is required when ties are possible, which does not resolve the decisive condition in this scenario.

Answer C is incorrect because this action is appropriate when aggregate totals double after a new join and the lookup side contains multiple matches per key. Specifically, the nonunique join creates row multiplication and must be constrained to the intended relationship, which does not resolve the decisive condition in this scenario.

Answer E is incorrect because this action is appropriate when the current query collapses rows but the output requires each row plus a partition-level calculation. Specifically, window functions preserve row detail while computing partition context, which does not resolve the decisive condition in this scenario.

Question 23

A data engineer must correct a design for a governed self-service analytics domain. The decisive requirement is that the current query collapses rows but the output requires each row plus a partition-level calculation. Which choice best addresses it?

  1. Handle nulls explicitly in the business expression
  2. Use a window function instead of GROUP BY when detail rows must remain
  3. Apply the filter before aggregation when the metric definition excludes those rows
  4. Define deterministic ordering for top/latest-row logic
  5. Fix the join predicate that multiplies fact rows

Correct Answer: B

Correct Answer

Answer B is correct because window functions preserve row detail while computing partition context. This directly addresses the relevant Fabric behavior while preserving the other stated constraints.

Incorrect Answers

Answer A is incorrect because this action is appropriate when rows with missing values produce unexpected null results in a calculation. Specifically, the query must define the intended null behavior rather than rely on implicit propagation, which does not resolve the decisive condition in this scenario.

Answer C is incorrect because this action is appropriate when the query aggregates all data and filters groups afterward, producing the wrong business population. Specifically, row filtering must happen at the stage required by the metric definition, which does not resolve the decisive condition in this scenario.

Answer D is incorrect because this action is appropriate when multiple rows share the same timestamp and the query returns nondeterministic winners. Specifically, a complete ordering rule is required when ties are possible, which does not resolve the decisive condition in this scenario.

Answer E is incorrect because this action is appropriate when aggregate totals double after a new join and the lookup side contains multiple matches per key. Specifically, the nonunique join creates row multiplication and must be constrained to the intended relationship, which does not resolve the decisive condition in this scenario.

Question 24

For a financial reporting workspace, the organization has fixed the following constraint: the query aggregates all data and filters groups afterward, producing the wrong business population. Which action best satisfies the requirement?

  1. Define deterministic ordering for top/latest-row logic
  2. Fix the join predicate that multiplies fact rows
  3. Handle nulls explicitly in the business expression
  4. Use a window function instead of GROUP BY when detail rows must remain
  5. Apply the filter before aggregation when the metric definition excludes those rows

Correct Answer: E

Correct Answer

Answer E is correct because row filtering must happen at the stage required by the metric definition. This directly addresses the relevant Fabric behavior while preserving the other stated constraints.

Incorrect Answers

Answer A is incorrect because this action is appropriate when multiple rows share the same timestamp and the query returns nondeterministic winners. Specifically, a complete ordering rule is required when ties are possible, which does not resolve the decisive condition in this scenario.

Answer B is incorrect because this action is appropriate when aggregate totals double after a new join and the lookup side contains multiple matches per key. Specifically, the nonunique join creates row multiplication and must be constrained to the intended relationship, which does not resolve the decisive condition in this scenario.

Answer C is incorrect because this action is appropriate when rows with missing values produce unexpected null results in a calculation. Specifically, the query must define the intended null behavior rather than rely on implicit propagation, which does not resolve the decisive condition in this scenario.

Answer D is incorrect because this action is appropriate when the current query collapses rows but the output requires each row plus a partition-level calculation. Specifically, window functions preserve row detail while computing partition context, which does not resolve the decisive condition in this scenario.

Question 25

During an operational design review for a healthcare operations workspace, engineers confirm that multiple rows share the same timestamp and the query returns nondeterministic winners. What should they do?

  1. Use a window function instead of GROUP BY when detail rows must remain
  2. Apply the filter before aggregation when the metric definition excludes those rows
  3. Define deterministic ordering for top/latest-row logic
  4. Fix the join predicate that multiplies fact rows
  5. Handle nulls explicitly in the business expression

Correct Answer: C

Correct Answer

Answer C is correct because a complete ordering rule is required when ties are possible. This directly addresses the relevant Fabric behavior while preserving the other stated constraints.

Incorrect Answers

Answer A is incorrect because this action is appropriate when the current query collapses rows but the output requires each row plus a partition-level calculation. Specifically, window functions preserve row detail while computing partition context, which does not resolve the decisive condition in this scenario.

Answer B is incorrect because this action is appropriate when the query aggregates all data and filters groups afterward, producing the wrong business population. Specifically, row filtering must happen at the stage required by the metric definition, which does not resolve the decisive condition in this scenario.

Answer D is incorrect because this action is appropriate when aggregate totals double after a new join and the lookup side contains multiple matches per key. Specifically, the nonunique join creates row multiplication and must be constrained to the intended relationship, which does not resolve the decisive condition in this scenario.

Answer E is incorrect because this action is appropriate when rows with missing values produce unexpected null results in a calculation. Specifically, the query must define the intended null behavior rather than rely on implicit propagation, which does not resolve the decisive condition in this scenario.

Question 26

After a recent change in a logistics monitoring solution, the team determines that the notebook runs manually but fails in orchestration because its required business-date parameter is missing. Which implementation should be selected?

  1. Pass the required notebook parameter from the pipeline
  2. Return a small explicit status rather than a large dataset to the pipeline
  3. Make the notebook write idempotent before enabling pipeline retry
  4. Separate environment setup failures from transformation-code failures
  5. Log the notebook run identifier with the target batch

Correct Answer: A

Correct Answer

Answer A is correct because the pipeline must supply the runtime input expected by the notebook. This directly addresses the relevant Fabric behavior while preserving the other stated constraints.

Incorrect Answers

Answer B is incorrect because this action is appropriate when the pipeline waits on a huge notebook output that should have remained in OneLake. Specifically, orchestration return values should carry control metadata, not bulk data, which does not resolve the decisive condition in this scenario.

Answer C is incorrect because this action is appropriate when a failed orchestration can rerun the notebook and duplicate target data. Specifically, idempotent writes make replay safe, which does not resolve the decisive condition in this scenario.

Answer D is incorrect because this action is appropriate when the notebook never reaches the first transformation statement because its session cannot start. Specifically, session/environment diagnostics must be fixed before code-level debugging, which does not resolve the decisive condition in this scenario.

Answer E is incorrect because this action is appropriate when operators need to trace written data back to the exact orchestrated execution. Specifically, run lineage in the output audit record supports diagnosis and replay decisions, which does not resolve the decisive condition in this scenario.

Question 27

A Fabric engineering team is reviewing a regional supply-chain platform. The pipeline waits on a huge notebook output that should have remained in OneLake Which action is most appropriate?

  1. Separate environment setup failures from transformation-code failures
  2. Log the notebook run identifier with the target batch
  3. Pass the required notebook parameter from the pipeline
  4. Return a small explicit status rather than a large dataset to the pipeline
  5. Make the notebook write idempotent before enabling pipeline retry

Correct Answer: D

Correct Answer

Answer D is correct because orchestration return values should carry control metadata, not bulk data. This directly addresses the relevant Fabric behavior while preserving the other stated constraints.

Incorrect Answers

Answer A is incorrect because this action is appropriate when the notebook never reaches the first transformation statement because its session cannot start. Specifically, session/environment diagnostics must be fixed before code-level debugging, which does not resolve the decisive condition in this scenario.

Answer B is incorrect because this action is appropriate when operators need to trace written data back to the exact orchestrated execution. Specifically, run lineage in the output audit record supports diagnosis and replay decisions, which does not resolve the decisive condition in this scenario.

Answer C is incorrect because this action is appropriate when the notebook runs manually but fails in orchestration because its required business-date parameter is missing. Specifically, the pipeline must supply the runtime input expected by the notebook, which does not resolve the decisive condition in this scenario.

Answer E is incorrect because this action is appropriate when a failed orchestration can rerun the notebook and duplicate target data. Specifically, idempotent writes make replay safe, which does not resolve the decisive condition in this scenario.

Question 28

A data engineer must correct a design for a shared business intelligence platform. The decisive requirement is that a failed orchestration can rerun the notebook and duplicate target data. Which choice best addresses it?

  1. Return a small explicit status rather than a large dataset to the pipeline
  2. Make the notebook write idempotent before enabling pipeline retry
  3. Separate environment setup failures from transformation-code failures
  4. Log the notebook run identifier with the target batch
  5. Pass the required notebook parameter from the pipeline

Correct Answer: B

Correct Answer

Answer B is correct because idempotent writes make replay safe. This directly addresses the relevant Fabric behavior while preserving the other stated constraints.

Incorrect Answers

Answer A is incorrect because this action is appropriate when the pipeline waits on a huge notebook output that should have remained in OneLake. Specifically, orchestration return values should carry control metadata, not bulk data, which does not resolve the decisive condition in this scenario.

Answer C is incorrect because this action is appropriate when the notebook never reaches the first transformation statement because its session cannot start. Specifically, session/environment diagnostics must be fixed before code-level debugging, which does not resolve the decisive condition in this scenario.

Answer D is incorrect because this action is appropriate when operators need to trace written data back to the exact orchestrated execution. Specifically, run lineage in the output audit record supports diagnosis and replay decisions, which does not resolve the decisive condition in this scenario.

Answer E is incorrect because this action is appropriate when the notebook runs manually but fails in orchestration because its required business-date parameter is missing. Specifically, the pipeline must supply the runtime input expected by the notebook, which does not resolve the decisive condition in this scenario.

Question 29

For an enterprise lakehouse program, the organization has fixed the following constraint: the notebook never reaches the first transformation statement because its session cannot start. Which action best satisfies the requirement?

  1. Log the notebook run identifier with the target batch
  2. Pass the required notebook parameter from the pipeline
  3. Return a small explicit status rather than a large dataset to the pipeline
  4. Make the notebook write idempotent before enabling pipeline retry
  5. Separate environment setup failures from transformation-code failures

Correct Answer: E

Correct Answer

Answer E is correct because session/environment diagnostics must be fixed before code-level debugging. This directly addresses the relevant Fabric behavior while preserving the other stated constraints.

Incorrect Answers

Answer A is incorrect because this action is appropriate when operators need to trace written data back to the exact orchestrated execution. Specifically, run lineage in the output audit record supports diagnosis and replay decisions, which does not resolve the decisive condition in this scenario.

Answer B is incorrect because this action is appropriate when the notebook runs manually but fails in orchestration because its required business-date parameter is missing. Specifically, the pipeline must supply the runtime input expected by the notebook, which does not resolve the decisive condition in this scenario.

Answer C is incorrect because this action is appropriate when the pipeline waits on a huge notebook output that should have remained in OneLake. Specifically, orchestration return values should carry control metadata, not bulk data, which does not resolve the decisive condition in this scenario.

Answer D is incorrect because this action is appropriate when a failed orchestration can rerun the notebook and duplicate target data. Specifically, idempotent writes make replay safe, which does not resolve the decisive condition in this scenario.

Question 30

During an operational design review for a regulated retail analytics platform, engineers confirm that operators need to trace written data back to the exact orchestrated execution. What should they do?

  1. Make the notebook write idempotent before enabling pipeline retry
  2. Separate environment setup failures from transformation-code failures
  3. Log the notebook run identifier with the target batch
  4. Pass the required notebook parameter from the pipeline
  5. Return a small explicit status rather than a large dataset to the pipeline

Correct Answer: C

Correct Answer

Answer C is correct because run lineage in the output audit record supports diagnosis and replay decisions. This directly addresses the relevant Fabric behavior while preserving the other stated constraints.

Incorrect Answers

Answer A is incorrect because this action is appropriate when a failed orchestration can rerun the notebook and duplicate target data. Specifically, idempotent writes make replay safe, which does not resolve the decisive condition in this scenario.

Answer B is incorrect because this action is appropriate when the notebook never reaches the first transformation statement because its session cannot start. Specifically, session/environment diagnostics must be fixed before code-level debugging, which does not resolve the decisive condition in this scenario.

Answer D is incorrect because this action is appropriate when the notebook runs manually but fails in orchestration because its required business-date parameter is missing. Specifically, the pipeline must supply the runtime input expected by the notebook, which does not resolve the decisive condition in this scenario.

Answer E is incorrect because this action is appropriate when the pipeline waits on a huge notebook output that should have remained in OneLake. Specifically, orchestration return values should carry control metadata, not bulk data, which does not resolve the decisive condition in this scenario.

Popular posts

img