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 18

Question 170

A finance analyst needs monthly Azure spending grouped by Project tags across eligible resources. How should the team prepare the tagging data for Cost Management?

  1. Rely exclusively on the current VM names as the Project cost dimension.
  2. Assign subscription Owner to every finance analyst.
  3. Standardize Project tag names and values on resources, then group or filter costs by the supported tag dimensions.
  4. Disable tags and use a CanNotDelete lock for billing classification.

Explanation

Correct Answer

C:

Azure Cost Management can use resource tag metadata for supported cost allocation and grouping. To obtain meaningful project totals, administrators should standardize the Project tag key, define consistent allowed values, and apply those values to cost-accruing resources. They must also account for services that do not emit all tag dimensions in billing data and use supported cost inheritance features where appropriate. Grouping by a reliable Project tag is more meaningful than inferring project ownership from arbitrary VM display names.

Incorrect Answers

A:

VM names do not consistently represent project ownership across different Azure resource families or shared workloads. Cost reports may also include disks, networking, and services without matching naming conventions. Standardized Project tags and supported Cost Management grouping provide a more systematic metadata-based cost classification.

B:

Azure RBAC Owner grants broad infrastructure and access management permissions, not a standardized project cost dimension. It would create unnecessary privilege while leaving inconsistent tags unresolved. Finance needs permitted cost-report access and reliable resource metadata, which should be managed separately from subscription ownership.

D:

Management locks protect control-plane resource operations and do not provide a Project dimension for cost allocation. Removing tags would make the desired grouping harder, not easier. Standardize and retain relevant resource tags, then use supported Cost Management reporting views and filters.

Question 171

Different teams supply the same Azure tag key as CostCenter and costcenter, and some tag values also have inconsistent capitalization. Which governance action reduces reporting ambiguity?

  1. Assign Reader to every tagged resource so the values become case-insensitive.
  2. Normalize the tag key casing and enforce consistent value conventions, noting that tag keys are case-insensitive but values are case-sensitive.
  3. Treat CostCenter and costcenter as independent access-control tags by design.
  4. Convert every resource into a new subscription to normalize tag capitalization.

Explanation

Correct Answer

B:

Azure treats tag names as case-insensitive for operations, though resource providers can preserve the supplied key casing in reporting. Tag values are case-sensitive, so values such as Finance and finance may be treated differently in grouping. A standardized naming and value policy prevents confusing visual differences and inconsistent cost reporting. Administrators should normalize tags on existing resources and enforce the convention in templates or suitable governance policies instead of assuming spelling variants intentionally define separate categories.

Incorrect Answers

A:

Reader controls which resources a principal can view; it does not alter Azure tag comparison or value semantics. Tag values remain case-sensitive regardless of read privileges. Use a consistent value standard and policy or deployment validation rather than modifying user access to fix reporting discrepancies.

C:

Azure tag keys are case-insensitive for operations; differing capitalization is not a reliable strategy for independent tag identities. Treating spellings as separate business controls would create misleading reports. A consistent canonical key spelling and stable value convention are needed for trustworthy cost classification and resource queries.

D:

Subscription boundaries do not automatically rewrite resource tag names or values. Moving workloads to new subscriptions is disruptive and does not establish a canonical tagging convention. The correct change is to standardize and enforce tag metadata on the relevant resources through authorized tagging workflows.

Question 172

A DevOps team proposes storing a production API password in an Azure resource tag named ApiSecret for convenience. What should the security reviewer recommend?

  1. Store the password in the tag and apply a CanNotDelete lock.
  2. Put the password into the resource-group name instead of a tag.
  3. Store the password in the tag but use a mixed-case tag key.
  4. Keep the password in an approved secrets store such as Key Vault, not in plain-text Azure tags.

Explanation

Correct Answer

D:

Azure resource tags are metadata and can appear in API responses, templates, deployment history, monitoring output, and cost reports. They are not a secure secrets-storage mechanism. A production API password should be protected in a dedicated secret service such as Azure Key Vault, accessed through narrowly scoped identities and audited authorization. The application can reference the secret through approved configuration methods instead of copying sensitive values into resource tag metadata that many resource readers may inspect.

Incorrect Answers

A:

A CanNotDelete lock restricts some Azure resource deletions, but it does not conceal tag values from authorized readers or encrypt resource metadata. The API password would remain exposed through places that surface tags. Use Key Vault or an equivalent approved secret store and appropriate role-based access controls.

