How many Troubleshooting Scenario Questions questions are on this page?

This page has 8 Troubleshooting Scenario Questions scenario questions for the DP-203 exam, each with detailed explanations and wrong-answer analysis.

How should I approach DP-203 scenario questions?

Read the full scenario before looking at the answer options. Identify the constraint or requirement in the scenario, then eliminate options that are generally true but wrong for this specific case. Scenario questions reward careful reading over pattern matching.

← Back to Microsoft Azure Data Engineer Associate DP-203 questions

Scenario-based practice

Troubleshooting Scenario Questions

Practise Microsoft Azure Data Engineer Associate DP-203 practice questions — original exam-style scenarios covering every exam domain, with detailed explanations, wrong-answer analysis, and common exam traps.

Start full practice test Read exam guide

scenario questions

DP-203

exam code

Microsoft

vendor

Scenario guide

How to approach troubleshooting scenario questions

These questions describe a network symptom and ask you to identify the root cause or the correct fix. They appear across all certification exams and reward systematic thinking over memorisation. The best candidates follow a consistent troubleshooting framework even under time pressure.

Quick answer

Troubleshooting Scenario Questions questions test whether you can apply the concept in context, not just recognise a definition.

How the topic appears in realistic exam-style scenarios.

Which detail in the question changes the correct answer.

How to eliminate plausible but wrong options.

How to connect the question back to the wider exam objective.

Practice scenarios

Question 1mediummultiple choice

Full question →

You are reviewing the ARM template snippet for an Azure Data Lake Storage Gen2 account. The template fails to deploy with an error that the encryption key cannot be accessed. What is the most likely cause?

Exhibit

Refer to the exhibit.

{
  "encryption": {
    "keySource": "Microsoft.Keyvault",
    "keyvaultproperties": {
      "keyvaulturi": "https://mykeyvault.vault.azure.net/",
      "keyname": "mykey",
      "keyversion": "1"
    }
  }
}

A
The key vault does not have soft-delete enabled.
Why it fails: Soft-delete is not required for encryption key access.
B
The Data Lake Storage account does not have Get and Wrap Key permissions on the key vault.
The storage account's identity must have these permissions to use the key.
C
The key name or version is incorrect.
Why it fails: The key name and version are specified.
D
The key vault URI is incorrectly formatted.
Why it fails: The URI appears correctly formatted.

Full breakdown with real-world context →

Question 2mediummultiple choice

Full question →

Your team is troubleshooting slow query performance on a dedicated SQL pool in Azure Synapse Analytics. The query uses a hash-distributed fact table with 60 distributions. After reviewing the execution plan, you notice a high number of data moves. Which action would most likely reduce data movement?

A
Change the distribution type to round-robin.
Why it fails: Round-robin spreads rows evenly but destroys co-location, so every join must shuffle all 60 distributions, increasing data movement. Round-robin suits staging or loading tables with no join keys, not fact tables repeatedly joined on a shared column.
B
Update statistics on all columns used in joins.
Why it fails: Statistics inform cardinality estimates, not distribution placement; stale stats cause poor plans but cannot eliminate data movement when joined columns are not the distribution key. Updating statistics is the right fix for skewed estimates producing bad join strategies, not for a hash-distributed table whose joins require shuffling.
C
Increase the number of distributions to 120.
Why it fails: Raising distributions to 120 splits each distribution's rows further, multiplying shuffle operations across more nodes without co-locating join keys. More distributions help when a single distribution exceeds compute capacity, not when joins move data because keys differ from the distribution column.
D
Redistribute the fact table on the join column using hash distribution.
Hash-distributing the fact table on the join column co-locates matching rows in the same distribution, so joins execute locally instead of shuffling data across the 60 distributions. This directly reduces the high data movement identified in the execution plan.

Full breakdown with real-world context →

Question 3hardmultiple choice

Full question →

Refer to the exhibit. A Stream Analytics job shows increasing watermark delay and input deserialization errors. Which action should be taken first to troubleshoot?

Exhibit

Azure Stream Analytics job diagnostics log:

{
  "time": "2023-08-01T12:00:00Z",
  "properties": {
    "jobId": "job-123",
    "jobName": "IoTStreamJob",
    "events": [
      {
        "time": "2023-08-01T11:59:00Z",
        "type": "WatermarkDelay",
        "properties": {
          "watermarkDelaySeconds": 120,
          "maxWatermarkDelaySeconds": 300
        }
      },
      {
        "time": "2023-08-01T11:59:30Z",
        "type": "InputDeserializationError",
        "properties": {
          "source": "iothub",
          "count": 15
        }
      }
    ],
    "jobOutputWatermark": "2023-08-01T11:57:00Z"
  }
}

