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 41

Question 400

An ARM deployment must add tags to each generated resource. Which administrative action most directly meets the requirement?

  1. Add the plan resource and correct dependency or resource ID reference.
  2. Add validated resource naming and length constraints to the template inputs before redeployment.
  3. Modify the resource tags property rather than unrelated template metadata.
  4. Fix the expression/parameter identity instead of supplying duplicate shadow parameters.

Explanation

Correct Answer

C:

Azure resource tags are properties on the actual resource declarations, not the deployment's general metadata. Add the required name/value pairs to each eligible resource's tags object, using parameters or variables where consistent values are needed. Validate the resulting template before deployment and account for resource types with different tagging support.

Incorrect Answers

A:

A hosting-plan dependency or resource ID reference controls which service resource a web app consumes. It does not populate the Azure resource tags of all resources emitted by this ARM template, so changing it would leave the tagging requirement unmet.

B:

Resource-name length validation prevents failed deployments caused by provider naming rules. It does not attach Owner, Environment or other tags to generated resources. The template needs explicit tags fields on the deployed resource definitions.

D:

Fixing a misspelled ARM parameter reference removes expression-evaluation errors. It does not create or assign the requested resource tags, so it is an unrelated change unless the tag expressions themselves have a verified reference error.

Question 401

An ARM deployment fails because a newly added resource has an invalid name length. Which Azure configuration or procedure is the best fit?

  1. Add the plan resource and correct dependency or resource ID reference.
  2. Add validated resource naming and length constraints to the template inputs before redeployment.
  3. Modify the resource tags property rather than unrelated template metadata.
  4. Use parameter files to vary supported SKU values while retaining one template.

Explanation

Correct Answer

B:

Validate the resource provider's name rules and adjust the template parameter, concatenation expression or naming convention that produces the overlong value. Then validate or run what-if with actual deployment inputs before redeploying. The resulting name must satisfy the provider's character, uniqueness and length restrictions; changing tags or dependency order cannot bypass those rules.

Incorrect Answers

A:

Adding a hosting-plan resource or dependency addresses an unresolved or missing resource relationship. The error here explicitly concerns the length of a resource name. An unrelated new dependency will not cause an invalid resource name to satisfy the service provider's naming constraints.

C:

Resource tags affect metadata and cost/governance organization; they do not shorten the underlying ARM resource name. Updating tags without correcting the deployment's name expression leaves the validation error unchanged.

D:

Parameter files are useful for changing supported SKU values without duplicating the template. A different SKU does not necessarily change an invalid resource-name length, so this operation is not the root fix for the reported naming failure.

Question 402

An ARM parameter currently uses a plaintext default password. What should the administrator do to resolve this specific case?

  1. Add a location parameter and reference it consistently from affected resources.
  2. Evaluate deployment mode/stack semantics before adopting deletion behavior, preserving existing resources.
  3. Fix the expression/parameter identity instead of supplying duplicate shadow parameters.
  4. Convert it to a secure parameter and supply the secret outside source control.

Explanation

Correct Answer

D:

Declare the credential input with an appropriate secureString/secureObject parameter type and supply the value through a protected deployment channel, such as a Key Vault-backed reference or secure parameter input. Do not commit the password as a default, echo it through outputs or place it in verbose deployment logs. Validate that the consuming resource property uses the secure value without exposing it.

Incorrect Answers

A:

A location parameter allows infrastructure templates to deploy the same resources in more than one region. It does not protect the existing plaintext password default, which can still be exposed through source control or template content.

B:

Selecting deployment-stack or incremental semantics determines which resources can be removed during a deployment. It has no effect on whether a hard-coded password is exposed in the ARM parameter definition.

C:

Correcting a misspelled parameter expression can make template evaluation succeed. It does not turn a plaintext password into a confidential input, so the credential would still be improperly stored or shared.

Question 403

