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 80

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.

Question 791

A team sees no logs because a diagnostic setting references a deleted Event Hub. Which Azure configuration or procedure is the best fit?

  1. Export the subscription Activity Log using diagnostic settings to a supported destination.
  2. Repair target destination and permissions, then validate new event ingestion.
  3. Enable the required diagnostic log category and send it to the correct workspace.
  4. Deploy via Azure Policy deployIfNotExists or infrastructure automation as appropriate.

Explanation

Correct Answer

B:

A diagnostic setting whose Event Hub destination was deleted cannot deliver new events to that target. Update the setting to a valid destination, ensure authorization and test new ingestion; changing the Log Analytics query alone will not recreate delivery.

Incorrect Answers

A:

Activity Log export targets subscription-level administrative events, not the application resource logs asked for in this scenario.

C:

Enabling another diagnostic log category cannot restore delivery to a deleted Event Hub destination. Resource logging configuration already exists but its output target no longer resolves. Update the diagnostic setting's destination and required permissions, then generate a new event and verify ingestion at the replacement destination.

D:

Policy deployIfNotExists automates applying settings to resources; it does not correct a wrong destination/table or query definition by itself.

Question 792

A policy requires diagnostic settings on every new supported VM resource. What should the administrator do to resolve this specific case?

  1. Deploy via Azure Policy deployIfNotExists or infrastructure automation as appropriate.
  2. Repair target destination and permissions, then validate new event ingestion.
  3. Route to Log Analytics or ingest into a queryable table, not just raw storage.
  4. Distinguish platform metric collection from resource log/table retention.

Explanation

Correct Answer

A:

Azure Policy with `deployIfNotExists` can detect missing diagnostic settings on supported resources and deploy the prescribed settings through an identity with appropriate permissions. It also supports consistent onboarding of new VMs without manual portal updates for every resource.

Incorrect Answers

B:

Repairing one deleted or unauthorized diagnostics destination is a manual fix for an existing collection failure. It doesn't automatically onboard every newly created VM to a mandated diagnostics configuration. Use an appropriately scoped Azure Policy `deployIfNotExists` initiative or supported deployment automation with the required identity permissions.

C:

A Log Analytics workspace makes data queryable after ingestion; a raw-storage destination alone does not enable KQL tables.

D:

Azure platform metrics and resource logs have different collection and retention paths; changing one does not automatically fix the other.

Question 793

An Azure Storage account exposes its supported Transactions platform metric in Azure Monitor Metrics. Security needs six months of transaction-volume trend analysis. Administrators extended the `AzureActivity` Log Analytics table to 180 days, but no export of this storage metric was configured and Metrics explorer still retains its native metric history for 93 days. Which change captures future metric history for the required longer analysis window without misrepresenting native Metrics retention?

  1. Extend the `AzureActivity` table to 180 days and query it as if Azure Storage Transactions platform metrics were automatically represented by subscription activity events.
  2. Configure supported platform metric export (for example `AllMetrics`) on the storage account diagnostic setting to a Log Analytics workspace, then set retention on the exported metrics table for at least 180 days and query those ingested records.
  3. Increase native Azure Monitor Metrics explorer retention for this one Transactions series from 93 to 180 days by changing its chart time picker.
  4. Enable only Blob read/write resource-log categories such as `StorageRead` and assume those event rows are an exact historic copy of the platform Transactions metric, without exporting metric data.

Explanation

Correct Answer

B:

Azure Monitor retains native platform/custom metric values for 93 days. Microsoft documents export of supported platform metrics to Log Analytics for longer trends; the resulting log table has separately configured analytics/total retention. Configuring the storage account’s applicable metric diagnostic category before future samples arrive, then retaining those ingested records for the requested period, meets the six-month need. It does not retroactively recover expired native metric values.

Incorrect Answers

A:

