Microsoft DP-700 Practice Test 39

Question 380

A team reverts a suspected Spark environment change. What validates that it was the cause of degraded performance?

Run the same notebook with equivalent input under the previous and new environment configurations and compare stage timing, output parity and resource usage.
Confirm only that the rolled-back environment name matches the previous version.
Compare fastest single-run times after rollback against the slowest pre-rollback run.
Ignore job output differences if rollback reduces elapsed time.

Explanation

Correct Answer

An A/B execution controlled for input and capacity establishes technical causality more credibly than simple before/after wall-clock observations.

Incorrect Answers

Names can remain unchanged while published runtime, libraries or compute differ; inspect effective settings.

Cherry-picked timing can misrepresent performance; use comparable representative runs and resource metrics.

A faster run with changed or lost data is not an acceptable environment regression fix.

Question 381

A Fabric Copy activity fails with invalid credentials for a SQL source after password rotation. What should the operator repair?

Increase automated Copy retries without updating authentication.
Update the source connection identity or credential and confirm it has the required database read permissions, then rerun the Copy.
Change the target lakehouse name while keeping the source secret unchanged.
Grant everyone workspace Administrator to address source SQL login.

Explanation

Correct Answer

Authentication is checked by the source connector; additional throughput or retry attempts cannot make an invalid credential valid.

Incorrect Answers

A repeated invalid-secret error is not repaired by retrying the same rejected identity. It does not implement the corrective control requested in this incident.

Destination metadata does not alter source database credentials or access grants. It does not implement the corrective control requested in this incident.

A broad Fabric role is not a substitute for the specific connection principal and database permission. It does not implement the corrective control requested in this incident.

Question 382

A Copy job gets an authentication error on every attempt, while the SQL server is reachable by IP. What explains the continued failure?

The SQL source is unreachable at the network layer, even though basic IP connectivity works.
The lakehouse target lacks V-Order optimization for its Delta files.
Network reachability does not satisfy source authentication, and the stored connection identity or secret is rejected.
The pipeline forgot to set a Fabric domain label matching the SQL database.

Explanation

Correct Answer

A permanent invalid-credential response differs from a transient transport failure and requires connection authorization repair.

Incorrect Answers

IP reachability does not prove successful SQL authentication; the failure identifies a credential boundary.

Storage optimization doesn't validate the upstream SQL user/password after credential rotation.

Workspace domains do not change SQL source authentication or connector credential storage.

Question 383

A source credential is updated after a Copy failure. What is a sound release validation?

Rerun the activity as workspace Admin and treat that privileged success as proof.
Verify only that the SQL server answers ICMP echo requests.
Check historical Copy job counts from before rotation without executing current extraction.
Run a least-privileged connection test using the actual Copy identity and verify a controlled read and destination write from the target source.

Explanation

Correct Answer

A successful source authentication plus representative transfer demonstrates the new connection has sufficient, not excessive, permissions.

Incorrect Answers

A different identity can hide the production connection's outdated password; test the scheduled account.

Ping reachability does not prove the connector logs in using current credentials and retrieves rows.

Prior success cannot validate that the new connection secret is active after rotation.

Question 384

A Copy activity used to map `customer_no`, but the upstream source renamed it to `customer_id`. The run fails on a missing column. What should be fixed?

Inspect the live source schema and update the Copy source projection and destination mapping to the correct supported column contract.
Increase Copy concurrency to recreate the deleted column.
Use the old field name as a workspace title.
Disable all destination logging so the schema error disappears.

Explanation

Correct Answer

A renamed source field invalidates a mapping reference; explicit schema remapping is required to restore the intended data.

Incorrect Answers

More parallelism cannot resolve a field name that is absent from the source schema. It does not implement the corrective control requested in this incident.

Workspace labels are not source column aliases in an activity mapping. It does not implement the corrective control requested in this incident.

Suppressing diagnostics cannot make a missing source field available to the query. It does not implement the corrective control requested in this incident.

Question 385

A pipeline fails with Column not found immediately after a source deployment. The activity still references the old field name. Why?

The source rename automatically updates every stored column mapping on the next run.
The activity mapping is bound to a column that the revised source no longer exposes.
The error must be caused by the lakehouse SQL endpoint being read-only.
The activity has too many Spark executors for the source schema.

Explanation

Correct Answer

A connection can authenticate successfully while its query or mapping fails during schema resolution.

Incorrect Answers

Explicit mappings can retain the old field token and fail until updated against the current schema.

Read-only SQL affects DML at the endpoint, not a Copy source mapping to a renamed column.

Compute sizing cannot resolve an obsolete `customer_no` reference in the mapping.

Question 386

A missing-column mapping has been repaired. Which test verifies correctness beyond successful execution?

Verify only that the Copy activity reports Succeeded after removing the missing field.
Compare only target row counts, without checking the mapped customer key column.
Copy representative new-schema rows and reconcile source-to-sink column names, types and values, including null handling.
Rename the destination table and assume the source column mapping is now correct.

Explanation

Correct Answer

A valid run could still swap or lose values; detailed mapping parity is needed after schema drift.