B:

Azure resource-group names are visible identifiers and are even less suitable for storing confidential values. A resource name can appear in logs, URLs, billing records, and inventories. The sensitive credential should remain in a dedicated secret management service, not in tags or other management metadata.

C:

Changing a tag's capitalization does not encrypt its value or prevent it from being returned through Azure management APIs and reporting. Azure tag names are case-insensitive for many operations, and tag values remain metadata. A secret requires a credential-protection service, not an obscure spelling of its label.

Question 173

A VM deployment receives an Azure Policy denial because its Environment tag uses a value outside the approved catalog. The deploying principal already has Contributor. What should be changed?

  1. Assign Storage Blob Data Contributor to the principal.
  2. Use an approved Environment value or have governance correct an erroneous policy parameter through authorization.
  3. Grant Owner to the deployment identity.
  4. Change a VM's availability zone without touching its tag.

Explanation

Correct Answer

B:

An Azure Policy tag-value standard evaluates resource metadata independently from the deploying user's resource-management role. Contributor permission to create the VM does not override a matching deny effect. The developer should select a permitted Environment value or request an authorized correction if the assigned allowed-value list is wrong. This preserves the policy's purpose of consistent tagging while allowing compliant deployments. Increasing the user's Azure RBAC role would not address the noncompliant value.

Incorrect Answers

A:

Storage Blob Data Contributor governs blob data read, write, and delete operations, not deployment-time Azure Policy evaluation of VM metadata. Granting it would expose unrelated data permissions while leaving the tag standard unmet. The policy conflict must be resolved at the resource tag or governance assignment level.

C:

Azure subscription Owner provides broad resource and role-assignment privileges but does not cancel Azure Policy deny evaluation. The deployment fails because the tag value violates the allowed catalog, not because the principal lacks an ARM write action. Correct the tag or the authorized policy parameter rather than escalating access.

D:

Availability zones determine placement within an Azure region and do not change the Environment tag that the policy evaluated. The same unsupported tag value would still violate the assignment. The appropriate remediation is to supply a permitted tag or address the policy's configured allowed values.

Question 174

An application reads tags from an Azure resource-group object and assumes those values always match the tags on each VM in that group. The values differ. What should the application do?

  1. Rename the resource group to match the VM's tag value.
  2. Treat resource-group tags as proof that every contained VM has the same tags.
  3. Change the application's RBAC role from Reader to Owner.
  4. Query the tags on the actual VM resources or apply an explicit tag-inheritance policy; group tags are separate.

Explanation

Correct Answer

D:

Azure resource groups and their contained resources maintain separate tag sets. An application reading a group's Environment or CostCenter values is retrieving metadata for the management container, not necessarily the same fields on each VM. To report per-resource classification accurately, query the VM's own tags or enforce a supported inherited-tag policy and verify remediation. Do not assume that tagging a resource group automatically changes all existing or future child-resource metadata.

Incorrect Answers

A:

A resource-group name is a management identifier, not the source of resource tag inheritance. Renaming groups is not a direct supported operation, and even a different group name would not update child tags automatically. Query the appropriate tags or enforce an explicit tagging policy to obtain consistent metadata.

B:

Azure does not automatically propagate resource-group tags to resources. A VM can have different tags or no tag at all without implying that its group metadata is invalid. The application should query the resource object whose classification it needs instead of assuming tags match across the hierarchy.

C:

Increasing privileges does not make separate resource and resource-group tag collections become identical. The application is reading the wrong metadata object for a per-VM assertion. Correct its query or configure policy-based tag inheritance rather than granting powerful subscription or resource-management rights.

Question 175

A governance team wants to detect resources missing an Owner tag and report their noncompliance while permitting new deployments during a pilot. Which policy effect should it use?

  1. Audit, with a condition that checks for the Owner tag on eligible resources.
  2. Modify, so all existing Owner tags are deleted.
  3. Deny, so missing tags always block deployments.
  4. Create an Azure resource management lock on every untagged VM.

Explanation

Correct Answer

A:

An Azure Policy definition using the audit effect can evaluate resource metadata and record noncompliance when a required Owner tag is absent, without automatically preventing the deployment from completing. During a pilot, this lets the governance team assess the scale of missing tags and prioritize follow-up work. The rule must target supported resource types and use correct aliases or tag-field expressions. The team can later decide whether to enforce a deny or modify approach based on the reported results.