A
Check the input data schema and ensure it matches the query
Deserialization errors indicate the incoming event format cannot be parsed against the declared input schema, which directly inflates watermark delay as unreadable events stall progress. Verifying that the input data schema matches the query's field definitions and serialisation format (JSON, Avro, CSV) addresses the root cause before scaling or partition tuning.
B
Change the output to a different sink
Why it fails: Switching the output sink cannot resolve input deserialization errors, since failures occur while reading and parsing the source stream before any output write. Sink changes suit output throttling or write failures, not malformed inbound events.
C
Increase the number of Streaming Units (SUs)
Why it fails: Adding Streaming Units scales compute throughput for CPU-bound or partitioned workloads, but deserialization errors originate from malformed input records, which extra SUs cannot parse. SU increases suit genuine backlog from insufficient parallel processing, not format failures.
D
Set the watermark delay threshold higher
Why it fails: Raising the watermark threshold conceals the symptom without addressing the deserialization errors corrupting the input stream; those malformed events still fail to parse. Threshold tuning suits late-arriving-but-valid data in event-ordering scenarios, not schema or format mismatches.

Full breakdown with real-world context →

Question 4hardmultiple choice

Full question →

You have a production pipeline in Azure Data Factory that copies data from an on-premises SQL Server to Azure Blob Storage using a self-hosted integration runtime. The pipeline fails intermittently with a 'Connection closed' error. The data volume is 50 GB per run. What should you first troubleshoot to resolve this issue?

A
Increase the memory and CPU resources on the self-hosted integration runtime machine and check network stability.
Intermittent 'Connection closed' errors on a self-hosted integration runtime copying 50 GB typically stem from resource exhaustion or unstable network throughput on the runtime host. Increasing CPU and memory and verifying network stability addresses the constrained capacity causing dropped connections before changing pipeline configuration.
B
Increase the 'connection timeout' setting in the linked service to 30 minutes.
Why it fails: A longer connection timeout does not address an intermittently closed connection; the self-hosted integration runtime is likely exhausting concurrent capacity or hitting network instability during the 50 GB transfer. Timeout increases suit consistently slow handshakes, not sporadic mid-transfer drops.
C
Change the copy activity to use staged copy with Azure Blob Storage as an intermediate store.
Why it fails: Staged copy routes data through Blob Storage before loading, adding latency and cost without addressing why the self-hosted integration runtime's connection closes mid-transfer. Staged copy is chosen when the sink cannot accept the source format directly, or for PolyBase-style loading into Synapse.
D
Disable fault tolerance in the copy activity to improve performance.
Why it fails: Disabling fault tolerance makes the copy activity abort on the first incompatible row or transient read error, worsening intermittent failures rather than resolving the closed connection. Fault tolerance is intended to skip malformed rows when loading imperfect source data, not to stabilise network transport.

Full breakdown with real-world context →

Question 5easymultiple choice

Full question →

You are troubleshooting an Azure Databricks job that writes data to Azure Data Lake Storage Gen2. The job fails with '403 Forbidden' error. The Databricks workspace uses a managed identity (system-assigned) for authentication. What should you verify?

A
The storage account name is correct
Why it fails: An incorrect storage account name produces a name-resolution or not-found error, not 403 Forbidden, which signals authenticated-but-unauthorised access. It is tempting because typos are a frequent misconfiguration, and would be correct if the job reported that the account or container could not be located.
B
The storage account firewall is configured to allow Azure services
Why it fails: Allowing Azure services permits traffic from trusted platform services, but the workspace's system-assigned managed identity still needs a role assignment granting access; the firewall alone does not authorise it. It is tempting because firewall rules commonly cause storage failures, and would be correct if the error were a network timeout.
C
A private endpoint is configured between Databricks and the storage account
Why it fails: A private endpoint affects network routing, not authorisation; a missing one yields timeouts or connection failures, not 403. It is tempting because private endpoints are commonly configured for secure Databricks storage access, and would be the answer if the error were a connectivity or DNS failure.
D
The managed identity has 'Storage Blob Data Contributor' role assigned to the storage account
The 403 arises because the system-assigned managed identity lacks data-plane authorisation on the storage account. Granting Storage Blob Data Contributor at the account or container scope supplies the OAuth permissions needed for writes to Data Lake Storage Gen2.

Full breakdown with real-world context →

Question 6hardmultiple choice

Full question →

You have a Data Factory pipeline that runs a U-SQL script in Azure Data Lake Analytics. The script processes terabytes of data and outputs to a CSV file. The pipeline is failing with the error: 'The job failed with UserError: Script execution failed.' You need to troubleshoot the issue. Which approach should you take first?

