Design identity, governance, and monitoring solutions →hardMultiple Choice

AZ-305 Practice Question: Design identity, governance, and monitoring solutions

Exhibit

{
  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentParameters.json#",
  "contentVersion": "1.0.0.0",
  "parameters": {
    "workspaceName": {
      "value": "LAW-CorpProd"
    },
    "sku": {
      "value": "PerGB2018"
    },
    "retentionInDays": {
      "value": 365
    },
    "dailyQuotaGb": {
      "value": 100
    }
  }
}

Refer to the exhibit. You are deploying a Log Analytics workspace using an ARM template with the parameters shown. Your compliance team requires that all log data be retained for at least 2 years. Which parameter value should you modify?

⚠ Common exam trap

Many candidates confuse `sku` with retention capabilities, assuming that upgrading the SKU automatically extends retention, when in fact `retentionInDays` is an independent parameter that must be explicitly set to meet compliance requirements.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

retentionInDays

The `retentionInDays` parameter controls how long log data is retained in a Log Analytics workspace. To meet the compliance requirement of at least 2 years (730 days), you must set this value to 730 or higher. The default retention is 30 days for free tiers and up to 730 days for paid tiers, but the parameter must be explicitly modified to enforce the 2-year retention.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✓
retentionInDays
Why this is correct
In Azure Log Analytics, retentionInDays is the workspace-level property that determines exactly how many days log data is retained before being purged from the storage layer. The current setting of 365 fails the 2-year requirement, so this value must be set to 730 or higher. This is the only property that directly controls the retention period; no other workspace setting can extend it.
✗
workspaceName
Why it's wrong here
workspaceName is a user-defined, globally unique identifier for the Log Analytics workspace, used for addressing in ARM templates, REST APIs, and the Azure portal. It is purely a label and has no bearing on storage behavior or data lifecycle. Changing the name does not alter retention because retention is enforced by the retentionInDays property, independent of the workspace's resource metadata.
✗
sku
Why it's wrong here
sku represents the pricing tier (e.g., PerGB2018, Capacity Reservation) and determines the billing structure and certain feature limits, but it does not govern how long data is kept. All SKUs respect the same workspace-level retentionInDays setting; upgrading or changing the SKU does not automatically increase retention to 2 years. Only the numeric retention property can meet the compliance requirement.
✗
dailyQuotaGb
Why it's wrong here
dailyQuotaGb is the daily ingestion cap that stops data collection once the configured volume is reached, helping control cost. It does not affect historical data or the retention window; even if the quota is raised or removed, data will still be purged after the existing retentionInDays value. Therefore, adjusting dailyQuotaGb has no impact on satisfying the 2-year retention mandate.

Go deeper

AZ-305 Practice Question: Design identity, governance, and monitoring solutions

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question