Incorrect Answers

B:

A modify effect can change supported properties or tags when authorized and correctly configured. Deleting tag values is not the intended pilot outcome, and automatically editing resources exceeds the observation-only requirement. Audit is appropriate for identifying omissions before the organization decides how to remediate them.

C:

A deny effect would reject matching noncompliant resource create or update requests, which conflicts with the explicit requirement to keep deployments running during the pilot. The team wants observational compliance findings first. Audit supplies those findings without introducing the preventive behavior of a deny policy.

D:

Management locks prevent selected control-plane modifications or deletions, not evaluate the presence of an Owner tag or report compliance centrally. Locking missing-tag resources would create unrelated operational restrictions. An Azure Policy audit rule directly tests the metadata condition and supports compliance reporting.

Question 176

An ARM/Bicep template deploys a new VM for several teams. Every deployment must set the team's CostCenter and Environment tags without manual portal editing. Which template pattern is appropriate?

  1. Set only the resource group's tags and assume the VM inherits them.
  2. Use a ReadOnly lock on the VM after deployment instead of defining tags.
  3. Define the tag values as template parameters and assign them to the VM resource's tags property.
  4. Grant Owner to the deployment pipeline and leave tag values undefined.

Explanation

Correct Answer

C:

ARM and Bicep support declaring resource tags in infrastructure-as-code definitions. Exposing CostCenter and Environment as validated deployment parameters makes the values explicit and repeatable for each team. Applying those parameters to the VM's tags property ensures the resource receives the intended metadata during provisioning. Azure Policy can provide an additional compliance safeguard, but resource-group tags alone do not automatically flow down. The team should verify the targeted resource type supports tags and that parameter defaults do not leak sensitive data.

Incorrect Answers

A:

Azure resources do not automatically inherit tags from the containing resource group. A template that tags only the group may leave the newly created VM untagged, failing the requirement. The VM resource declaration must include the intended tags or a supported Azure Policy inheritance mechanism must be explicitly configured.

B:

A management lock can restrict subsequent ARM changes, but it does not populate CostCenter or Environment metadata at deployment time. The requirement concerns repeatable resource classification across teams. Parameterized tag properties in the template address that directly, while a lock would solve a separate resource-protection problem.

D:

Owner controls deployment and role-administration permissions but does not invent correct CostCenter or Environment tags for a template. Without the tag properties or a governance policy, the deployed VM can remain unclassified. Use explicit resource tag parameters rather than relying on broad deployment privileges.

Question 177

A web API and its worker service are deployed and retired together, and the same operations group needs common access to both. How should these resources be organized in Azure?

  1. Create a separate subscription for each application process.
  2. Assign Owner separately on every resource and avoid resource groups.
  3. Place the related resources in a resource group aligned with their shared lifecycle and assign scoped RBAC.
  4. Use one storage account container to hold the API and worker resources.

Explanation

Correct Answer

C:

An Azure resource group is a management container for resources that can share deployment, monitoring, access, and lifecycle operations. When the API and worker are maintained and retired together, grouping them can simplify scoped RBAC assignment and coordinated administration. The team can apply a suitable role to the group rather than duplicating grants for each resource. Resources that have a different lifecycle or special service dependencies need not be forced into the same group simply because they communicate with the application.

Incorrect Answers

A:

Subscriptions provide a broader billing and management boundary than is necessary for two tightly coupled resources with one lifecycle. Splitting each process into a different subscription would complicate routine operations and access management. A common resource group is the natural Azure container for this shared application lifecycle when no stronger boundary is required.

B:

Azure resources normally reside in a management hierarchy that includes resource groups. Per-resource Owner grants are broader than the shared operations team needs and require duplicated access administration. Assign an appropriate scoped role on the common resource group instead of granting unnecessary ownership on every component.

D:

Blob containers hold storage objects rather than act as Azure Resource Manager management containers for arbitrary App Service or compute resources. They cannot provide the general resource-group RBAC and deployment lifecycle boundary requested here. Use an Azure resource group to organize the API and worker infrastructure.

Question 178

A team wants to move an existing VM and its dependent NIC into a new resource group without rebuilding the workload. What should the engineer do before starting the move?

  1. Delete the VM and NIC so the empty resource group can be moved.
  2. Validate the resource types' move support, required dependencies, locks, permissions, and target group.
  3. Change the VM's region while moving its resource-group metadata.
  4. Move the NIC first, regardless of VM and subnet dependencies.

