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 43

Question 420

A Bicep deployment runs at resource-group scope rg-app, but it must read the ID of an existing storage account stshared located in another resource group rg-data in the same subscription. What must its Bicep resource reference include?

  1. Declare the account as `existing` with the right name but omit `scope`; Bicep automatically searches all resource groups in the subscription.
  2. Declare a brand new storage account named stshared in rg-app because Bicep cannot reference an account in another resource group.
  3. Use an `if` condition on a new local resource declaration instead of setting a resource scope.
  4. Declare stshared as `existing` and set its scope explicitly to `resourceGroup('rg-data')` so its symbolic ID resolves to the other resource group.

Explanation

Correct Answer

D:

The `existing` modifier prevents redeployment, while `scope: resourceGroup('rg-data')` tells Bicep which resource group contains the referenced account. Both details matter.

Incorrect Answers

A:

Without an explicit different scope, a resource declaration resolves relative to its deployment scope. Bicep does not automatically discover resources by name across resource groups.

B:

Bicep supports a cross-resource-group existing-resource reference. Creating a second account produces the wrong identity and is unnecessary.

C:

Conditionally creating a local resource does not bind a symbol to an existing account in rg-data. The location of the existing resource must be specified.

Question 421

A release pipeline selects subscription sub-prod and runs `az deployment sub create` using `main.bicep`. The file explicitly has `targetScope = 'resourceGroup'` and declares a VM inside existing `rg-orders`; no subscription-level resources are intended. Validation reports that the deployment scope doesn't match the Bicep file. What change corrects this specific failure without changing the workload's intended scope?

  1. Keep `az deployment sub create` and add `--location eastus`; the deployment metadata location changes the Bicep file's targetScope.
  2. Keep the subscription deployment and add `scope: resourceGroup('rg-orders')` to an unrelated nested module while leaving the root Bicep file unchanged.
  3. Invoke `az deployment group create --resource-group rg-orders --template-file main.bicep` while keeping the file's resource-group target scope.
  4. Change the root file to `targetScope = 'managementGroup'`, then continue using `az deployment sub create` against sub-prod.

Explanation

Correct Answer

C:

Bicep defaults to resource-group deployment and also accepts an explicit `targetScope = 'resourceGroup'`. Use the matching `az deployment group create` command with the existing target resource group, keeping the VM resource at its intended management scope.

Incorrect Answers

A:

A subscription-level deployment requires a location for its deployment record, but adding one does not convert a `resourceGroup`-targeted root Bicep file into a subscription-scope deployment. The command and file target would still mismatch.

B:

A child module's `scope` controls that child's nested deployment, not the scope of the root Bicep invocation. The problem occurs before the pipeline can deploy the resource-group-targeted root file through a subscription command.

D:

A management-group target represents a third, different management scope. Combining it with a subscription deployment command introduces a new mismatch rather than deploying the VM to rg-orders.

Question 422

An Azure governance team needs to deploy a custom Azure Policy definition directly at management group mg-corp with Bicep or ARM. A resource-group-scope deployment currently fails because the policy definition is intended to be managed at mg-corp. What is the correct approach?

  1. Keep the deployment at resource-group scope and assume the policy definition automatically appears at the parent management group.
  2. Assign an Azure resource Reader role on an unrelated virtual machine and redeploy the same resource-group template.
  3. Deploy at the management-group scope with a valid management-group target/template schema and appropriate permissions to create the policy definition.
  4. Deploy an Azure Blob data-plane SAS token as a stand-in for a management-group policy definition.

Explanation

Correct Answer

C:

A management-group deployment (`targetScope = 'managementGroup'` for Bicep) can define Azure Policy resources at that scope with the required authorized identity.

Incorrect Answers

A:

Management-group policy definitions are extensions of their management-group scope. A regular resource-group deployment does not automatically create one at that different scope.

B:

Reader on a VM neither authorizes creation of a policy definition at a management group nor changes deployment target scope.

D:

Blob SAS authorizes selected storage data operations, not Azure Resource Manager governance definitions. It cannot replace a policy definition.

Question 423

