Microsoft AZ-104 Exam Dumps, Practice Test Questions

Azure Monitor does not guarantee that metric sets are shared across resource providers. A missing or invalid metric can invalidate the alert design.

Azure Monitor multi-resource views do not cause one provider's metric namespace to become available on another resource type. The chart must use metrics that are actually published and supported for the target resources and namespace.

Azure resource-specific metrics are scoped by resource type and published namespace. Naming a Storage metric namespace for an App Service plan does not cause the latter to emit Storage account metrics. Inspect provider-specific metric definitions and choose a valid namespace.

Metrics summarize numerical measurements, but do not collect the diagnostic resource log records that analysts must search within Log Analytics.

A saved query can only analyze records already present. It does not send missing storage diagnostic events into the workspace.

Action groups send notifications when alerts fire. They are not the ingestion mechanism for storing diagnostic log events in a workspace.

A guest operating-system event log does not necessarily contain Azure Resource Manager role assignment operations outside the VM.

Application request telemetry describes app invocations and performance, not the Azure Resource Manager administrative operations recorded by subscription Activity Log.

Resource Graph is useful for querying current resource inventory and configuration, not as a comprehensive historical log of who changed subscription IAM at a specified time. The subscription's Activity Log administrative events provide the management-plane operation history.

Selecting one currently available category records only that log type. New resource-log categories introduced by the service don't enter the setting automatically, so the strict all-category collection requirement would require manual maintenance and could leave gaps.

The audit group targets logs representing customer interactions with service data or settings. It is a subset of the available resource logs and doesn't promise all non-audit operational categories. It can be suitable for a narrower compliance purpose but fails the stated all-categories requirement.

Azure Activity Log concerns subscription control-plane activity and is not a substitute for per-resource diagnostic settings that collect service resource logs. Administrative activity events do not cover the resource's entire changing family of operational log categories.

Absence from the Activity Log is not proof of no access, especially for ordinary management reads and data-plane activity outside its intended scope. Inferring nonaccess from this incomplete evidence would undermine the audit and leave legitimate accesses unexamined.

RBAC Reader controls which resource-management information an identity may view; it does not retrospectively change the log categories Azure collected. Additional privileges cannot generate historical GET records that were not part of the captured Activity Log stream.

Moving a resource group changes management metadata but does not reconstruct missing log records or change the Activity Log event model. It could introduce unnecessary operational impact while leaving the regulated data-access audit gap unresolved.

The Azure Activity Log records subscription management and control-plane events; it is distinct from an individual PaaS resource’s request-level resource logs. A subscription Activity Log diagnostic setting cannot replace the resource’s missing resource-log categories. The required change belongs to the resource-level diagnostic setting for supported logs.

Workspace retention governs how long ingested records are kept; it cannot recreate past resource logs that were never collected. The resource’s diagnostic setting must be changed to send supported log categories before future request-level records can arrive. A longer retention period would be relevant only after ingestion was configured and running.

Sending platform metrics to Event Hubs changes the metric stream destination, not the resource-log categories selected for Log Analytics. It does not cause the original workspace to ingest request records, and it could remove metrics from that workspace if its destination were replaced. Configure supported resource logs as a separate selected data source.

An alert processing rule affects notification behavior after alerts are generated, not raw diagnostic records ingested through a DCR. A supported ingestion-time DCR transformation is needed to drop DEBUG rows before storage and billing.

A reporting filter changes what readers see but does not prevent DEBUG records from being ingested and billed in the workspace.

Retention determines how long records are stored after ingestion, not which severity rows enter through the DCR.

The agent is already installed; reinstalling it does not bind the relevant rule to the VM. It may leave the same missing collection configuration.

Retention changes how already ingested records are stored, not whether the VM agent receives a rule telling it which Windows events to collect.

Unassociated DCRs do not automatically configure the agent. Another unattached rule would reproduce the same missing event stream.

The request fails at a service quota, not from missing authorization. Additional management permissions do not raise the maximum number of diagnostic settings per resource.

Destinations are settings within each diagnostic configuration. Replacing one destination does not make a sixth diagnostic setting available when five already exist.

Adding categories to an already-invalid sixth settings resource cannot bypass the quota. Consolidating existing settings is the supported design.

A metric alert evaluates conditions and triggers actions; it is not a continuous resource-log export destination. Diagnostic settings must route the requested supported categories.

Reader permits supported workspace queries but does not forward platform logs into the Event Hubs namespace. Export and consumer authorization are separate controls.

Workspace export operates on eligible ingested data, not an implicit collection of every resource log. The case needs diagnostic settings at the emitting resource to stream supported categories.

Choosing additional categories changes data volume, not how long previously ingested rows remain available inside Log Analytics.

Renaming the route does not extend the lifetime of log data held by the workspace.

Ingesting more events cannot extend the retention period for prior log records. The destination table lifecycle must be adjusted.