Question 50
The planned architecture is: Query Azure Resource Graph across authorized subscriptions using resource inventory KQL-style queries. Workload context: A platform team needs to inventory VM power state and tags across 90 subscriptions rather than inspect each subscription in the portal. Which acceptance test demonstrates that the required behavior works?
- Open the workbook with representative reader permissions and validate each panel renders the expected values.
- Query the configured Log Analytics collection table (resource-specific or AzureDiagnostics as appropriate) and compare records from all three resource IDs.
- Find the Delete Resource Group administrative event and its caller/correlation ID in the activity records.
- Compare Resource Graph results with several known subscriptions and verify subscription scope covers the expected count.
Explanation
Correct Answer
D:This observation directly verifies the intended design: Compare Resource Graph results with several known subscriptions and verify subscription scope covers the expected count. The architecture being tested is: Query Azure Resource Graph across authorized subscriptions using resource inventory KQL-style queries. The original symptom was: The inventory report misses entire subscriptions because an engineer queried a single resource group.
Incorrect Answers
A:The architecture being tested is: Query Azure Resource Graph across authorized subscriptions using resource inventory KQL-style queries.
B:That observation pertains to a separate failure: The centralized workspace contains no firewall decisions although the firewalls are passing traffic. Its cause is: Resource log generation alone does not forward firewall logs without enabled diagnostic settings for the desired destination. It does not confirm the result of this design. The direct proof would be: Compare Resource Graph results with several known subscriptions and verify subscription scope covers the expected count.
C:The alternative test targets: Collect and query the Azure Activity Log for subscription-level control-plane operations rather than application request traces. The scenario's actual proposed remedy is: Query Azure Resource Graph across authorized subscriptions using resource inventory KQL-style queries. Verify that one by: Compare Resource Graph results with several known subscriptions and verify subscription scope covers the expected count.
Question 51
The customer states: A platform team needs to inventory VM power state and tags across 90 subscriptions rather than inspect each subscription in the portal. An incident reveals: The inventory report misses entire subscriptions because an engineer queried a single resource group. What cause best accounts for this evidence?
- Application instrumentation does not capture Azure Resource Manager administrative operations.
- Resource log generation alone does not forward firewall logs without enabled diagnostic settings for the desired destination.
- Static images lack the live query and presentation model provided by Azure Monitor workbooks.
- The reporting source or scope is too narrow for organization-wide Azure resource inventory.
Explanation
Correct Answer
D:The incident is explained by: The reporting source or scope is too narrow for organization-wide Azure resource inventory. The reported symptom is: The inventory report misses entire subscriptions because an engineer queried a single resource group. The corresponding design fix is: Query Azure Resource Graph across authorized subscriptions using resource inventory KQL-style queries.
Incorrect Answers
A:Application instrumentation does not capture Azure Resource Manager administrative operations. The reporting source or scope is too narrow for organization-wide Azure resource inventory.
B:The reported symptom is: The inventory report misses entire subscriptions because an engineer queried a single resource group.
C:Static images lack the live query and presentation model provided by Azure Monitor workbooks. The reporting source or scope is too narrow for organization-wide Azure resource inventory.
Question 52
Workload context: A platform team needs to inventory VM power state and tags across 90 subscriptions rather than inspect each subscription in the portal. The implemented remedy is: Query Azure Resource Graph across authorized subscriptions using resource inventory KQL-style queries. Which ongoing practice most specifically prevents recurrence of this failure: The inventory report misses entire subscriptions because an engineer queried a single resource group.?
- Review delegated read permissions and subscription scope when new landing zones are provisioned.
- Preserve subscription Activity Log export and validate administrative-event retention after organizational changes.
- Review workbook sharing, queries and selected time ranges after changes to workspace schema.
- Use policy-based diagnostic-setting deployment and audit newly created firewalls for required categories.
Explanation
Correct Answer
A:The preventive control is: Review delegated read permissions and subscription scope when new landing zones are provisioned. It targets the earlier cause: The reporting source or scope is too narrow for organization-wide Azure resource inventory. Confirm ongoing effectiveness by: Compare Resource Graph results with several known subscriptions and verify subscription scope covers the expected count.
Incorrect Answers
B:Preserving subscription Activity Log export and validating administrative-event retention after organizational changes would not review delegated read permissions and subscription scope when new landing zones are provisioned.
C:Reviewing workbook sharing, queries and selected time ranges after changes to workspace schema would not review delegated read permissions and subscription scope when new landing zones are provisioned.
D:Using policy-based diagnostic-setting deployment and auditing newly created firewalls for required categories would not review delegated read permissions and subscription scope when new landing zones are provisioned.
Question 53
A solution architect is reviewing a workload: An AKS platform owner wants namespace and pod CPU indicators plus container logs without installing a dashboard on each cluster. The observed incident is: Azure Monitor shows only node VM metrics, not the container namespace or workload logs needed by owners. Which architecture choice most directly removes the identified weakness?
- Configure Azure Monitor Agent with Linux syslog data sources and appropriate facility/severity filters in a DCR.
- Use Azure Monitor Agent with a data collection rule that defines the required Windows sources and workspace destinations.
- Plan Azure Monitor Private Link Scope and supported private endpoints with correct DNS and network reachability for monitored clients.
- Enable supported Azure Monitor Container insights collection for the clusters and attach the appropriate monitoring destination.
Explanation
Correct Answer
D:The evidence (Azure Monitor shows only node VM metrics, not the container namespace or workload logs needed by owners.) identifies the following cause: Host-only telemetry does not capture the desired Kubernetes container and workload context. The design that removes it is: Enable supported Azure Monitor Container insights collection for the clusters and attach the appropriate monitoring destination. The acceptance check is: Inspect cluster/container inventory and a sample pod's logs and performance through centralized monitoring.
Incorrect Answers
A:Configuring Azure Monitor Agent with Linux syslog data sources and appropriate facility/severity filters in a DCR would not enable supported Azure Monitor Container insights collection for the clusters and attach the appropriate monitoring destination.
B:Using Azure Monitor Agent with a data collection rule that defines the required Windows sources and workspace destinations would not enable supported Azure Monitor Container insights collection for the clusters and attach the appropriate monitoring destination.
C:Planning Azure Monitor Private Link Scope and supported private endpoints with correct DNS and network reachability for monitored clients would not enable supported Azure Monitor Container insights collection for the clusters and attach the appropriate monitoring destination.
Question 54
An architect proposes this change: Enable supported Azure Monitor Container insights collection for the clusters and attach the appropriate monitoring destination. The workload context is: An AKS platform owner wants namespace and pod CPU indicators plus container logs without installing a dashboard on each cluster. Which evidence would most directly validate the change?
- Test private endpoint DNS resolution and data flow from a restricted VM with public network access disabled as required.
- Inspect cluster/container inventory and a sample pod's logs and performance through centralized monitoring.
- Verify agent/DCR association and newly populated Perf and WindowsEvent tables for a test VM.
- Emit a controlled syslog event and confirm it lands in the Syslog table with the expected facility and severity.
Explanation
Correct Answer
B:The decisive evidence is: Inspect cluster/container inventory and a sample pod's logs and performance through centralized monitoring. This measures the mechanism of the planned change, not an unrelated Azure service: Enable supported Azure Monitor Container insights collection for the clusters and attach the appropriate monitoring destination.
Incorrect Answers
A:That observation pertains to a separate failure: A restricted VM can no longer deliver monitoring data after public access is closed. Its cause is: The private-link DNS or AMPLS network path for Azure Monitor was not established correctly. It does not confirm the result of this design. The direct proof would be: Inspect cluster/container inventory and a sample pod's logs and performance through centralized monitoring.
C:The decisive evidence is: Inspect cluster/container inventory and a sample pod's logs and performance through centralized monitoring.
D:That observation pertains to a separate failure: No Linux syslog entries appear although the VM can reach Azure Monitor. Its cause is: The applied data collection rule targets the wrong operating-system log source. It does not confirm the result of this design. The direct proof would be: Inspect cluster/container inventory and a sample pod's logs and performance through centralized monitoring.
Question 55
During architecture troubleshooting, a team reports: Azure Monitor shows only node VM metrics, not the container namespace or workload logs needed by owners. Context: An AKS platform owner wants namespace and pod CPU indicators plus container logs without installing a dashboard on each cluster. Which underlying design mistake explains the observed behavior most precisely?
- The applied data collection rule targets the wrong operating-system log source.
- The private-link DNS or AMPLS network path for Azure Monitor was not established correctly.
- Platform metrics are not a replacement for guest log collection through Azure Monitor Agent and DCR sources.
- Host-only telemetry does not capture the desired Kubernetes container and workload context.
Explanation
Correct Answer
D:This is the failure mechanism rather than an incidental symptom: Host-only telemetry does not capture the desired Kubernetes container and workload context. It accounts for: Azure Monitor shows only node VM metrics, not the container namespace or workload logs needed by owners. The architectural repair is: Enable supported Azure Monitor Container insights collection for the clusters and attach the appropriate monitoring destination.
Incorrect Answers
A:The alternative diagnosis “The applied data collection rule targets the wrong operating-system log source” does not match the observed symptom: Azure Monitor shows only node VM metrics, not the container namespace or workload logs needed by owners. Context: An AKS platform owner wants namespace and pod CPU indicators plus container logs without installing a dashboard on each cluster. This is the failure mechanism rather than an incidental symptom: Host-only telemetry does not capture the desired Kubernetes container and workload context. It accounts for: Azure Monitor shows only node VM metrics, not the container namespace or workload logs needed by owners. The evidence instead supports “Host-only telemetry does not capture the desired Kubernetes container and workload context”.
B:The alternative diagnosis “The private-link DNS or AMPLS network path for Azure Monitor was not established correctly” does not match the observed symptom: Azure Monitor shows only node VM metrics, not the container namespace or workload logs needed by owners. Context: An AKS platform owner wants namespace and pod CPU indicators plus container logs without installing a dashboard on each cluster. This is the failure mechanism rather than an incidental symptom: Host-only telemetry does not capture the desired Kubernetes container and workload context. It accounts for: Azure Monitor shows only node VM metrics, not the container namespace or workload logs needed by owners. The evidence instead supports “Host-only telemetry does not capture the desired Kubernetes container and workload context”.
C:The alternative diagnosis “Platform metrics are not a replacement for guest log collection through Azure Monitor Agent and DCR sources” does not match the observed symptom: Azure Monitor shows only node VM metrics, not the container namespace or workload logs needed by owners. Context: An AKS platform owner wants namespace and pod CPU indicators plus container logs without installing a dashboard on each cluster. This is the failure mechanism rather than an incidental symptom: Host-only telemetry does not capture the desired Kubernetes container and workload context. It accounts for: Azure Monitor shows only node VM metrics, not the container namespace or workload logs needed by owners. The evidence instead supports “Host-only telemetry does not capture the desired Kubernetes container and workload context”.
Question 56
The design change is: Enable supported Azure Monitor Container insights collection for the clusters and attach the appropriate monitoring destination. The original failure was: Azure Monitor shows only node VM metrics, not the container namespace or workload logs needed by owners. Which ongoing control best prevents recurrence of the same root cause?
- Test syslog facility coverage and DCR association when provisioning Linux hosts.
- Monitor agent collection health and cluster onboarding as node pools or namespaces change.
- Audit DCR scope and association whenever VMs are rebuilt or added to scale sets.
- Revalidate private DNS zones and endpoint approvals after network peering changes.
Explanation
Correct Answer
B:The key follow-up control is: Monitor agent collection health and cluster onboarding as node pools or namespaces change. It avoids recurrence of the scenario in which: Azure Monitor shows only node VM metrics, not the container namespace or workload logs needed by owners. It addresses: Host-only telemetry does not capture the desired Kubernetes container and workload context.
Incorrect Answers
A:The alternative diagnosis “Test syslog facility coverage and DCR association when provisioning Linux hosts” does not match the observed symptom: The design change is: Enable supported Azure Monitor Container insights collection for the clusters and attach the appropriate monitoring destination. The key follow-up control is: Monitor agent collection health and cluster onboarding as node pools or namespaces change. It avoids recurrence of the scenario in which: Azure Monitor shows only node VM metrics, not the container namespace or workload logs needed by owners. The evidence instead supports “Monitor agent collection health and cluster onboarding as node pools or namespaces change”.
C:The alternative diagnosis “Audit DCR scope and association whenever VMs are rebuilt or added to scale sets” does not match the observed symptom: The design change is: Enable supported Azure Monitor Container insights collection for the clusters and attach the appropriate monitoring destination. The key follow-up control is: Monitor agent collection health and cluster onboarding as node pools or namespaces change. It avoids recurrence of the scenario in which: Azure Monitor shows only node VM metrics, not the container namespace or workload logs needed by owners. The evidence instead supports “Monitor agent collection health and cluster onboarding as node pools or namespaces change”.
D:The alternative diagnosis “Revalidate private DNS zones and endpoint approvals after network peering changes” does not match the observed symptom: The design change is: Enable supported Azure Monitor Container insights collection for the clusters and attach the appropriate monitoring destination. The key follow-up control is: Monitor agent collection health and cluster onboarding as node pools or namespaces change. It avoids recurrence of the scenario in which: Azure Monitor shows only node VM metrics, not the container namespace or workload logs needed by owners. The evidence instead supports “Monitor agent collection health and cluster onboarding as node pools or namespaces change”.
Question 57
A design workshop has this requirement: A team using managed Prometheus for Kubernetes wants to preserve PromQL query semantics rather than attempt equivalent log-event counting. Operators currently observe: Operations search the Log Analytics workspace for Prometheus samples that were never sent there. Select the ONE design remedy that best addresses the root cause.
- Use supported cross-workspace Log Analytics queries with explicitly scoped workspace references and permissions.
- Use Azure Monitor managed service for Prometheus and compatible scrape configuration for the required metrics.
- Configure resource diagnostic settings on each firewall to send supported log categories to the shared Log Analytics workspace.
- Create a log-search alert rule over a KQL query in Log Analytics with appropriate evaluation and frequency.
Explanation
Correct Answer
B:This option addresses the actual design defect: Prometheus metric ingestion/querying is a separate collection path from ordinary Log Analytics resource logs. The correction is: Use Azure Monitor managed service for Prometheus and compatible scrape configuration for the required metrics. Confirm the outcome with: Run a PromQL query for the target workload metric and confirm time series arrive from designated scrape jobs.
Incorrect Answers
A:The alternative diagnosis “Use supported cross-workspace Log Analytics queries with explicitly scoped workspace references and permissions” does not match the observed symptom: Operations search the Log Analytics workspace for Prometheus samples that were never sent there. This option addresses the actual design defect: Prometheus metric ingestion/querying is a separate collection path from ordinary Log Analytics resource logs. The correction is: Use Azure Monitor managed service for Prometheus and compatible scrape configuration for the required metrics. The evidence instead supports “Use Azure Monitor managed service for Prometheus and compatible scrape configuration for the required metrics”.
C:The alternative diagnosis “Configure resource diagnostic settings on each firewall to send supported log categories to the shared Log Analytics workspace” does not match the observed symptom: Operations search the Log Analytics workspace for Prometheus samples that were never sent there. This option addresses the actual design defect: Prometheus metric ingestion/querying is a separate collection path from ordinary Log Analytics resource logs. The correction is: Use Azure Monitor managed service for Prometheus and compatible scrape configuration for the required metrics. The evidence instead supports “Use Azure Monitor managed service for Prometheus and compatible scrape configuration for the required metrics”.
D:The alternative diagnosis “Create a log-search alert rule over a KQL query in Log Analytics with appropriate evaluation and frequency” does not match the observed symptom: Operations search the Log Analytics workspace for Prometheus samples that were never sent there. This option addresses the actual design defect: Prometheus metric ingestion/querying is a separate collection path from ordinary Log Analytics resource logs. The correction is: Use Azure Monitor managed service for Prometheus and compatible scrape configuration for the required metrics. The evidence instead supports “Use Azure Monitor managed service for Prometheus and compatible scrape configuration for the required metrics”.
Question 58
The planned architecture is: Use Azure Monitor managed service for Prometheus and compatible scrape configuration for the required metrics. Workload context: A team using managed Prometheus for Kubernetes wants to preserve PromQL query semantics rather than attempt equivalent log-event counting. Which acceptance test demonstrates that the required behavior works?
- Query the configured Log Analytics collection table (resource-specific or AzureDiagnostics as appropriate) and compare records from all three resource IDs.
- Inject a sample denied event and confirm the KQL query returns records and the alert fires.
- Run a PromQL query for the target workload metric and confirm time series arrive from designated scrape jobs.
- Execute a query combining both workspace IDs and check records include each intended region.
Explanation
Correct Answer
C:The acceptance test is specific: Run a PromQL query for the target workload metric and confirm time series arrive from designated scrape jobs. Its purpose is to establish that the proposed architecture works: Use Azure Monitor managed service for Prometheus and compatible scrape configuration for the required metrics.
Incorrect Answers
A:The alternative test targets: Configure resource diagnostic settings on each firewall to send supported log categories to the shared Log Analytics workspace. The scenario's actual proposed remedy is: Use Azure Monitor managed service for Prometheus and compatible scrape configuration for the required metrics. Verify that one by: Run a PromQL query for the target workload metric and confirm time series arrive from designated scrape jobs.
B:Its purpose is to establish that the proposed architecture works: Use Azure Monitor managed service for Prometheus and compatible scrape configuration for the required metrics.
D:The alternative test targets: Use supported cross-workspace Log Analytics queries with explicitly scoped workspace references and permissions. The scenario's actual proposed remedy is: Use Azure Monitor managed service for Prometheus and compatible scrape configuration for the required metrics. Verify that one by: Run a PromQL query for the target workload metric and confirm time series arrive from designated scrape jobs.
Question 59
The customer states: A team using managed Prometheus for Kubernetes wants to preserve PromQL query semantics rather than attempt equivalent log-event counting. An incident reveals: Operations search the Log Analytics workspace for Prometheus samples that were never sent there. What cause best accounts for this evidence?
- Prometheus metric ingestion/querying is a separate collection path from ordinary Log Analytics resource logs.
- Resource log generation alone does not forward firewall logs without enabled diagnostic settings for the desired destination.
- The required condition is a log-data join, not a single platform metric time series.
- A single-workspace query does not automatically span unrelated workspaces.
Explanation
Correct Answer
A:The recorded behavior follows from: Prometheus metric ingestion/querying is a separate collection path from ordinary Log Analytics resource logs. The appropriate mitigation would be: Use Azure Monitor managed service for Prometheus and compatible scrape configuration for the required metrics. Verify with: Run a PromQL query for the target workload metric and confirm time series arrive from designated scrape jobs.
Incorrect Answers
B:Firewall diagnostic log delivery would not address the need for prometheus metric ingestion/querying is a separate collection path from ordinary Log Analytics resource logs.
C:The required condition is a log-data join, not a single platform metric time series. Prometheus metric ingestion/querying is a separate collection path from ordinary Log Analytics resource logs.
D:A single-workspace query does not automatically span unrelated workspaces. Prometheus metric ingestion/querying is a separate collection path from ordinary Log Analytics resource logs.
Question 60
Workload context: A team using managed Prometheus for Kubernetes wants to preserve PromQL query semantics rather than attempt equivalent log-event counting. The implemented remedy is: Use Azure Monitor managed service for Prometheus and compatible scrape configuration for the required metrics. Which ongoing practice most specifically prevents recurrence of this failure: Operations search the Log Analytics workspace for Prometheus samples that were never sent there.?
- Audit cross-workspace read permission and query workspace references when regions are added.
- Use policy-based diagnostic-setting deployment and audit newly created firewalls for required categories.
- Version KQL alert definitions and test table/schema changes after service updates.
- Validate scrape targets, time-series cardinality and supported retention before enabling additional exporters.
Explanation
Correct Answer
D:The key follow-up control is: Validate scrape targets, time-series cardinality and supported retention before enabling additional exporters. It avoids recurrence of the scenario in which: Operations search the Log Analytics workspace for Prometheus samples that were never sent there. It addresses: Prometheus metric ingestion/querying is a separate collection path from ordinary Log Analytics resource logs.
Incorrect Answers
A:Auditing cross-workspace read permission and querying workspace references when regions are added would not validate scrape targets, time-series cardinality and supported retention.
B:Using policy-based diagnostic-setting deployment and auditing newly created firewalls for required categories would not validate scrape targets, time-series cardinality and supported retention.
C:Log Analytics query access would not validate scrape targets, time-series cardinality and supported retention.
Designing Microsoft Azure Infrastructure Solutions (AZ-305) Practice Tests