A platform team manages subscription `sub-apps` and needs to create resource group `rg-east-payroll` declaratively. The Bicep file declares `targetScope = 'subscription'` and resource type `Microsoft.Resources/resourceGroups`; the deployment identity has suitable subscription permissions. Which Azure CLI operation should be used?

  1. Run `az deployment group create --resource-group rg-east-payroll` even though the group has not yet been created.
  2. Use `az deployment tenant create` because every new Azure resource group must be deployed at tenant scope.
  3. Change `targetScope` to `managementGroup` and deploy an unsupported resource-group declaration to the management group.
  4. Run `az deployment sub create --location eastus --template-file main.bicep` with the resource-group name/location parameters and the selected subscription.

Explanation

Correct Answer

D:

Microsoft documents `targetScope = subscription` and `az deployment sub create` for subscription resource deployments, with a deployment metadata location separate from the new group location. This matches the Bicep file and rights.

Incorrect Answers

A:

A resource-group deployment assumes a target resource group exists. It is not the correct parent scope for the Bicep resource declaration that creates a resource group.

B:

Tenant-level deployments target a different Azure resource-management scope and are unnecessary for an authorized resource group creation in one subscription.

C:

Resource-group creation is a supported subscription-scope resource. Changing the Bicep targetScope to a management group changes the resource scope and does not match this declaration.

Question 424

A release pipeline targets existing resource group rg-stage in the already selected subscription. It uses an ARM JSON template main.json and must read stage-specific values from stage.parameters.json. The CLI command already includes `az deployment group create --template-file main.json`, and the service identity has resource-group deployment permissions. Which TWO additional command arguments meet the stated requirements? Select TWO answers.

  1. `--location eastus` on an `az deployment mg create` command instead of the resource-group deployment.
  2. `--parameters stage.parameters.json` to supply the external stage-specific ARM template values.
  3. `--resource-group rg-stage` to target the intended existing resource group.
  4. `--mode Complete` to remove undeclared resources before loading the parameter values.
  5. `--template-uri` pointing to an unrelated management-group policy definition instead of local main.json.

Explanation

Correct Answers

B:

`--parameters stage.parameters.json` is the supported Azure CLI argument for passing values from the staging parameters file to an ARM JSON template. Without it, the template would use defaults or fail on required parameters instead of applying the stated stage-specific values. This is one of the two missing inputs.

C:

`--resource-group rg-stage` identifies the existing Azure resource group targeted by `az deployment group create`. The correct subscription is already selected in the scenario, but that alone does not specify the destination resource group. This is the second missing command argument.

Incorrect Answers

A:

`az deployment mg create` targets management-group scope and does not use `--location` to select an existing resource group. The question explicitly specifies a resource-group deployment using `az deployment group create`, so switching the scope and command would not deploy main.json to rg-stage.

D:

Complete deployment mode controls resource deletion behavior and is neither a means of supplying a parameter file nor a substitute for choosing the resource-group scope. The requirement does not authorize deleting undeclared production resources; a simple parameterized resource-group deployment does not require this destructive mode.

E:

`--template-uri` supplies a remotely hosted template instead of the existing local `--template-file main.json` input, and a management-group policy definition is not the requested resource-group ARM template. It does not satisfy either missing scope or staging parameter argument.

Question 425

An approved Bicep update for resource group `rg-billing` is about to enter the production release pipeline. Its new network declaration may resize a subnet, and the engineer must inspect predicted Create, Modify, and Delete effects using the exact production template and parameters before any production change occurs. What check directly provides the required preflight evidence?

  1. Inspect the last completed deployment's operation history only, assuming past operations predict every change in the new template.
  2. Run `az deployment group what-if` against rg-billing with the intended template, parameters, and deployment settings; investigate the predicted resource/property changes before deploying.
  3. Check that the updated Bicep file parses successfully, and infer that no existing resource can be modified or deleted.
  4. Execute the new deployment immediately in production and inspect the actual changes afterward to determine which resources were affected.

Explanation

Correct Answer

B:

Azure Resource Manager what-if previews the proposed changes at the actual deployment scope using the intended inputs. Its output can surface Create, Modify, Delete, Ignore, and other outcomes without applying them. Review limitations and expressions before authorizing production execution.

Incorrect Answers

A:

Deployment operation history explains what a prior execution did, not what the unreleased Bicep and current parameters would do next. The engineer needs a predictive plan for this exact production change.

C:

Syntax or template validation catches structural problems but cannot independently establish the before/after resource-property differences or deletion impact that management wants reviewed.

D:

Executing first reverses the required safety sequence. Real changes can be disruptive or irreversible; a what-if preview is the supported pre-deployment evidence, whereas deployment logs are after-the-fact.

Question 426

A governance deployment must create a new Azure management group from a Bicep file. The deployment identity already has the required tenant-level permissions, but the release job incorrectly calls `az deployment group create` and fails because the resource is tenant-scoped. Which Bicep scope and deployment command should the job use?

  1. Keep `targetScope = 'resourceGroup'` and retry `az deployment group create` against a different resource group.
  2. Set `targetScope = 'subscription'` and invoke `az deployment sub create` to create the tenant-level management group.
  3. Set `targetScope = 'tenant'` and invoke `az deployment tenant create` with a deployment location and the Bicep file.
  4. Use `az deployment group create` with a management-group ID supplied as the resource group name.

Explanation

Correct Answer

C:

Bicep supports `targetScope = 'tenant'` for supported tenant-level resources such as management groups. `az deployment tenant create` submits that template at tenant scope and requires a deployment location and suitable tenant-level authorization, which the case already provides.

Incorrect Answers

A:

Resource-group deployments cannot directly create a tenant-scoped management group. Changing only the resource group does not change the template's ARM deployment scope.

B:

Subscription-level deployments apply to supported subscription resources; a new management group is a tenant-scoped resource. The `sub create` invocation is not the required tenant deployment operation.

D:

The group deployment command still targets a resource group, regardless of the text supplied in a parameter. Passing a management-group ID cannot convert that command into a tenant deployment.

Question 427

A root Bicep deployment already succeeds in resource group `rg-platform`. One child module now needs to create a storage account in existing resource group `rg-finance` in the SAME subscription. The child module currently has no explicit `scope`, and the release identity has deployment permissions in rg-platform but none in rg-finance. Neither group needs to be recreated and the root deployment command is already correct. Which TWO changes are required? Select TWO answers.

  1. Change only the root file to `targetScope = 'subscription'` and keep the module without `scope`, expecting it to deploy automatically into rg-finance.
  2. Run the root Bicep file as a management-group deployment so the child module inherits write access to rg-finance.
  3. Authorize the deployment identity for the necessary resource deployments at rg-finance or an eligible ancestor scope, following least privilege.
  4. Pass `rg-finance` as a plain string parameter to the child while leaving its `scope` unset, assuming parameter values change a module's deployment target automatically.
  5. Set the child module's `scope` to `resourceGroup('rg-finance')` from the root file so its nested deployment targets the other group.

Explanation

Correct Answers

C:

A cross-resource-group module is executed by an identity that needs appropriate deployment rights in its destination scope. Authorization in rg-platform alone does not grant writes in a sibling rg-finance group.

E:

A module may deploy to a different resource group when its `scope` is set to the intended `resourceGroup(...)`. Together with permission in rg-finance, this directs the nested deployment to the right scope without changing the parent group's deployment.

Incorrect Answers

A:

Root `targetScope` specifies the deployment scope of the parent file. Changing it to subscription does not automatically move a module with no `scope` into the named finance resource group; it would also disturb the already working root invocation.

B:

Management-group deployment is neither the declared root scope nor an RBAC grant. It cannot substitute for a correctly scoped nested module and an authorized principal in the destination resource group.

D:

A parameter can provide the destination group name for use by `resourceGroup(...)`, but a parameter by itself does not set the module `scope`. Without that property, the module inherits its parent's target group.

Question 428

A governance deployment pipeline holds a Bicep file whose `targetScope` is `managementGroup`. Its policy initiative must be assigned to management group mg-platform and inherited by child subscriptions. The pipeline currently runs a resource-group deployment command and fails its scope validation. Which change places this deployment at the correct scope?

  1. Pass a JSON parameters file to the existing resource-group deployment and keep the current command unchanged.
  2. Change the Bicep file to `targetScope = resourceGroup` so the policy assignment automatically becomes management-group-wide.
  3. Invoke a subscription deployment for a different subscription and assume its policy assignment becomes an ancestor of mg-platform.
  4. Use a management-group-targeted Bicep deployment for mg-platform with the necessary authorization to deploy the initiative assignment.