An ARM template currently deploys 12 managed disks, but the architecture specifies exactly three. The disk resource uses a `copy` loop whose count parameter was incorrectly set to 12. What is the necessary template correction before redeployment?

  1. Correct the copy loop's count/expression and unique resource naming.
  2. Add the plan resource and correct dependency or resource ID reference.
  3. Add validated resource naming and length constraints to the template inputs before redeployment.
  4. Replace the new-VNet resource relationship with an existing-resource reference and proper scope.

Explanation

Correct Answer

A:

The `copy.count` expression determines how many instances of this resource ARM deploys. Correct the count parameter to three and use a `copyIndex()`-based distinct disk name so the three iterations create unique resources rather than an accidental duplicate name. This directly fixes both the number and identities of the disks.

Incorrect Answers

B:

An App Service plan dependency and resource ID relate to deploying web applications, not to ARM disk resource iteration. Adding a web plan cannot change the `copy.count` expression that is explicitly producing twelve disks. The disk loop would still deploy twelve iterations.

C:

Name-length validation can prevent an invalid name, but it does not control the count of disk instances. Even if every disk name satisfies the naming rules, a `copy` loop configured for twelve iterations still tries to create twelve disks rather than three.

D:

An `existing` VNet reference prevents redeploying a network resource but does not change iteration on a separate Microsoft.Compute/disks definition. The overdeployment is caused by the disk loop count, not by whether a virtual network is already present.

Question 404

An ARM JSON template conditionally deploys storage account st-archive only when Boolean parameter `deployRegionalStorage` is true. In a test deployment the flag is false, st-archive does not exist, but the template still fails: its unconditional output `primaryBlobEndpoint` calls `reference(resourceId(...))` for that absent account. The output must be an empty string when no account is deployed and the real Blob endpoint otherwise. Which template edit fixes this failure without deploying the optional account?

  1. Add `dependsOn` from the output to the omitted storage account; a dependency causes the `reference()` to return an empty string after the false condition.
  2. Replace `reference()` with `resourceId()` in the output and label the resource ID as the Blob endpoint; resource IDs and Blob HTTPS endpoints have the same meaning.
  3. Switch to complete deployment mode and leave `reference()` unconditional; complete mode automatically generates mock values for omitted resources.
  4. Wrap the output in an ARM `if(deployRegionalStorage, reference(...).primaryEndpoints.blob, '')` expression so the false branch does not evaluate the missing-resource `reference()` call.

Explanation

Correct Answer

D:

ARM template if() evaluates only the selected branch. When deployRegionalStorage is false, the output becomes the required empty string without executing reference() against a nonexistent storage account. When true, the existing reference expression can return primaryEndpoints.blob after the resource deployment completes. This is a runtime-output guard, distinct from the resource condition itself.

Incorrect Answers

A:

Dependencies govern the ordering of deployed resources; they cannot make a runtime reference to a nonexistent resource succeed. ARM evaluates reference() even when the target resource itself is conditionally skipped, unless the expression is also guarded. An output cannot derive a Blob endpoint from a missing object merely by adding a dependsOn relationship.

B:

resourceId() constructs an ARM management-plane identifier such as a /subscriptions/.../storageAccounts path. It does not return a Blob service HTTPS endpoint and cannot meet the output contract. Moreover, this would hide the failed runtime reference instead of returning the requested empty value under the false condition.

C:

Complete-mode deployments do not synthesize values for missing resources. They can even remove an existing resource omitted by a false condition under modern API versions. The observed error is an unconditional reference evaluation; changing deletion semantics neither provides a real Blob endpoint nor safely guards the output.

Question 405

An ARM template creates web app app-billing but fails because its `serverFarmId` points to a hosting plan that the template never provisions. No eligible plan already exists in the target resource group, and the deployment must create both resources. Which TWO template corrections are required? Select TWO answers.

  1. Add a validation decorator to a storage account naming parameter unrelated to app-billing.
  2. Add a new virtual network to the template but leave the App Service hosting-plan ID unresolved.
  3. Declare the required Microsoft.Web/serverfarms hosting-plan resource with supported SKU, region and name.
  4. Make app-billing reference that hosting-plan resource through the correct serverFarmId and dependency relationship.
  5. Remove the web app resource entirely and preserve only its deployment outputs.

