The answer is that the query filters on the wrong OperationName, as denied traffic uses 'AzureFirewallApplicationRuleDeny' rather than 'AzureFirewallApplicationRuleHit'. This is because Azure Firewall logs allowed application rule hits under the 'Hit' operation, while denied traffic is explicitly logged under the 'Deny' operation within the same Category of 'AzureFirewallApplicationRule'. When troubleshooting denied Azure Firewall application rule logs, failing to specify the correct OperationName will return zero results even though rules are actively blocking traffic. On the AZ-500 exam, this tests your ability to differentiate between allowed and denied log entries in Azure Firewall diagnostics, a common trap where candidates assume all traffic appears under a single operation name. A reliable memory tip is to remember that "Deny" is spelled out fully in the log—think "D-E-N-Y" for denied, not just a generic "Hit"—so always check the OperationName field for the exact deny action.
AZ-500 Secure networking Practice Question
This AZ-500 practice question tests your understanding of secure networking. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Exhibit
Refer to the exhibit.
KQL query in Microsoft Sentinel:
```
AzureDiagnostics
| where ResourceType == "AZUREFIREWALLS"
| where Category == "AzureFirewallApplicationRule"
| where OperationName == "AzureFirewallApplicationRuleHit"
| where msg_s contains "Deny"
| project TimeGenerated, msg_s
| take 10
```
Refer to the exhibit. You run the KQL query in Microsoft Sentinel to investigate denied application rule traffic through Azure Firewall. The query returns no results, but you know that application rules are being applied and some traffic is being denied. What is the most likely cause?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Refer to the exhibit.
KQL query in Microsoft Sentinel:
```
AzureDiagnostics
| where ResourceType == "AZUREFIREWALLS"
| where Category == "AzureFirewallApplicationRule"
| where OperationName == "AzureFirewallApplicationRuleHit"
| where msg_s contains "Deny"
| project TimeGenerated, msg_s
| take 10
```
A
The time range is too short and the denied events are older.
Why wrong: The query does not specify a time range, so it defaults to last 24 hours. If events are older, they wouldn't appear, but the stem implies traffic is being denied now.
B
The firewall is not configured to log denied traffic.
Why wrong: If logging is enabled, both allowed and denied traffic are logged by default.
C
The query should use the 'AzureFirewallNetworkRule' category for denied traffic.
Why wrong: Application rule denies are logged under 'AzureFirewallApplicationRule' category.
D
The query filters on the wrong OperationName; denied hits use 'AzureFirewallApplicationRuleDeny'.
Denied application rule hits are logged with OperationName 'AzureFirewallApplicationRuleDeny', not 'AzureFirewallApplicationRuleHit'.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The query filters on the wrong OperationName; denied hits use 'AzureFirewallApplicationRuleDeny'.
The query filters on Category == 'AzureFirewallApplicationRule' and OperationName == 'AzureFirewallApplicationRuleHit'. However, denied traffic is logged under Category == 'AzureFirewallApplicationRule' with OperationName == 'AzureFirewallApplicationRuleDeny'. The query uses 'AzureFirewallApplicationRuleHit' which may log only allowed hits, not denies. Alternatively, the logs might be in a different table or property. The most direct fix: the correct OperationName for denies is 'AzureFirewallApplicationRuleDeny'.
Key principle: NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
The time range is too short and the denied events are older.
Why it's wrong here
The query does not specify a time range, so it defaults to last 24 hours. If events are older, they wouldn't appear, but the stem implies traffic is being denied now.
✗
The firewall is not configured to log denied traffic.
Why it's wrong here
If logging is enabled, both allowed and denied traffic are logged by default.
✗
The query should use the 'AzureFirewallNetworkRule' category for denied traffic.
Why it's wrong here
Application rule denies are logged under 'AzureFirewallApplicationRule' category.
✓
The query filters on the wrong OperationName; denied hits use 'AzureFirewallApplicationRuleDeny'.
Why this is correct
Denied application rule hits are logged with OperationName 'AzureFirewallApplicationRuleDeny', not 'AzureFirewallApplicationRuleHit'.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Static NAT maps one inside address to one outside address.
Common exam traps
Common exam trap: NAT rules depend on direction and matching traffic
NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.
Detailed technical explanation
How to think about this question
NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.
KKey Concepts to Remember
Static NAT maps one inside address to one outside address.
PAT allows many inside hosts to share one public address using ports.
Inside local and inside global describe the private and translated addresses.
NAT ACLs identify traffic for translation, not always security filtering.
TExam Day Tips
→Identify inside and outside interfaces first.
→Check whether the scenario needs static NAT, dynamic NAT or PAT.
→Do not confuse NAT matching ACLs with normal packet-filtering intent.
Key takeaway
NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
Real-world example
How this comes up in practice
A healthcare organisation deploys an application with a public-facing web tier and a private database tier. The database subnet has no public IP and only accepts connections from the web tier's security group. Questions like this test whether you can design cloud network isolation using VNets/VPCs, subnets, and security group rules.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this AZ-500 question in full detail.
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related AZ-500 NAT questions on configuration and troubleshooting.
Secure networking — This question tests Secure networking — Static NAT maps one inside address to one outside address..
What is the correct answer to this question?
The correct answer is: The query filters on the wrong OperationName; denied hits use 'AzureFirewallApplicationRuleDeny'. — The query filters on Category == 'AzureFirewallApplicationRule' and OperationName == 'AzureFirewallApplicationRuleHit'. However, denied traffic is logged under Category == 'AzureFirewallApplicationRule' with OperationName == 'AzureFirewallApplicationRuleDeny'. The query uses 'AzureFirewallApplicationRuleHit' which may log only allowed hits, not denies. Alternatively, the logs might be in a different table or property. The most direct fix: the correct OperationName for denies is 'AzureFirewallApplicationRuleDeny'.
What should I do if I get this AZ-500 question wrong?
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related AZ-500 NAT questions on configuration and troubleshooting.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
What is the key concept behind this question?
Static NAT maps one inside address to one outside address.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This AZ-500 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-500 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.