A
Change the output format to Parquet to reduce file size.
Why it fails: The failure occurs during script execution, before output writing, so changing the sink format cannot resolve a UserError. It is tempting because Parquet reduces file size and speeds up downstream reads, which is the right optimisation when output volume or query performance is the actual problem.
B
Review the job logs in Azure Data Lake Analytics to identify the specific script error.
Azure Data Lake Analytics records detailed job logs, including the vertex and script error behind UserError failures. Reviewing them first pinpoints the faulty U-SQL statement, avoiding guesswork before changing the terabytes-scale script or pipeline configuration.
C
Migrate the U-SQL script to Azure Synapse Spark pool.
Why it fails: Migrating engines is a redesign, not troubleshooting; it discards the diagnostic detail in the U-SQL job output and cannot be the first step. It is tempting because Spark pools are the strategic replacement for the retiring Data Lake Analytics, so migration is correct as a long-term platform decision.
D
Increase the degree of parallelism for the U-SQL job.
Why it fails: Parallelism cannot fix a UserError, which signals a script-level fault such as a syntax error, missing file or bad schema; raising it just re-runs the same broken script. It is tempting because parallelism tuning genuinely helps VertexFailed or performance-related failures on large jobs.

Full breakdown with real-world context →

Question 7mediummultiple choice

Full question →

You are troubleshooting a slow-running pipeline in Azure Data Factory that uses a Copy activity to transfer data from Azure Blob Storage to Azure Synapse Analytics. The pipeline processes about 100 GB of CSV files. The copy performance is poor even though the source and sink are in the same region. What is the most likely cause?

A
The copy activity is not using staging and PolyBase
PolyBase dramatically improves load performance.
B
The source and sink are in different Azure regions
Why it fails: The stem states both source and sink sit in the same region, so cross-region egress cannot be the bottleneck. Cross-region placement is the genuine cause when a Copy activity's throughput is capped by inter-region network latency and bandwidth, which is not the case here.
C
The Data Integration Unit (DIU) setting is too low
Why it fails: A low DIU count limits parallel connections, but the stem gives no evidence of this setting; the question asks for the most likely cause of poor throughput on 100 GB of CSV. DIUs are the correct lever when parallelism is deliberately throttled or defaults are insufficient for large files.
D
The source files are compressed
Why it fails: Compressed source files reduce bytes transferred, so they cannot explain slow copy performance; if anything they improve throughput. Compression is the right consideration when diagnosing CPU-bound decompression overhead or when choosing whether to decompress before the Copy activity.

Full breakdown with real-world context →

Question 8mediummultiple choice

Full question →

You are troubleshooting a failed Azure Synapse Pipeline execution. The pipeline uses a Copy activity to load data from an on-premises SQL Server to Azure Data Lake Storage Gen2. The error indicates a 'Connection timeout' to the on-premises source. The Integration Runtime is Self-Hosted and has been running successfully for months. What is the most likely cause?

A
The SQL Server authentication credentials have expired.
Why it fails: Expired credentials produce authentication failures, not connection timeouts, because the TCP connection to the source is never established. It is tempting since credential expiry is a common pipeline failure, but it would be correct only if the error were a login failure rather than a timeout.
B
The Self-Hosted Integration Runtime is not installed.
Why it fails: The runtime has run successfully for months, so it is installed and registered; an absent runtime would fail immediately at pipeline start, not after months of operation. It is tempting because a missing runtime does cause connectivity failures, but the stem rules this out.
C
The on-premises network configuration has changed.
A self-hosted integration runtime that worked for months rules out credentials and installation faults. A connection timeout to the on-premises SQL Server therefore points to changed network configuration, such as firewall rules, routing, or proxy settings, blocking the runtime's outbound path to the source.
D
The Azure Storage account firewall is blocking access.
Why it fails: The storage firewall governs access to the Azure Data Lake Gen2 sink, not the on-premises SQL Server source, so it cannot cause a source connection timeout. It is tempting because firewall rules commonly block pipeline traffic, but here the failure occurs before data reaches storage.

Full breakdown with real-world context →

These DP-203 practice questions are part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style DP-203 questions with detailed explanations, topic-based practice, mock exams, readiness tracking, and study analytics.

Troubleshooting Scenario Questions

How to approach troubleshooting scenario questions

Quick answer

Related DP-203 topic practice pages

Secure, monitor, and optimize data storage and data processing practice questions

Develop data processing practice questions

Design and implement data storage practice questions

DP-203 fundamentals practice questions

DP-203 scenario practice questions

DP-203 troubleshooting practice questions

Practice scenarios

You are reviewing the ARM template snippet for an Azure Data Lake Storage Gen2 account. The template fails to deploy with an error that the encryption key cannot be accessed. What is the most likely cause?

Exhibit

Your team is troubleshooting slow query performance on a dedicated SQL pool in Azure Synapse Analytics. The query uses a hash-distributed fact table with 60 distributions. After reviewing the execution plan, you notice a high number of data moves. Which action would most likely reduce data movement?

Refer to the exhibit. A Stream Analytics job shows increasing watermark delay and input deserialization errors. Which action should be taken first to troubleshoot?

Exhibit

You are troubleshooting an Azure Databricks job that writes data to Azure Data Lake Storage Gen2. The job fails with '403 Forbidden' error. The Databricks workspace uses a managed identity (system-assigned) for authentication. What should you verify?