Explanation

Correct Answers

C:

Microsoft.Web/serverfarms represents the App Service plan that provides compute capacity for the web app. Because no appropriate plan exists, the deployment must declare one with a supported region, SKU and naming configuration. Creating only the site cannot satisfy the plan dependency under the stated constraints. The declaration also permits validation of the plan’s resource ID and location compatibility before the web app is created.

D:

The web app’s serverFarmId must resolve to the actual plan resource, not an undeclared or mismatched identifier. A supported ARM resourceId expression or reference to the plan declaration allows the site to join the newly created plan. The deployment must also respect ordering or inferred dependencies as appropriate for the template. This is a separate necessary correction from adding the plan itself: without the correct reference, the site remains unbound or fails validation.

Incorrect Answers

A:

Resource naming validation can be valuable in ARM templates, but this failure concerns a missing Microsoft.Web/serverfarms plan and a broken reference from the site. Changing unrelated storage constraints neither provisions the plan nor repairs the web app’s required hosting-plan ID.

B:

A virtual network resource may serve web app connectivity in a different design, but it is not a substitute for an App Service plan. Adding the network object leaves serverFarmId pointing at a nonexistent target. The template still cannot provision the required site hosting infrastructure.

E:

Deleting the app declaration might make a smaller template deploy, but it would not deliver the required app-billing workload. The project explicitly requires creating both the plan and the site. Removing the dependent resource is evasion rather than correction of its hosting infrastructure.

Question 406

An ARM template has already been configured to deploy at the intended subscription scope. Before the pipeline actually writes resources, operations requires a read-only preview of additions, modifications, and deletions in that exact subscription. Which option produces the requested preview?

  1. Use parameter files to vary supported SKU values while retaining one template.
  2. Replace the new-VNet resource relationship with an existing-resource reference and proper scope.
  3. Run template validation and what-if against the exact deployment scope.
  4. Add a location parameter and reference it consistently from affected resources.

Explanation

Correct Answer

C:

An ARM deployment `what-if` invoked at subscription scope compares the template with the current state and displays planned Create, Modify, Delete, and other effects without writing them. Validation checks template correctness, and selecting the exact subscription for `az deployment sub what-if` targets the intended scope.

Incorrect Answers

A:

Changing SKU values through parameter files changes what resources might be deployed; it is not a read-only forecast of changes to the existing subscription. It might unintentionally alter the proposed deployment rather than report its consequences.

B:

Declaring an `existing` VNet avoids creating that particular VNet, but this request concerns all proposed resource operations at subscription scope. A VNet reference gives no complete report of adds, modifies, and deletes across the template.

D:

Location parameters make resources reusable across supported Azure regions; they do not show which existing subscription resources would be changed. The requested operation must be a preview against live state, not merely a different location supplied for deployment.

Question 407

An ARM JSON template declares a parameter named `vmSize` but a resource expression calls `parameters('vmsizee')`, causing template validation to report an undefined parameter. Which edit fixes the actual failure without introducing redundant configuration?

  1. Fix the expression/parameter identity instead of supplying duplicate shadow parameters.
  2. Modify the resource tags property rather than unrelated template metadata.
  3. Use parameter files to vary supported SKU values while retaining one template.
  4. Correct the copy loop's count/expression and unique resource naming.

Explanation

Correct Answer

A:

ARM parameter expressions must reference a declared parameter. Change the expression to `parameters('vmSize')`, matching the declaration, and revalidate. Creating a second similarly named parameter would hide the typo and introduce two configuration sources rather than fixing the invalid reference.

Incorrect Answers

B:

Resource tags are metadata on deployed resources; changing them does not supply the missing parameter declaration referenced by `parameters('vmsizee')`. Validation will still fail to resolve the expression despite changes to tags.