`AzureActivity` records subscription management and policy activity, not an automatic six-month archive of this storage account’s Transactions platform metric. Changing that table’s retention cannot preserve metric samples that were never exported. The case already says metric export was not configured.

C:

The Metrics explorer time picker controls the visualization range, not the platform metric database retention setting. Native platform and custom metrics use a documented 93-day retention and the portal also limits a single metric chart’s displayed span. Increasing a chart interval cannot create missing historic data.

D:

Blob resource logs document individual storage operations under their selected categories, and can be valuable for diagnostics. They are not a substitute for the preaggregated Transactions platform metric time series. For the specifically requested metric and six-month trend, export the supported metric and retain its resulting log data.

Question 794

An Azure Firewall already sends its supported resource-log categories to a Log Analytics workspace using legacy Azure diagnostics mode. The SOC wants new events in the supported dedicated resource-specific tables, while retaining historical rows already ingested in `AzureDiagnostics`. Which diagnostic-setting adjustment addresses that table-layout requirement?

  1. Increase the diagnostic setting's Storage destination retention only; existing Log Analytics records will then automatically move into dedicated tables.
  2. Switch the supported diagnostic setting collection mode for Azure Firewall resource logs to resource-specific tables, and query old AzureDiagnostics history separately or with union as needed.
  3. Delete the Log Analytics destination and expect Event Hubs to populate the same resource-specific workspace tables without a data pipeline.
  4. Replace resource-log categories with generic platform CPU metrics; those metrics automatically include all firewall rule decision records.

Explanation

Correct Answer

B:

Azure Monitor diagnostic settings support resource-specific collection mode for supported resources including Azure Firewall. New selected log-category events are written into dedicated tables rather than AzureDiagnostics. Historical AzureDiagnostics rows remain until their normal retention expires and can be queried or combined separately.

Incorrect Answers

A:

Changing storage retention affects data stored in Azure Storage, not how Log Analytics organizes existing resource-log rows. It does not migrate legacy AzureDiagnostics data into new resource-specific tables.

C:

Event Hubs is an event-streaming destination, not an automatic way to create Log Analytics tables. Removing the workspace destination would stop direct workspace ingestion unless another supported integration is explicitly configured.

D:

Platform CPU metrics are numerical signals rather than Azure Firewall detailed resource log events. Changing category to a metric would discard the requested rule/event details and would not achieve resource-specific log tables.

Question 795

An Azure resource supports the diagnostic setting category groups `audit` and `allLogs`. Security must collect only audit-relevant resource log categories without automatically including operational log categories. Which category-group selection should be made?

  1. Select the `audit` category group for supported resources and verify the destination receives the required audit event types.
  2. Select `allLogs` because it excludes nonaudit categories by definition.
  3. Use a metric-only diagnostic setting; the metric stream replaces audit records.
  4. Disable all diagnostic settings because Activity Log permanently contains every service resource audit event.

Explanation

Correct Answer

A:

The audit category group groups supported customer interaction and security/audit resource logs without requiring all nonaudit resource categories.

Incorrect Answers

B:

The allLogs group aggregates all supported resource-log categories, usually including more than audit events and potentially increasing ingestion volume.

C:

Resource metrics are not a substitute for detailed audit resource logs, event identities and operations.

D:

Azure Activity Log covers management/control-plane operations but does not replace every service resource audit log, and its default retention is limited.

Question 796

An Azure resource already streams its required audit categories to security workspace law-sec through one Azure Monitor diagnostic setting. Compliance now requires the same resource logs to be sent independently to a second Log Analytics workspace law-archive, without removing the existing route. What diagnostic-setting design is supported?

  1. Add a second Log Analytics workspace destination to the same diagnostic setting; multiple destinations of the same type are allowed without limit.
  2. Change the first diagnostic setting from audit to allLogs and expect an additional workspace to be created automatically.
  3. Send the resource logs to a public DNS record named law-archive so Azure Monitor resolves the second workspace.
  4. Create a second diagnostic setting on the resource targeting law-archive, staying within the per-resource diagnostic-settings limit.

