The correct answer is to use Azure Resource Graph queries within an Azure Logic App scheduled to run weekly, sending the report via email. This design works because Azure Resource Graph provides a powerful, fast query engine that can instantly scan all resources and their tags across subscriptions, while Azure Logic Apps handles the scheduling and email delivery without requiring complex scripting. On the AZ-305 exam, this scenario tests your ability to differentiate between governance tools: Azure Policy enforces tagging rules but cannot generate scheduled reports, Azure Monitor Alerts are for real-time thresholds not weekly summaries, and Azure Automation runbooks are overkill for this simple orchestration. The common trap is choosing Azure Policy because it deals with tags, but remember that Policy is for enforcement, not reporting. Memory tip: think “Graph for data, Logic for schedule”—the combination of a query engine and a scheduler is the lightweight, serverless solution Azure recommends for automated compliance reports.
AZ-305 Practice Question: Design identity, governance, and monitoring solutions
This AZ-305 practice question tests your understanding of design identity, governance, and monitoring solutions. 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.
Your company has a large Azure environment with thousands of resources. You need to design a solution to track resource ownership and ensure that resources are cleaned up when projects end. You want to use a tag-based approach where each resource has an 'Owner' and 'Project' tag. Additionally, you need to generate a weekly report of resources that are not tagged or have been orphaned (no recent activity). What should you include in the design?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use Azure Resource Graph queries in an Azure Logic App scheduled to run weekly, and send the report via email.
Option C is correct because Azure Resource Graph can query all resources and their tags, and Azure Logic Apps can schedule the query and send a report via email. Option A is wrong because Azure Policy can enforce tags but does not generate reports natively. Option B is wrong because Azure Monitor alerts are for real-time notifications, not scheduled reports. Option D is wrong because Azure Automation runbooks can do this but are more complex than Logic Apps.
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.
✗
Use Azure Policy to audit missing tags and create a custom dashboard in Azure Monitor.
Why it's wrong here
Policy audits but does not generate weekly email reports.
✗
Use Azure Monitor alerts with a metric alert for unmodified resources.
Why it's wrong here
Alerts are not designed for scheduled reporting.
✗
Use Azure Automation runbook to inventory resources and store in a SQL database, then use Power BI to report.
Why it's wrong here
Overly complex; Logic App is simpler.
✓
Use Azure Resource Graph queries in an Azure Logic App scheduled to run weekly, and send the report via email.
Why this is correct
Logic Apps can execute queries and send formatted reports.
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 cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this AZ-305 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-305 NAT questions on configuration and troubleshooting.
Design identity, governance, and monitoring solutions — This question tests Design identity, governance, and monitoring solutions — Static NAT maps one inside address to one outside address..
What is the correct answer to this question?
The correct answer is: Use Azure Resource Graph queries in an Azure Logic App scheduled to run weekly, and send the report via email. — Option C is correct because Azure Resource Graph can query all resources and their tags, and Azure Logic Apps can schedule the query and send a report via email. Option A is wrong because Azure Policy can enforce tags but does not generate reports natively. Option B is wrong because Azure Monitor alerts are for real-time notifications, not scheduled reports. Option D is wrong because Azure Automation runbooks can do this but are more complex than Logic Apps.
What should I do if I get this AZ-305 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-305 NAT questions on configuration and troubleshooting.
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-305 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-305 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.