Explanation

Correct Answer

D:

Bicep deployments to management groups use the matching deployment scope and required management-group access. Because the file explicitly targets a management group, the pipeline must invoke the management-group deployment operation with the intended group identifier and a suitable location for deployment metadata. A policy assignment at mg-platform can then apply to eligible descendants. Resource-group deployment or changing a parameter file alone cannot produce the ancestor assignment.

Incorrect Answers

A:

A parameter file supplies values to a deployment, but it does not redefine the deployment scope. A command aimed at a resource group remains at that level regardless of whether its input parameters come from a file. It cannot resolve the specified management-group targetScope mismatch.

B:

Switching targetScope to resourceGroup would change the Bicep file’s intended deployment level and cannot silently grant an assignment at the management-group ancestor. A child group deployment does not create inherited policy control over sibling subscriptions. Keep the declared scope aligned with the actual governance requirement.

C:

A subscription is below a management group in the Azure management hierarchy. Assigning policy at one subscription does not make it effective on every child subscription under mg-platform. The deployment command and resource scope need to target the common ancestor with appropriate permissions, not an arbitrary descendant.

Question 429

A Bicep template provisions storage account `payrollarchive` as `StorageV2` in West Europe. Deployment validation reports `StorageAccountAlreadyTaken`, and the account with that globally reserved name belongs to an unrelated tenant in another Azure region. The team is authorized to choose a new account name. What must change?

  1. Change only the deployment to management-group scope; the same storage account name becomes available inside the management group.
  2. Run a what-if deployment but leave `name = payrollarchive`; the name conflict will disappear when validation completes.
  3. Choose a globally unique compliant storage account name and update the Bicep/parameter input before redeployment.
  4. Run `az deployment sub create` instead of a resource-group deployment without changing the globally conflicting storage account name.

Explanation

Correct Answer

C:

The Azure Storage account DNS namespace requires global name uniqueness. Changing the name parameter to an unused compliant value resolves the specific `StorageAccountAlreadyTaken` cause.

Incorrect Answers

A:

Storage account names are globally unique across Azure; deployment scope does not make a name already owned by another tenant available.

B:

What-if is useful for inspecting prospective changes, but it does not reserve or change a globally taken storage account name.

D:

Subscription-scope CLI deployment changes where ARM applies the template but cannot override Azure Storage global account-name allocation.

Question 430

A deployment named `app-prod-081` has succeeded in resource group `rg-apps`. Its Bicep file declares `output endpointUrl string = web.properties.defaultHostName`. A downstream CI/CD stage needs that exact endpoint value, but it is not automatically available as an environment variable. Which step retrieves the declared result reliably for the downstream stage?

  1. Read only the resource-group tags, because Bicep output variables are automatically copied to `rg-apps.tags`.
  2. List all Azure VM network interfaces in the subscription and assume one contains the web app deployment output.
  3. Query `az deployment sub show` without a subscription-level deployment name, because a successful group deployment is always stored at subscription scope.
  4. Retrieve the named group deployment using `az deployment group show -g rg-apps -n app-prod-081 --query properties.outputs.endpointUrl.value`, and pass that value explicitly into the next pipeline stage.

Explanation

Correct Answer

D:

Deployment outputs are stored under `properties.outputs`, with each named output's result in its `value` member. Querying the specific successful group deployment returns endpointUrl; the pipeline must then explicitly map that value for the later stage.

Incorrect Answers

A:

Bicep output declarations produce deployment results; they are not automatically materialized as resource-group tags. Unless the template explicitly writes a tag, reading rg-apps tags does not retrieve endpointUrl.

B:

A web app default hostname is a Microsoft.Web site property exposed through the deployment output, not a VM NIC inventory field. Listing unrelated VM adapters cannot reliably supply that declared Bicep result.

C:

The execution was a resource-group deployment, and its output belongs to that named group deployment's record. A subscription deployment lookup is the wrong scope and lacks the stated resource-group deployment identity.