C:

A parameter file can provide a value for the declared `vmSize` input, but it cannot make an undeclared `vmsizee` reference valid inside the template. Correcting the reference is necessary even if different environments supply different VM sizes.

D:

A `copy` loop changes how many resources are iterated and often their unique names. This scenario reports one unresolved parameter identifier during validation; modifying the loop would not repair the misspelled parameter function call.

Question 408

A new application environment needs different SKU values across stages. Which change addresses the stated situation most precisely?

  1. Run template validation and what-if against the exact deployment scope.
  2. Use parameter files to vary supported SKU values while retaining one template.
  3. Add validated resource naming and length constraints to the template inputs before redeployment.
  4. Fix the expression/parameter identity instead of supplying duplicate shadow parameters.

Explanation

Correct Answer

B:

Keeping the ARM/Bicep template constant while supplying environment-specific parameter files selects supported SKU values at deployment time. This avoids maintaining divergent resource definitions for development, test and production while allowing each environment to use an appropriate SKU.

Incorrect Answers

A:

What-if previews deployment changes and validation catches errors; neither supplies the different SKU values that each environment must pass as parameters.

C:

Validating resource naming prevents provider name-length errors, not differences in SKU selection between environments.

D:

Correcting parameter references fixes an undefined-name deployment error; it doesn't choose an environment-specific SKU.

Question 409

A redeployment unexpectedly attempts to remove resources under an obsolete complete-mode process. What is the most appropriate next administrative decision?

  1. Convert it to a secure parameter and supply the secret outside source control.
  2. Evaluate deployment mode/stack semantics before adopting deletion behavior, preserving existing resources.
  3. Replace the new-VNet resource relationship with an existing-resource reference and proper scope.
  4. Run what-if, then execute the same complete-mode deployment even though it forecasts unintended deletions.

Explanation

Correct Answer

B:

Complete-mode ARM deployments can delete resource-group resources not present in the template. For redeployments that should preserve resources, use incremental mode, inspect what-if output and migrate intentional delete management to deployment stacks where appropriate. Do not accept a destructive complete-mode run simply because the old procedure used it.

Incorrect Answers

A:

Secure parameters prevent exposure of credentials in source control or deployment history. They do not control whether ARM deletes resources missing from a template, which is the risk reported in the redeployment.

C:

Referencing an existing VNet avoids creating a duplicate network resource; it does not determine whether other resource-group objects are deleted by an ARM deployment mode. The choice of deletion semantics is independent of that resource reference.

D:

Validation and the what-if operation are essential safeguards because they preview intended changes, including deletions. However, invoking them alone does not change a destructive complete-mode deployment into a preserving incremental run or a managed deployment stack. Review the resulting plan and explicitly correct deployment behavior before execution.

Question 410

A Bicep file hardcodes a storage name and conflicts across environments. Which administrative action most directly meets the requirement?

  1. Define a shared tags object or parameter and reference it in each resource declaration.
  2. Parameterize the prefix and use supported uniqueString input for a deterministic unique name.
  3. Use a supported @allowed decorator or union type and validate supplied input.
  4. Use a loop with unique names and conditional constraints rather than copy-pasted blocks.

Explanation

Correct Answer

B:

Azure Storage account names must be globally unique and obey naming rules. A Bicep prefix parameter lets each deployment supply its environment value, while uniqueString on stable scope inputs creates a reproducible suffix; hardcoding one account name would collide across deployments.

Incorrect Answers

A:

A shared tags object centralizes resource labels but cannot substitute for the deployment logic, type constraint or scoped reference this case needs.

C:

A Bicep `@allowed` decorator or string-literal union constrains what values a parameter may accept. It doesn't stop a storage account's globally unique name from colliding across deployments. Make the account name depend on appropriate deployment-specific values and check the storage naming rules; restricting unrelated environment labels does not create uniqueness.

D:

A resource loop generates multiple declarations; it does not by itself establish the parameter, conditional or scoped behavior required here.