How should I use these Troubleshooting practice questions?

Read each scenario carefully and choose your answer before revealing the explanation. Then check why your choice was right or wrong. Repeat until the reasoning feels automatic.

Can I practise just Troubleshooting questions in a focused session?

Yes — use the session launcher on this page to start a 10-, 20-, 30- or 50-question session drawn entirely from the Troubleshooting domain.

AZ-204 · topic practice

Troubleshooting practice questions

Practise Microsoft Azure Developer Associate AZ-204 Troubleshooting practice questions — original exam-style scenarios with answer choices, explanations, and analysis of common mistakes.

Courseiva uses original exam-style practice questions designed for learning and revision. The goal is to understand the concepts, recognise exam patterns, and improve through explanations — not memorise copied exam dumps.

Reviewed byJohnson Ajibi· MSc IT Security

5 questionsDomain: Troubleshooting

Practice 10 questions Browse domain →

What the exam tests

What to know about Troubleshooting

Troubleshooting 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.

Watch out for

Common Troubleshooting exam traps

▸Answering from memory before reading the full scenario.
▸Missing a constraint such as cost, availability, security, scope or command context.
▸Choosing a broad answer when the question asks for the most specific fix.
▸Ignoring why the wrong options are tempting.

Practice set

Troubleshooting questions

5 questions · select your answer, then reveal the explanation

Question 1mediummultiple choice

Read the full Troubleshooting explanation →

You are troubleshooting an Azure Function that intermittently throws exceptions. You have enabled Application Insights. You need to capture the exact line of code that caused the exception, even for exceptions that occur during high load. Which feature should you use?

Trap 1: Application Insights Profiler

Incorrect. Profiler traces performance of requests but does not capture exception context or source code lines for errors.

Trap 2: Live Metrics Stream

Incorrect. Live Metrics shows real-time performance data but does not capture detailed exception snapshots.

Trap 3: SQL Insights

Incorrect. SQL Insights is for monitoring database queries, not application exceptions.

Study all Troubleshooting common traps →

A
Snapshot Debugger
Correct. Snapshot Debugger automatically collects debug snapshots on exceptions, providing the call stack and local variables at the moment of failure.
B
Application Insights Profiler
Why wrong: Incorrect. Profiler traces performance of requests but does not capture exception context or source code lines for errors.
C
Live Metrics Stream
Why wrong: Incorrect. Live Metrics shows real-time performance data but does not capture detailed exception snapshots.
D
SQL Insights
Why wrong: Incorrect. SQL Insights is for monitoring database queries, not application exceptions.

Full breakdown with real-world context →

Question 2hardmultiple choice

Read the full NAT/PAT explanation →

You have an Azure App Service web app that experiences intermittent slowness. You enable Application Insights and notice that the "Failed Requests" metric is low, but "Server Response Time" is high for a subset of requests. You want to identify the specific code path causing the delay. Which feature should you use?

Trap 1: Live Metrics.

Incorrect. Live Metrics shows real-time telemetry but does not provide code-level profiling.

Trap 2: Snapshot Debugger.

Incorrect. Snapshot Debugger captures state on exceptions, not general slowness.

Trap 3: Availability tests.

Incorrect. Availability tests monitor uptime and responsiveness from external locations, not internal code paths.

Study all Troubleshooting common traps →

A
Live Metrics.
Why wrong: Incorrect. Live Metrics shows real-time telemetry but does not provide code-level profiling.
B
Snapshot Debugger.
Why wrong: Incorrect. Snapshot Debugger captures state on exceptions, not general slowness.
C
Profiler.
Correct. Profiler traces requests and identifies slow code paths.
D
Availability tests.
Why wrong: Incorrect. Availability tests monitor uptime and responsiveness from external locations, not internal code paths.

Full breakdown with real-world context →

Question 3hardmultiple choice

Read the full Troubleshooting explanation →

You are troubleshooting a containerized application running on Azure Kubernetes Service (AKS). The application logs indicate that it cannot connect to an Azure SQL Database using a managed identity. The pod is configured with a user-assigned managed identity. Which step is most likely missing?

Trap 1: The Azure SQL Database firewall is blocking the pod IP

Wrong: Managed identity uses a token, not the pod IP.

Trap 2: The pod's service account is not linked to the managed identity

Wrong: That is part of the configuration, but the missing add-on is the root cause.

Trap 3: The managed identity is not in the same Microsoft Entra ID tenant…

Wrong: The identity must be in the same tenant.

Study all Troubleshooting common traps →

A
The Azure SQL Database firewall is blocking the pod IP
Why wrong: Wrong: Managed identity uses a token, not the pod IP.
B
The pod's service account is not linked to the managed identity
Why wrong: Wrong: That is part of the configuration, but the missing add-on is the root cause.
C
The managed identity is not in the same Microsoft Entra ID tenant as the AKS cluster
Why wrong: Wrong: The identity must be in the same tenant.
D
The AKS cluster does not have the Azure AD Pod Identity add-on enabled
Correct: The add-on is required to assign the identity to pods.