Explanation

Correct Answer

B:

Azure Resource Manager supports moves for eligible resource types, but dependencies and provider-specific restrictions determine which collections can move together. A VM and its associated networking resources may require coordinated planning, and the source and target scopes must satisfy the move prerequisites. Use Azure's move validation process, inspect resource locks and permissions, and update any external references to changed resource IDs afterward. Do not assume all VM attachments and services are independently movable without impact.

Incorrect Answers

A:

Destroying the workload would violate the requirement to preserve existing infrastructure and is not necessary for eligible ARM resource moves. Resource groups themselves are not simply relocated as single cross-subscription objects in every scenario. Validate and move supported resources into the desired target group while maintaining data and dependent configurations.

C:

A move between resource groups does not, by itself, relocate a resource's physical Azure region. Region migration requires a separate supported service or migration workflow. The business request is for a management-grouping change while retaining the workload, so first validate the resource and dependency move rather than add an unrelated geographic migration.

D:

Moving a dependent network interface alone may not be supported for the proposed combination, and it can disrupt a VM's resource references. Azure move support and dependency rules must be validated as a unit. The correct sequence is to check the provider's supported move scenario and include dependent resources as required.

Question 179

A resource group is located in West Europe for metadata operations. The team must deploy an Azure VM in East US into that group. Which statement is correct?

  1. The VM can use East US if the resource supports it; the resource group's own location does not force member resource regions.
  2. Move the resource group to East US before deploying the VM.
  3. Create the VM only in West Europe, then use Reader to switch its region.
  4. Every resource must be created in the same region as the resource group.

Explanation

Correct Answer

A:

Azure resource groups have a location used for storing resource-group metadata and handling management operations. Individual resources also have their own supported deployment locations, which can differ from the group's metadata location. A VM can therefore be placed in East US within a resource group whose location is West Europe, assuming service and policy constraints allow that placement. The engineer should evaluate workload latency, residency rules, dependencies, and allowed Azure regions separately rather than infer VM region from the group's location.

Incorrect Answers

B:

The group does not need its metadata location changed to host a supported VM in a different region. Resource-group location is not a universal placement constraint on member resources. The administrator should simply deploy the VM with the permitted East US location, after checking policy and required service availability.

C:

Reader provides resource visibility rather than region-migration capability. Azure does not change a VM's physical region merely by changing its role assignment or by pointing to a different resource-group location. The team can choose East US at VM provisioning if the required resource type and policies support it.

D:

A resource group's location does not generally determine the physical region of all contained services. Azure resource types can carry their own location field and may be deployed elsewhere when supported. The VM's requested East US placement should be evaluated using the VM resource's region and governance constraints, not the group's metadata location.

Question 180

An operations manager asks to move a resource group itself, with all its contents, into a different Azure subscription as a single resource. What is the supported Azure Resource Manager approach?

  1. Use the Move command on the resource-group object without examining its resources.
  2. Create or select a target resource group and move eligible contained resources to it after validating dependencies.
  3. Grant Reader at the destination subscription and assume the entire group moves automatically.
  4. Rename the source resource group to the target subscription ID.

Explanation

Correct Answer

B:

Azure Resource Manager does not support moving a resource-group container itself into another subscription as an atomic object. Instead, an administrator can move supported resources from the original group into an existing or newly created target group in the destination subscription, subject to same-tenant, service, identity, lock, and dependency constraints. Resource IDs change where the subscription or group segment changes, and source group settings such as tags and RBAC assignments are not simply carried over. Plan and verify those details before executing the move.

Incorrect Answers

A:

Resource-group containers do not have a universal cross-subscription move operation equivalent to moving eligible resources. The contents must be validated and moved to a destination group through the supported resource move workflow. Ignoring move restrictions and dependencies risks failures and broken references after the attempted management change.

C:

Azure RBAC Reader changes management visibility but does not move resources or resource groups. Cross-subscription changes require explicit resource-move operations and checks, not simply assigning a role. Create the target group, verify tenant and provider support, and move the eligible contained resources through the supported workflow.

D:

Changing a group name cannot relocate it between subscriptions, and Azure resource groups cannot be directly renamed. The subscription is part of the hierarchical resource identifier. To change ownership of supported resources, select a target group in the destination subscription and perform a validated resource move.