Explanation

Correct Answer

D:

Azure Monitor supports separate diagnostic settings to send a resource's logs to multiple Log Analytics workspaces, with at most five settings per resource. Keep the original law-sec setting and create a second approved log route to law-archive, subject to proper permissions and collection categories.

Incorrect Answers

A:

One Azure Monitor diagnostic setting supports no more than one destination of each type. It cannot contain two distinct Log Analytics workspaces as two destinations of that same type.

B:

Changing categories controls which resource events are collected; the allLogs category group neither creates another workspace nor adds another Log Analytics destination.

C:

An Azure public DNS record provides name resolution and is not an Azure Monitor diagnostic destination. Workspace routes must be configured explicitly on diagnostic settings.

Question 797

Microsoft Entra interactive sign-in events are already being ingested into the `SigninLogs` table of workspace `law-identity`. A SOC analyst wants individual failed interactive sign-in attempts ingested during the last 24 hours, showing each user, application and error code, rather than success rows, non-interactive workload events or summary counts. Which KQL query meets the request?

  1. SigninLogs | where TimeGenerated >= ago(24h) and ResultType == "0" | project TimeGenerated, UserPrincipalName, AppDisplayName, ResultType, ResultDescription
  2. SigninLogs | where TimeGenerated >= ago(24h) and ResultType != "0" | project TimeGenerated, UserPrincipalName, AppDisplayName, ResultType, ResultDescription
  3. AADNonInteractiveUserSignInLogs | where TimeGenerated >= ago(24h) | project TimeGenerated, UserPrincipalName, AppDisplayName, ResultType
  4. SigninLogs | where TimeGenerated >= ago(24h) | summarize AttemptCount=count() by AppDisplayName

Explanation

Correct Answer

B:

SigninLogs is the table for the specified ingested interactive sign-ins. TimeGenerated bounds the ingested rows to the requested day and ResultType != "0" selects error-code outcomes; project retains one row per attempt with the user, app, code and description. No summarize step destroys the individual evidence.

Incorrect Answers

A:

Microsoft Learn defines ResultType 0 as a successful SigninLogs sign-in. Comparing ResultType to "0" returns the successful attempts, the opposite of the requested failed events, even though the 24-hour time filter and projected columns are appropriate.

C:

The non-interactive sign-in table represents a different event type from the interactive SigninLogs stream named in the scenario. Switching tables and omitting a failed-result filter cannot return precisely the requested failed interactive user attempts.

D:

Summarize groups all recent attempts by app, mixing successful and failed results and discarding each event’s identity, timestamp and result code. It does not return the individual failed sign-in records that the SOC requested.

Question 798

A custom Azure Monitor Logs table `AppEvents_CL` contains one row per request, including successes, with `TimeGenerated`, string `ServiceName_s`, and Boolean `IsError_b` fields. A team needs the number of error requests from the last 24 hours grouped by service. Which KQL pipeline returns the required counts?

  1. `AppEvents_CL | where TimeGenerated >= ago(24h) and IsError_b == true | summarize ErrorCount=count() by ServiceName_s`
  2. Use KQL `summarize count() by bin(TimeGenerated, 15m)` with an appropriate where clause.
  3. Check diagnostic ingestion/table name and query time range rather than assume no events.
  4. Use KQL `summarize arg_max(TimeGenerated, *) by Computer` on the Heartbeat table.

Explanation

Correct Answer

A:

The where predicate removes successful events and restricts the period to the last 24 hours before aggregation. The summarize count() by ServiceName_s operation then returns an error-event count for each service. Both the specified schema and the error filter are necessary; an unfiltered count would include successful requests.

Incorrect Answers

B:

TimeGenerated bins produce a chronological histogram, not one error total per service. Even after an error predicate is added, this option groups by quarter-hour boundaries rather than ServiceName_s and therefore answers a different question.