Full breakdown with real-world context →

Question 4mediummultiple choice

Read the full network assurance explanation →

You are troubleshooting an Azure App Service that runs a Node.js application. The application returns HTTP 500 errors intermittently. Application Insights is configured. Which telemetry item should you examine first to find the root cause?

Trap 1: Traces

Traces are custom log messages, may not capture exceptions.

Trap 2: Dependencies

Dependencies track external calls, not application errors.

Trap 3: Requests

Requests show success/failure but not exception details.

Study all Troubleshooting common traps →

A
Exceptions
Exceptions telemetry captures detailed error information.
B
Traces
Why wrong: Traces are custom log messages, may not capture exceptions.
C
Dependencies
Why wrong: Dependencies track external calls, not application errors.
D
Requests
Why wrong: Requests show success/failure but not exception details.

Full breakdown with real-world context →

Question 5easymultiple choice

Read the full Troubleshooting explanation →

You are troubleshooting a slow web application hosted on Azure App Service. The application uses Azure SQL Database. You suspect that the database queries are taking too long. Which Azure Monitor feature should you use to identify slow queries?

Trap 1: Azure Activity Log

Activity Log records management events.

Trap 2: Azure Advisor

Advisor gives recommendations, not diagnostics.

Trap 3: Azure Monitor Metrics

Metrics show performance counters, not query details.

Study all Troubleshooting common traps →

A
Azure Activity Log
Why wrong: Activity Log records management events.
B
Azure Advisor
Why wrong: Advisor gives recommendations, not diagnostics.
C
Azure Monitor Metrics
Why wrong: Metrics show performance counters, not query details.
D
Azure SQL Analytics
Azure SQL Analytics provides query performance insights.

Full breakdown with real-world context →

Continue with 20-question session →

Free account

Track your progress over time

Create a free account to save your results and see which topics improve across sessions.

Focused Troubleshooting sessions

Start a Troubleshooting only practice session

Every question in these sessions is drawn from the Troubleshooting domain — nothing else.

10 questions 20 questions 30 questions 50 questions

Browse all Troubleshooting questions →Mixed AZ-204 session

Frequently asked questions

What does the AZ-204 exam test about Troubleshooting?: Troubleshooting questions test whether you can apply the concept in context, not just recognise a definition.
How should I use these practice questions?: Select your answer before revealing the explanation. Then read why each option is right or wrong — this active recall approach builds retention far faster than re-reading notes.
Can I practise just Troubleshooting questions in a focused session?: Yes — the session launcher on this page draws every question from the Troubleshooting domain. Use a 10-question session first to gauge your baseline, then move to 20 or 30 once the weak spots are clear.
Where can I practise other AZ-204 topics?: Use the topic links above to move to related areas, or go back to the AZ-204 question bank to see all topics.
Are these real exam questions or dumps?: These are original practice questions written to test the same concepts the AZ-204 exam covers. They are not copied from any real exam or dump site.

Troubleshooting only

10 questions 20 questions 30 questions 50 questions

Mixed AZ-204 session

Track your progress

A free account saves results across sessions and highlights which topics need work.

Study resources

All AZ-204 questions Troubleshooting domain overview AZ-204 exam guide

Exam traps to avoid

▸Answering from memory before reading the full scenario.
▸Missing a constraint such as cost, availability, security, scope or command context.
▸Choosing a broad answer when the question asks for the most specific fix.
▸Ignoring why the wrong options are tempting.

Troubleshooting practice questions

What to know about Troubleshooting

Common Troubleshooting exam traps

Troubleshooting questions

You are troubleshooting an Azure Function that intermittently throws exceptions. You have enabled Application Insights. You need to capture the exact line of code that caused the exception, even for exceptions that occur during high load. Which feature should you use?

You are troubleshooting a containerized application running on Azure Kubernetes Service (AKS). The application logs indicate that it cannot connect to an Azure SQL Database using a managed identity. The pod is configured with a user-assigned managed identity. Which step is most likely missing?

You are troubleshooting an Azure App Service that runs a Node.js application. The application returns HTTP 500 errors intermittently. Application Insights is configured. Which telemetry item should you examine first to find the root cause?

You are troubleshooting a slow web application hosted on Azure App Service. The application uses Azure SQL Database. You suspect that the database queries are taking too long. Which Azure Monitor feature should you use to identify slow queries?

Track your progress over time

Start a Troubleshooting only practice session

Related AZ-204 topic practice pages

Develop Azure compute solutions practice questions

Develop for Azure storage practice questions

Implement Azure security practice questions

Connect to and consume Azure services and third-party services practice questions

Monitor, troubleshoot, and optimize Azure solutions practice questions

AZ-204 fundamentals practice questions

AZ-204 scenario practice questions

AZ-204 troubleshooting practice questions

Frequently asked questions

Track your progress

Study resources

Exam traps to avoid