mcAfee Secure Website
23

Microsoft AZ-104 Bundle

Exam Code: AZ-104

Exam Name Microsoft Azure Administrator

Certification Provider: Microsoft

Corresponding Certification: Microsoft Certified: Azure Administrator Associate

AZ-104 Training Materials $44.99

Reliable & Actual Study Materials for AZ-104 Exam Success

The Latest AZ-104 Exam Questions as Experienced in the Actual Test!

  • 24
    Questions & Answers

    AZ-104 Questions & Answers

    606 Questions & Answers

    Includes questions types found on actual exam such as drag and drop, simulation, type in, and fill in the blank.

  • 25
    AZ-104 Video Course

    AZ-104 Training Course

    132 Video Lectures

    Based on Real Life Scenarios which you will encounter in exam and learn by working with real equipment.

  • exam =30
    Study Guide

    AZ-104 Study Guide

    458 PDF Pages

    Study Guide developed by industry experts who have written exams in the past. They are technology-specific IT certification researchers with at least a decade of experience at Fortune 500 companies.

exam =32

Microsoft Azure Administrator (AZ-104) Practice Tests

Guarantee

Satisfaction Guaranteed

Pass4sure has a remarkable Microsoft Candidate Success record. We're confident of our products and provide no hassle product exchange. That's how confident we are!

99.3% Pass Rate
Total Cost: $194.97
Bundle Price: $149.98

Purchase Individually

  • exam =34
    Questions & Answers

    Questions & Answers

    606 Questions

    $124.99
    exam =35
  • exam =37
    AZ-104 Video Course

    Training Course

    132 Video Lectures

    $39.99
  • exam =36
    Study Guide

    Study Guide

    458 PDF Pages

    $29.99

Microsoft AZ-104 Practice Test 79

Question 780

An Azure Monitor metric alert for VM `vm-ops` evaluates every one minute (`Check every = 1 minute`) but uses a 15-minute `Lookback period` and Average aggregation of Percentage CPU. CPU briefly drops from 92% to 5% for one minute. An operator incorrectly expects the alert's next evaluation to use only the 5% CPU reading. Which configuration detail explains why the alert can remain above its threshold?

  1. The one-minute evaluation cadence checks a rolling 15-minute Average; it does not replace the lookback/aggregation window with a one-minute sample.
  2. Raising the alert's severity from Sev 2 to Sev 1 changes its CPU aggregation window to the duration of the latest sample.
  3. Selecting a different action group causes the metric threshold calculation to ignore all but the newest CPU value.
  4. Changing the alert target to a subscription Activity Log event automatically converts the VM's existing 15-minute CPU average into a one-minute metric.

Explanation

Correct Answer

A:

Metric alert evaluation frequency controls how often the service evaluates the condition. The lookback period independently defines the preceding interval and Average combines its samples, so a one-minute dip might not move the 15-minute result below threshold.

Incorrect Answers

B:

Severity is notification and prioritization metadata. Altering it changes neither the time window over which CPU values are aggregated nor the numerical average used to determine threshold crossings.

C:

Action groups govern what happens after an alert condition fires, such as emailing an on-call address. They do not change CPU measurement, the lookback interval or the aggregation calculation.

D:

An Activity Log alert evaluates resource management events, not a time series of VM platform CPU metrics. Switching alert type discards the requested CPU condition instead of explaining the existing average.

Question 781

An engineer has an Azure Monitor platform CPU utilization metric for a VM scale set, and the metric supports an instance dimension. The engineer wants separate CPU trend lines for each VMSS instance. Which operation meets this exact reporting requirement?

  1. Configure eligible guest/VM Insights collection rather than assume host metrics include every guest counter.
  2. Analyze storage transaction/error metrics with aligned time window and dimensions.
  3. Split metrics by supported instance dimension or resource granularity where available.
  4. Account for ingestion delay and verify resource metric availability before claiming data loss.

Explanation

Correct Answer

C:

When the VMSS CPU metric exposes an instance dimension, splitting the chart by that dimension produces separate time series for individual workers. A single aggregate CPU line cannot reveal an overloaded VMSS instance hidden by the average.

Incorrect Answers

A:

VM Insights and guest data collection expose additional in-guest counters and performance observations; they aren't a substitute for splitting an already supported metric by VMSS instance. The question asks for per-instance charting of the selected metric, so use the available instance dimension or appropriate resource-level series in Metrics.

B:

Storage transaction and error metrics expose storage workload behavior; they don't measure VM-host or application-request performance.

D:

Metrics ingestion delay can explain a recent missing data point, not why a supported dimension is shown as a single aggregate rather than per-instance lines. For an existing VMSS CPU metric with an instance dimension, split by that dimension or select the appropriate instance-level resource time series.

Question 782

An Azure Storage platform metric appears promptly in Azure Monitor Metrics explorer, but a workbook backed by the metric's exported Log Analytics records shows the same latest points several minutes later. Historical points are present and the diagnostic/data collection export is healthy. What is the best interpretation and check before reporting data loss?

  1. Select consistent metric namespace/resource and dimensions, then compare like-for-like periods.
  2. Split metrics by supported instance dimension or resource granularity where available.
  3. Query the VM's platform CPU metric in Azure Monitor Metrics with suitable aggregation.
  4. Account for ingestion delay and verify resource metric availability before claiming data loss.

Explanation

Correct Answer

D:

Platform metrics generally reach Azure Monitor's metrics database sooner than their export reaches a log collection destination; Microsoft documents additional export latency of about three minutes before the collection endpoint. Check the metric's export/ingestion pipeline and timestamps after the expected lag, without calling a temporary delay permanent data loss. If records remain absent, troubleshoot the export configuration separately.

Incorrect Answers

A:

Checking the namespace, source resource and metric dimensions prevents incomparable charts, but both views already refer to the same storage metric. A namespace change would not remove the additional export and ingestion latency between the Metrics database and Log Analytics.

B:

Splitting a supported metric by a dimension changes how the series is displayed, not the time needed to export a platform metric to the monitoring ingestion endpoint. It cannot explain an otherwise healthy Log Analytics copy lagging behind Metrics explorer.

C:

A VM's Percentage CPU metric is a compute-resource measurement and cannot diagnose the Azure Storage metric export path. The question concerns the same storage metric appearing at different times in the platform metrics database and in exported Log Analytics records.

Question 783

A dashboard shows 100% availability but users still see failed API requests. Which change addresses the stated situation most precisely?

  1. Inspect the application's relevant response-time metric rather than infer from CPU alone.
  2. Select Average and Maximum aggregations intentionally and compare over the same interval.
  3. Select service/app health or request-error indicators relevant to the actual user experience.
  4. Select consistent metric namespace/resource and dimensions, then compare like-for-like periods.

Explanation

Correct Answer

C:

A platform availability indicator can measure a different condition from users' API request success. Use application request failures, latency or relevant service health telemetry so the dashboard represents the failures clients actually experience.

Incorrect Answers

A:

Application response time measures request latency; it is not equivalent to host CPU or disk I/O and doesn't solve scope or dimension alignment.

B:

Changing between Average and Maximum aggregations of the same availability series may change its summary, but a 100% platform availability metric can coexist with application-level failed requests. Use actual request errors, application health, latency and service-level response indicators to evaluate the reported impact.

D:

Selecting aligned metrics and dimensions is essential for comparison, but cannot supply a missing resource-log stream or alert notification route.

Question 784

An engineer graphs vm-accounting Percentage CPU over a 30-minute window, but chooses Count as the metric aggregation and misreads the resulting number as average utilization. Which aggregation provides a meaningful CPU percentage over that interval?

  1. Use Sum over the Percentage CPU samples because summing all percentages describes average utilization.
  2. Switch to a Storage transactions metric and divide it by VM CPU readings.
  3. Use Average for the utilization trend, or Maximum when the highest observed percentage is the stated question.
  4. Keep Count, since it always returns the same value as the average CPU percentage.

Explanation

Correct Answer

C:

Azure Monitor Metrics supports aggregations such as Average, Maximum and Count, but they answer different questions. Average summarizes the CPU percentage across collected samples, making it suitable for a utilization trend over 30 minutes. Maximum shows the highest reported percentage in a time interval if a peak is the concern. Count measures the number of data points, not CPU utilization itself. The operator should pick the aggregation corresponding to the specific interpretation and preserve the same time grain when comparing charts.

Incorrect Answers

A:

Sum adds the numeric percentage samples together; it does not normalize by the number of measurements. The result can exceed 100 and should not be interpreted as average CPU utilization. To compare utilization over the specified interval, select Average. Maximum is a different meaningful aggregation when the task is specifically to find the highest observed percentage.

B:

Storage transactions and VM CPU utilization measure different signals. Dividing one by the other does not create an Azure Monitor CPU percentage. The question has already selected the correct VM Percentage CPU metric, so only the aggregation needs correction. Retain the right metric namespace and time window and choose a meaningful percentage aggregation.

D:

Count reports how many metric values exist in a time interval, not their arithmetic mean. A count of 60 samples says nothing directly about whether CPU was 20% or 90%. Interpreting the count as a utilization percentage is the original error. Use an actual numeric utilization aggregation on the Percentage CPU metric.

