Skip to content

AZ-305 Logging, log routing, and monitoring solutions

AZ-305 Azure Solutions Architect Expert

Azure Recommendations for Logging and Monitoring Solutions

Below are the recommended Azure solutions for the three key areas: logging, log routing, and monitoring, as aligned with the AZ-305 exam objectives.


1. Recommend a Logging Solution

Azure Monitor Logs and Log Analytics Workspace

  • Azure Monitor Logs is the primary logging solution in Azure, providing a unified platform for collecting, analyzing, and acting on telemetry from your cloud and on-premises environments123.
  • Log Analytics Workspace is the central repository where log data is stored and queried. It supports advanced querying, alerting, and visualization of logs from various Azure resources21.
  • Diagnostic Settings are configured on each Azure resource to specify which logs and metrics are collected and where they are sent (e.g., Log Analytics, Storage, Event Hubs)43.

Best Practices:

  • Use Log Analytics workspaces to centralize log data for analysis and compliance.
  • For large or multi-tenant environments, choose between distributed, centralized, or hybrid workspace architectures based on your operational, compliance, and performance needs2.

2. Recommend a Solution for Routing Logs

Diagnostic Settings for Log Routing

  • Diagnostic settings allow you to route platform logs and metrics from Azure resources to one or more destinations:
    • Log Analytics Workspace: For querying and analysis.
    • Azure Storage Account: For long-term archival.
    • Azure Event Hubs: For integration with external SIEMs or third-party tools.
    • Partner Solutions: For specialized monitoring integrations43.

Recommendations:

  • The default and recommended approach is to route resource logs to Azure Monitor Logs (Log Analytics workspace) for unified querying and alerting3.
  • Use Azure Private Link to route logs securely over the Microsoft backbone network, especially for sensitive environments5.
  • For multi-tenant or managed service scenarios, use Azure Lighthouse or guest user access to manage log routing across tenants2.
  • Use Azure Policy to automate the deployment of diagnostic settings at scale5.

3. Recommend a Monitoring Solution

Azure Monitor and Integrated Services

  • Azure Monitor is the comprehensive monitoring platform in Azure, offering data collection, analysis, visualization, and alerting for all Azure resources16.
  • Key Components:
    • Metrics: Real-time performance data.
    • Logs: Activity and diagnostic logs.
    • Alerts: Automated notifications based on defined thresholds or log queries.
    • Workbooks & Dashboards: Custom visualizations for insights.
    • Integration: With Azure Security Center (Defender for Cloud) for security monitoring, and Azure Sentinel for SIEM capabilities1.

Best Practices:

  • Set up baseline metrics and thresholds for proactive monitoring6.
  • Use alert management strategies to avoid alert fatigue and prioritize critical issues67.
  • Regularly review and refine monitoring configurations to align with evolving operational requirements6.
  • For VM monitoring, use Azure Monitor Agent (AMA) and VM Insights for granular data collection and visualization5.
  • Use data collection rules to control what data is collected and optimize costs5.

Summary Table

RequirementRecommended Azure Solution(s)
Logging SolutionAzure Monitor Logs, Log Analytics Workspace, Diagnostic Settings
Log Routing SolutionDiagnostic Settings (to Log Analytics, Storage, Event Hubs, Partners), Azure Private Link, Azure Policy
Monitoring SolutionAzure Monitor (Metrics, Logs, Alerts, Workbooks), Azure Monitor Agent, VM Insights, Integration with Security Center

These recommendations align with Microsoft best practices and are directly relevant to the AZ-305 exam objectives2415.


Summarised with Perplexity.

Footnotes

  1. https://roshancloudarchitect.me/azure-solutions-architect-40-real-world-exam-questions-for-az-305-certification-83140cb8f2d4 2 3 4 5
  2. https://learn.microsoft.com/en-us/azure/azure-monitor/logs/workspace-design 2 3 4 5
  3. https://docs.azure.cn/en-us/azure-monitor/fundamentals/monitor-azure-monitor 2 3 4
  4. https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/diagnostic-settings 2 3
  5. https://learn.microsoft.com/en-us/azure/azure-monitor/vm/best-practices-vm 2 3 4 5
  6. https://www.datacamp.com/tutorial/getting-started-with-azure-monitor 2 3 4
  7. https://learn.microsoft.com/en-us/azure/azure-monitor/best-practices-alerts