C:

Checking diagnostic ingestion and the table name is useful if records appear absent, but this case already has request events and needs a numerical aggregation. Troubleshooting the destination does not filter IsError_b or calculate error counts grouped by ServiceName_s.

D:

A Heartbeat arg_max operation returns the most recent computer observation, not request error counts from AppEvents_CL. It neither filters IsError_b nor counts events grouped by ServiceName_s, so it cannot satisfy this service-error aggregation.

Question 799

One Log Analytics workspace receives Azure Monitor Heartbeat rows from several subscriptions. Two Azure VMs share the guest computer name `web01` but have different Azure resource IDs. The operator needs the latest full heartbeat row for EACH Azure VM, without merging same-named machines. Which KQL query meets this requirement?

  1. `Heartbeat | where isnotempty(_ResourceId) | summarize arg_max(TimeGenerated, *) by _ResourceId`
  2. Use KQL `summarize count() by bin(TimeGenerated, 15m)` with an appropriate where clause.
  3. Use KQL `summarize count() by ServiceName` on the relevant log table.
  4. Use a suitable KQL join on normalized keys with constrained time ranges.

Explanation

Correct Answer

A:

Heartbeat identifies each Azure VM using its _ResourceId, which remains distinct even when guest Computer names collide across subscriptions. After excluding non-resource heartbeat rows, arg_max(TimeGenerated, *) by _ResourceId returns the latest complete observation for each Azure resource. Grouping only by Computer would incorrectly merge same-named VMs in this workspace.

Incorrect Answers

B:

Counting events by 15-minute TimeGenerated bin produces a volume time series, not the last complete heartbeat for each Azure VM. It cannot preserve separate identities for same-named resources or return the latest per-resource record.

C:

A service-name aggregate counts records by application service, not by the unique Azure VM resource identifier. It cannot return each VM’s most recent Heartbeat observation, especially when two guest computers have the same name.

D:

Joining other tables can enrich Heartbeat data, but this scenario already contains timestamps and unique Azure VM resource IDs in Heartbeat itself. A join does not select the latest row per VM and can multiply records unless its keys are controlled; use arg_max grouped by _ResourceId.

Question 800

A Log Analytics custom table `AppEvents_CL` records one row per request with datetime `TimeGenerated` and string `Result_s` equal to `Success` or `Failure`. A dashboard needs the count of failed requests in each 15-minute time bucket over the last six hours. Which complete KQL query returns that trend without counting successes?

  1. `AppEvents_CL | where TimeGenerated >= ago(6h) and Result_s == "Failure" | summarize FailureCount=count() by Result_s`
  2. `AppEvents_CL | where TimeGenerated >= ago(6h) and Result_s == "Failure" | summarize FailureCount=count() by bin(TimeGenerated, 15m)`
  3. `AppEvents_CL | summarize FailureCount=count() by bin(TimeGenerated, 15m)`
  4. `AppEvents_CL | where TimeGenerated >= ago(6h) | summarize FailureCount=count() by bin(TimeGenerated, 15m), Result_s`

Explanation

Correct Answer

B:

The `where` clause restricts both the six-hour time window and the failure status. `summarize count() by bin(TimeGenerated, 15m)` then rounds each event timestamp into a 15-minute bucket and reports only failure counts per bucket, exactly matching the dashboard requirement.

Incorrect Answers

A:

The predicates select recent failures, but grouping only by `Result_s` produces a single aggregate for the value Failure. It does not preserve the required series of 15-minute time bins.

C:

This query creates 15-minute buckets but omits the six-hour filter and includes both successes and failures. A valid time-bucket shape without the correct row predicates does not produce a failed-request trend.

D:

Grouping by status and time bucket produces separate Success and Failure rows, since the query lacks the required `Result_s == "Failure"` filter. The resulting data includes successful-request counts and therefore does not satisfy the requested failure-only output.