Question 785

Three App Service instances of the same application run in East US and three in West Europe. Azure Monitor Metrics explorer cannot select resources across regions in one multi-resource metric chart. What is a supported way to build an aggregated cross-region comparison?

  1. Select all six resources in a single Metrics explorer scope, ignoring its same-location restriction.
  2. Set the metric display unit to count; that removes the multiple-region resource-picker restriction.
  3. Use a workbook or query-capable monitoring view that gathers the corresponding metrics from both regions and plots them in the same visualization.
  4. Change the App Service custom domain to a global alias; that automatically combines historical metrics.

Explanation

Correct Answer

C:

An Azure Monitor workbook with appropriate cross-resource query/data sources can compare the regional metric series without assuming one Metrics explorer multi-resource scope spans regions.

Incorrect Answers

A:

Metrics explorer multi-resource selection requires supported resources of the same type, subscription and region; it cannot directly aggregate the two regions together.

B:

Changing display units does not change which resource locations are selectable in the Metrics explorer scope picker.

D:

Hostnames affect client access and DNS, not the Azure Monitor resource picker or the storage of metric time series.

Question 786

A subscription currently retains Azure Activity Log management events in the platform history for 90 days. Compliance requires newly generated resource-management and policy events to be searchable for 18 months in Log Analytics workspace `law-audit`, where `AzureActivity` retention has already been set. No Activity Log export exists, and no recovery of expired history is requested. Which action enables this collection?

  1. Configure a diagnostic setting for the subscription Activity Log, select the required Activity Log categories, send them to law-audit, and verify new rows in AzureActivity.
  2. Create diagnostic settings only on the application VMs to export their resource logs; these automatically include all subscription-wide ARM write/delete events.
  3. Increase the law-audit AzureActivity table retention again without configuring any Activity Log export; the workspace will ingest the missing management events retroactively.
  4. Create a CPU metric alert on all VMs and use its action group to reconstruct the subscription management events in AzureActivity.

Explanation

Correct Answer

A:

Subscription Activity Log events are collected by Azure and retained natively for 90 days; its subscription-level diagnostic setting streams selected new management events to the configured destination. Since law-audit retention is already set, confirming incoming AzureActivity rows completes the requested long-term search path. Previously expired events are not backfilled.

Incorrect Answers

B:

VM resource diagnostics collect resource-level categories, not the subscription Activity Log that records Azure Resource Manager subscription operations. Instrumenting individual VMs would not provide a complete subscription-wide management-activity stream or populate AzureActivity automatically.

C:

A retention policy governs how long rows already ingested into AzureActivity remain. It does not create subscription diagnostic export or recover events that were never sent to the workspace; increasing it again cannot meet the collection requirement.

D:

Platform CPU metrics and metric alerts describe numeric performance signals and notifications, not a historical ledger of ARM creates, deletes and policy changes. They do not feed the AzureActivity table with the missing Activity Log events.

Question 787

The Blob service in storage account stbilling must send its supported data-plane read/write/delete resource log categories into Log Analytics workspace law-audit. Subscription Activity Log export already works but contains no required blob request records. What should the administrator configure?

  1. Export only the subscription Activity Log again; management-plane events contain all Blob service data requests.
  2. Create a diagnostic setting on the supported Blob service resource, enable the required resource log categories and select law-audit as the destination.
  3. Create an Azure Monitor CPU metric alert for the storage account and expect detailed blob request rows to appear.
  4. Enable a resource lock on stbilling without selecting any log collection categories or destination.

Explanation

Correct Answer

B:

Azure resource logs are not collected automatically just because platform metrics or Activity Log export exist. A Blob service diagnostic setting identifies the supported read/write/delete log categories and a destination such as Log Analytics. After saving, new eligible events can flow into the workspace for queries and retention under its configured tables. Use the correct storage service resource path and validate ingestion with a test operation; a diagnostic setting on an unrelated parent resource would not necessarily capture the Blob service categories.

Incorrect Answers

A:

The subscription Activity Log covers subscription-level control-plane operations, not the detailed Blob service resource log stream specified here. Exporting it again would not capture the required individual Blob reads and writes. Configure a resource diagnostic setting for the storage service and its supported log categories instead.

C:

A metric alert evaluates an aggregated signal and can notify a recipient, but it does not enable the detailed Blob service resource log event stream. The question needs per-operation audit records in a Log Analytics workspace. Those records are produced through supported resource log diagnostic categories and destinations, not by choosing CPU utilization alerts.

D:

Management locks control certain operations on Azure Resource Manager resources. They do not create resource logs or automatically route Blob data-plane requests to a workspace. Retention and downstream querying matter only after the relevant diagnostic setting starts collecting the supported events. Apply the Blob service log categories and Log Analytics destination directly.

Question 788

A team expects configuring diagnostic logs to create new records from before the setting existed. Which change addresses the stated situation most precisely?

  1. Configure supported resource diagnostic settings and relevant log categories.
  2. Collect forward events and use other retained sources for historical gaps.
  3. Choose supported category group/categories that match actual audit requirements.
  4. Configure eligible diagnostic setting categories/destinations and access controls.

Explanation

Correct Answer

B:

Diagnostic settings forward eligible resource logs from the time collection is configured; they do not retroactively produce events that were never exported. Seek previously retained copies in other logs or destinations to investigate the earlier period.

Incorrect Answers

A:

Resource diagnostic settings route chosen log categories, not the subscription Activity Log or unprocessed files already in storage.

C:

Selecting a different diagnostic log category controls which supported events will be collected from now onward. It cannot recreate records for a period when collection was never enabled. Use other independently retained logs for the historical gap and keep the correct categories enabled prospectively.

D:

Diagnostic destination permissions and categories govern ingestion; they do not replace a required cross-subscription policy rollout or log query.

Question 789

A compliance team must send supported resource security logs only to workspace law-sec while its separate performance telemetry stream is delivered to an approved Event Hubs namespace. The underlying Azure resource supports the requested diagnostic categories and multiple diagnostic settings. Which configuration keeps the different categories on their intended destinations?

  1. Set only the workspace data-retention period; this automatically routes security and performance categories to their separate targets.
  2. Create distinct supported diagnostic settings with the appropriate category selections and destinations for the security and performance streams.
  3. Enable only the security category on a single setting and assume performance events reach Event Hubs without a destination.
  4. Put both category families and both destinations in one diagnostic setting, even though each destination must receive only its designated category family.

Explanation

Correct Answer

B:

Azure Monitor diagnostic settings specify a resource log or metric category selection and a destination. Where a supported source allows multiple settings, create a security-log setting routed to law-sec and a separate performance setting routed to Event Hubs. This allows each destination to receive only its approved category family instead of sending all categories to every target. Check resource support and avoid unintentionally duplicating event streams; verify fresh events at both destinations after the settings are applied.

Incorrect Answers

A:

Retention settings affect how long data already ingested into a workspace stays available, not how a source sends different data families to separate destinations. The stem requires routing control at the Azure resource. Configure diagnostic settings with explicit categories and destinations before relying on workspace retention policies.

C:

Enabling a category without a corresponding destination cannot route data to an external Event Hubs namespace. Performance logs also require their supported category selection, not just a security-log selection. Configure the separate destination and chosen categories explicitly to satisfy the independent compliance and operations requirements.

D:

One diagnostic setting that selects both category families and both destinations generally sends its selected stream to each configured destination; it cannot express the required per-category split to separate approved targets. Use separate diagnostic settings when the resource supports them, and verify that category and destination combinations remain within current service limits.

Question 790

A Blob service diagnostic setting is already successfully sending resource logs to Log Analytics in resource-specific table mode. A test read appears in the workspace, but an analyst queries only AzureDiagnostics and mistakenly reports that no Blob access audit events were ingested. Which specific query correction addresses the problem?

  1. Recreate the storage account so all Blob resource logs always use the AzureDiagnostics table.
  2. Query the subscription Activity Log instead; it always contains individual Blob read/delete data-plane calls.
  3. Disable Blob resource logging and wait for Azure Monitor Metrics to populate AzureDiagnostics.
  4. Query the StorageBlobLogs resource-specific table in the target workspace and filter by TimeGenerated, operation and result as needed.

Explanation

Correct Answer

D:

Microsoft defines StorageBlobLogs as the Blob service resource-specific Log Analytics table, with TimeGenerated, OperationName, StatusCode and other request fields. Query that table when the diagnostic collection mode is resource-specific; an empty AzureDiagnostics query alone does not show that ingestion failed.

Incorrect Answers

A:

AzureDiagnostics is not the only supported resource-log destination table. Recreating a working storage account would be destructive and would not solve a query aimed at the wrong table.

B:

The Activity Log concerns Azure Resource Manager control-plane events, not a full request-by-request Blob service data-plane audit stream. It cannot substitute for the already-ingested Blob resource logs.

C:

Platform metrics are distinct from resource log records. Turning off diagnostic logging would stop future Blob audit ingestion instead of fixing the analyst's table selection.