If you want to get in touch and hear more about this topic, feel free to contact me on or via .

© 2026 Andrei Bodea

Privacy policy

Privacy Policy

Last Updated: 2026-08-11

Thank you for visiting Compiled Thoughts (the “Blog”). We value your privacy and want to clarify how we handle any information you may provide or that may be collected when you visit this Blog. By accessing or using the Blog, you agree to the terms of this Privacy Policy.

1. Information We Do Not Collect

  • No Analytics or Tracking — We do not run analytics software, tracking pixels, session recording, or any other tool intended to profile visitors or follow them across sites.

  • No Advertisements — Our Blog does not display third-party advertisements and, therefore, does not collect data for advertising or marketing purposes.

  • No Reader Accounts or Subscriptions — Readers cannot create an account or subscribe, so we do not collect or store reader account data. Sign-in exists only for the Blog’s own author, in order to publish content.

  • No Cookies Set By Us — We do not set cookies of our own for any purpose. Please see Section 2 for the third-party services your browser contacts when you visit.

2. Third-Party Services and Automatic Data Collection

The Blog is a static site with no database of readers. However, displaying a page does require your browser to make requests to the services listed below. Those services necessarily receive your IP address, your browser’s user agent, and the address of the page you requested. This happens automatically when you visit, and we ask that you take it into account when reading Section 1.

  • Web Hosting, Netlify — The Blog is hosted by Netlify, which serves every page and may retain standard server logs, including IP addresses, for operational and security purposes.

  • Typefaces, Google Fonts — Every page loads fonts from fonts.googleapis.com and fonts.gstatic.com. As a result, Google receives your IP address and user agent when you visit. We do not use Google Analytics or any other Google advertising or measurement product.

  • Netlify Identity — The home page loads a login widget from identity.netlify.com. It exists solely so the author can sign in to publish, it offers nothing to ordinary readers, and it is not used to identify you. Your browser requests it regardless, and the widget may use your browser’s local storage to hold a sign-in session.

We do not control what these providers log or how long they retain it. Please consult their own privacy policies if that matters to you.

3. Voluntary Information

If you choose to contact us directly (for example, through an email link or contact form, if provided), we may receive personal information such as your name or email address. In such cases:

  • We will use this information solely to respond to your inquiry.

4. No Third-Party Data Sharing

Beyond the automatic requests described in Section 2, we do not share, sell, rent, or otherwise disclose personal information to third parties, because we do not collect or store any personal information about readers. In the event you voluntarily submit personal data (e.g., via direct email), we do not disclose that to any external entity.

5. Children’s Privacy

Our Blog does not target or direct content specifically to children under the age of 13. We do not knowingly collect or maintain personal information from children under 13. If you believe we may have inadvertently received personal information from a child under 13, please contact us immediately so we can delete such information.

6. External Links

Our Blog may contain links to external websites about programming, interviewing, music, books, psychology, or other related content. We are not responsible for the content, privacy policies, or practices of any third-party sites. We encourage you to review the privacy policies of those websites before interacting with them or providing any personal information.

7. Security

Although we do not collect or store personal data on our servers, we still endeavor to use reasonable security measures to protect the Blog’s integrity. However, no data transmission or storage system can be guaranteed to be 100% secure. Your use of the Blog indicates you understand and accept any inherent risks.

8. Changes to This Privacy Policy

We may update or modify this Privacy Policy from time to time to reflect changes in our practices or for other operational, legal, or regulatory reasons. If we make any material changes, we will update the “Last Updated” date at the top of this document. Your continued use of the Blog after any changes signifies your acceptance of the revised Privacy Policy.

9. Contact Us

If you have any questions or concerns about this Privacy Policy, please reach out using the email address in the header of the page.

By using Compiled Thoughts, you acknowledge that you have read, understood, and agree to this Privacy Policy.