Incorrect Answers

Dropping the field can make the job green while silently losing customer identity values.

Counts can agree while records contain null or misassigned customer IDs from the renamed source.

Target naming doesn't establish `customer_id` is selected and populated consistently in downstream rows.

Question 387

A fixed Fabric pipeline schedule supplies a `RegionCode` parameter but the pipeline defines `regionCode`. Which correction should be made?

Rename the workspace to RegionCode instead of correcting the parameter.
Increase Spark driver memory while retaining mismatched parameter names.
Remove the parameter and hard-code every region to the default.
Match the scheduled parameter name exactly to the pipeline declaration and bind the activity expression to that declared value.

Explanation

Correct Answer

Fabric schedule parameter names must align with pipeline parameter names to be applied at runtime.

Incorrect Answers

Workspace metadata has no role in binding a scheduled pipeline input. It does not implement the corrective control requested in this incident.

Compute resources cannot alter parameter matching at pipeline submission. It does not implement the corrective control requested in this incident.

A fixed literal avoids the error by discarding intended region-specific behavior, not repairing it. It does not implement the corrective control requested in this incident.

Question 388

A scheduled pipeline runs with its default region even though the schedule shows a new value under a differently cased parameter name. Why?

The schedule input name does not match the declared pipeline parameter, so the override is ignored and the default remains effective.
The mismatch is caused by Fabric automatically treating every parameter name as case-insensitive.
The pipeline needs a different capacity SKU to evaluate schedule-time parameters.
The scheduled task's default RegionCode will be overwritten by the source SQL column name.

Explanation

Correct Answer

Naming mismatch at the trigger-to-pipeline contract prevents the intended value from being passed.

Incorrect Answers

The schedule's `RegionCode` and pipeline's `regionCode` are different identifiers; mismatched bindings can fall back.

Capacity size does not align a trigger parameter key with its declared pipeline variable.

Data columns don't automatically substitute for incorrectly keyed pipeline parameter bindings.

Question 389

An engineer corrects a scheduled pipeline parameter. What test proves the override now works?

Check the schedule editor displays the intended region but do not inspect the effective run parameters.
Trigger the actual fixed schedule or an equivalent scheduled execution, inspect the effective RegionCode in the run and confirm the intended regional source was read.
Run once with the existing default region and accept it as proof of override.
Compare only the trigger execution timestamp without checking activity inputs.

Explanation

Correct Answer

Testing the schedule invocation path detects name mismatch that would be invisible in a manual Run with explicitly supplied parameters.

Incorrect Answers

A displayed value under the wrong key can be ignored at runtime, leaving the default active.

The default-path test cannot demonstrate the corrected scheduled parameter actually reached downstream activities.

An on-time run may still use the wrong region binding and process the wrong source partition.

Question 390

A Dataflow Gen2 refresh fails converting values such as `unknown` to integer. Which correction should be implemented?

Set the Dataflow output column name to Integer without changing its type.
Turn on pipeline activity retries for permanent invalid source tokens.
Identify the failing Power Query type-change step and apply explicit conversion/error handling or quarantine for invalid tokens.
Increase Fabric domain membership for source rows.

Explanation

Correct Answer

Dataflow type conversion follows Power Query semantics; unsupported values must be handled rather than allowed to fail the entire refresh.

Incorrect Answers

A name cannot cast a nonnumeric string into a valid integer value. It does not implement the corrective control requested in this incident.

A deterministic malformed value will fail again until the transformation changes. It does not implement the corrective control requested in this incident.

Governance access cannot repair an invalid Power Query numeric conversion. It does not implement the corrective control requested in this incident.

Implementing Data Engineering Solutions Using Microsoft Fabric (DP-700) Practice Tests

Microsoft DP-700 Practice Test 37 - 10 Questions (Last Reviewed 28-Sep-2026)
Microsoft DP-700 Practice Test 38 - 10 Questions (Last Reviewed 27-Sep-2026)
Microsoft DP-700 Practice Test 39 - 10 Questions (Last Reviewed 26-Sep-2026)
Microsoft DP-700 Practice Test 40 - 10 Questions (Last Reviewed 25-Sep-2026)
Microsoft DP-700 Practice Test 41 - 10 Questions (Last Reviewed 24-Sep-2026)

Pass Your Microsoft DP-700 Exam Easy!

Question 380

Explanation

Correct Answer

Incorrect Answers

Question 381

Explanation

Correct Answer

Incorrect Answers

Question 382

Explanation

Correct Answer

Incorrect Answers

Question 383

Explanation

Correct Answer

Incorrect Answers

Question 384

Explanation

Correct Answer

Incorrect Answers

Question 385

Explanation

Correct Answer

Incorrect Answers

Question 386

Explanation

Correct Answer

Incorrect Answers

Question 387

Explanation

Correct Answer

Incorrect Answers

Question 388

Explanation

Correct Answer

Incorrect Answers

Question 389

Explanation

Correct Answer

Incorrect Answers

Question 390

Explanation

Correct Answer

Incorrect Answers

Implementing Data Engineering Solutions Using Microsoft Fabric (DP-700) Practice Tests