McAfee-Secured Website

Exam Bundle

Exam Code: AZ-104

Exam Name Microsoft Azure Administrator

Certification Provider: Microsoft

Corresponding Certification: Microsoft Certified: Azure Administrator Associate

Microsoft AZ-104 Bundle $44.99

100% Microsoft AZ-104 Guaranteed Success With Testking Training Materials

Get Real AZ-104 Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

  • Questions & Answers

    AZ-104 Questions & Answers

    606 Questions & Answers

    The ultimate exam preparation tool, Questions & Answers mirrors the actual AZ-104 exam while allowing you to hone and measure every aspect of your test-taking ability.

  • AZ-104 Video Course

    AZ-104 Video Course

    132 Video Lectures

    AZ-104 Video Course is developed by Microsoft Professionals to help you pass the AZ-104 exam.

    Description

    This course will improve your knowledge and skills required to pass Microsoft Azure Administrator exam.
  • Study Guide

    AZ-104 Study Guide

    458 PDF Pages

    Developed by industry experts, this 458-page guide spells out in painstaking detail all of the information you need to ace AZ-104 exam.

Microsoft Azure Administrator (AZ-104) Practice Tests

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Total Cost: $194.97
Bundle Price: $149.98

Purchase Individually

  • Questions & Answers

    Questions & Answers

    606 Questions

    $124.99
  • AZ-104 Video Course

    Video Course

    132 Video Lectures

    $39.99
  • Study Guide

    Study Guide

    458 PDF Pages

    $29.99

Microsoft AZ-104 Practice Test 4

Question 30

A Windows-based team uses an Azure Files SMB share. They need to restore an entire accidentally altered folder to a previously captured point in time. What storage feature should be scheduled?

  1. Use Blob versioning on the storage account as the recovery mechanism for directories in the SMB Azure Files share.
  2. Create Azure Files share snapshots and configure appropriate Azure Files backup and retention protection.
  3. Configure Blob point-in-time restore on the account and use the resulting restore-point timestamp to recover the SMB share folder.
  4. Increase the Azure Files share quota before each change and use that allocation increase as the historical folder restore point.

Explanation

Correct Answer

B:

Share snapshots capture point-in-time share states that can support file restoration. A backup policy adds managed protection and retention; snapshots alone must be governed carefully.

Incorrect Answers

A:

Blob versioning protects blob objects, not Azure Files SMB directories. Azure Files share snapshots or a suitable Azure Files backup design are needed for point-in-time directory recovery.

C:

Blob point-in-time restore does not create a point-in-time snapshot of an Azure Files share. The Blob and Azure Files protection mechanisms are distinct.

D:

A quota change expands or restricts allowed capacity but stores no earlier directory state. Create share snapshots or managed share backups before risky modifications.

Question 31

A team deploys the same Bicep template to development and production, but storage redundancy differs by environment. They want one maintained template with explicit input differences. What should they do?

  1. Use a Bicep output for the storage SKU, and each environment will override the resource property after deployment finishes.
  2. Declare the variable setting as a parameter and provide environment-specific parameter values at deployment.
  3. Hard-code the production SKU and manually edit the source before every development deployment.
  4. Store different SKU values in a resource tag and the Bicep template will automatically treat that tag as a deployment parameter.

Explanation

Correct Answer

B:

Parameters let one declarative template accept validated environment inputs without duplicating resource definitions. Production and test use the same infrastructure logic.

Incorrect Answers

A:

Outputs report deployment results; they do not provide environment-specific input values for resources. A parameter is the supported deployment input mechanism.

C:

Manual source edits promote drift and make deployments less reproducible. A parameter is designed for exactly this environment difference.

D:

Tags do not automatically supply Bicep input values. Explicit parameter files or values let the same maintained template vary by environment.

Question 32

A production deployment changes several network and storage resources. The owner wants to inspect expected additions, modifications and deletions before running the deployment. Which operation best fits?

  1. Run the appropriate ARM/Bicep deployment what-if operation and review its proposed changes.
  2. Run the full deployment in production and compare resource costs afterward.
  3. Run only Bicep build and the template linter, and these local checks identify actual Azure resource deletions before deployment.
  4. Validate the Bicep file with a template syntax check only and this returns the live proposed resource changes.

Explanation

Correct Answer

A:

What-if predicts deployment-level resource changes without immediately applying them. Some computed properties can yield noise, so the preview should be reviewed rather than treated as guaranteed execution.

Incorrect Answers

B:

That applies the changes before review and can create outages. The requirement is an advance change preview.

C:

Build and lint validate the template structure but lack the live-resource state comparison supplied by the what-if deployment operation.

D:

Validation can detect syntax or deployment errors but does not produce the current-resource change preview delivered by what-if.

Question 33

A Bicep deployment must attach a new diagnostic setting to an already existing Log Analytics workspace in the same subscription. The workspace must not be redeployed. How should the template refer to it?

  1. Declare the Log Analytics workspace as a new resource with its existing name and depend on the deployment engine to avoid all updates to it.
  2. Declare the workspace as an existing resource using the correct scope and ID so new resources can reference it without redeploying it.
  3. Create a second workspace with the same name in every deployment.
  4. Use an ARM template parameter containing the workspace display name but never resolve its existing resource ID or deployment scope.

Explanation

Correct Answer

B:

Bicep existing-resource declarations let templates use known resource identities without creating the referenced resource. Correct scope and permissions remain required.

Incorrect Answers

A:

Declaring a new managed resource can cause the deployment to manage or update that workspace, contrary to the requirement to reference it unchanged.

C:

Duplicate creation conflicts with the requirement to retain the existing workspace and may fail due to identity/scope collisions.

D:

A bare display name does not safely identify an existing resource for a scoped Bicep reference or its dependent diagnostic configuration.

Question 34

An operator built a resource group manually and now needs a reproducible infrastructure-as-code baseline. They wish to move to Bicep gradually. What is the appropriate starting point?

  1. Export the ARM template and deploy it unchanged into every environment with its original resource identifiers and parameter values.
  2. Export the existing resource group deployment as an ARM template, inspect it, then convert or refactor it into maintained Bicep modules.
  3. Export the existing group and commit the generated parameter values, including environment-specific IDs, without reviewing sensitive or nonportable settings.
  4. Recreate every resource by hand without saving a template or export.

Explanation

Correct Answer

B:

Exported templates provide a useful starting description but may include unsupported properties or environment-specific values. The admin must validate and simplify them before reuse.

Incorrect Answers

A:

An exported template is a starting point, but unreviewed identifiers and fixed settings can collide or misconfigure the next environment; refactoring and validation remain necessary.

C:

Raw exports require inspection and refactoring. Treating an unreviewed export as reusable Bicep can preserve unsuitable resource IDs, secrets or defaults.

D:

Manual recreation produces drift and does not establish a reproducible code baseline. Export and controlled refactoring are more appropriate.

Question 35

Three application teams need the same standardized monitoring configuration, while each deploys separate resources to different resource groups. How should a maintained Bicep design avoid repeating the entire monitoring definition?

  1. Extract the common monitoring configuration into a parameterized Bicep module and call it with each target resource or scope.
  2. Create three copies of the monitoring module with identical names but independently maintained logic for each team and target group.
  3. Use a Bicep module with fixed resource IDs for one application, then call it from every resource group unchanged.
  4. Duplicate the monitoring JSON by hand into three independent templates with unrelated defaults.

Explanation

Correct Answer

A:

A module packages reusable declarative infrastructure. Parameters and supported scopes let multiple deployments share consistent logic without copying full resource blocks.

Incorrect Answers

B:

Independent module copies drift and defeat reuse. A single parameterized module called at the appropriate target scope maintains consistent configuration.

C:

A hard-coded resource ID makes the module unsuitable for the separate teams and scopes; parameterized resource references are required.

D:

Manual duplicates increase configuration drift and make later fixes harder to propagate. A shared module addresses the repeated definition.

Question 36

A critical two-VM web tier must survive failure of one Azure datacenter availability zone within its region. Which placement choice provides distinct zone fault domains where available?

  1. Place VMs in separate subnets in the same selected zone and each subnet corresponds to an independent datacenter fault boundary.
  2. Put both VMs on one availability set and this always spans regional availability zones.
  3. Place the two VMs in separate proximity placement groups within one zone, and proximity groups define distinct availability zones.
  4. Deploy the VMs in different supported availability zones, and configure application failover or load balancing.

Explanation

Correct Answer

D:

Availability zones separate infrastructure locations within the region. The application also needs a suitable failover and routing design to maintain service after one zone fails.

Incorrect Answers

A:

Subnets are logical address spaces and do not give separate availability-zone physical placement.

B:

Availability sets separate fault/update domains within a datacenter infrastructure context but are not an explicit multi-zone placement choice.

C:

A proximity placement group optimizes physical closeness rather than cross-zone separation. Explicit distinct zones provide the requested zone fault boundary.

Question 37

A public API is stateless and needs additional identical VM instances during afternoon traffic peaks, then fewer instances overnight. What Azure compute arrangement fits?

  1. Create an Azure Monitor metric alert on the standalone API VM and attach an autoscale action that provisions identical Azure VMs when CPU utilization rises.
  2. Use Azure Virtual Machine Scale Sets with an autoscale rule based on a relevant workload metric.
  3. Schedule a larger VM size for afternoon demand and a smaller size overnight on the one existing VM.
  4. Place the existing VM in an Azure availability set and use its update-domain distribution to adjust the number of running copies as workload rises.

Explanation

Correct Answer

B:

VM Scale Sets can manage a pool of equivalent instances and scale out or in based on thresholds. Health and cooldown settings should prevent unstable cycling.

Incorrect Answers

A:

An Azure Monitor alert on a standalone VM does not provide the native scale-set instance orchestration needed to create and retire identical VM replicas. Use a VM Scale Set with a supported autoscale profile.

C:

Vertical resizing changes the capacity of one machine and can require restarts or deallocation; it does not supply the additional identical VM instances specifically requested for horizontal peak handling.

D:

Availability sets distribute existing machines across platform fault and update domains. Their placement metadata has no native autoscale controller for adding and removing instances.

Question 38

A legacy database VM will receive a risky operating system upgrade. The administrator wants a point-in-time copy of the managed OS disk to support recovery if the patch corrupts it. Which artifact should be created?

  1. Export the VM's ARM resource template and preserve the JSON as the rollback artifact for the operating-system disk.
  2. Turn on boot diagnostics and retain its serial output and screenshot history as the OS disk recovery artifact.
  3. Take a managed disk snapshot with the appropriate consistency planning before the upgrade.
  4. Enable a disk encryption set and complete the OS upgrade with the encryption configuration as the previous-image rollback mechanism.

Explanation

Correct Answer

C:

A disk snapshot captures a point-in-time disk state and can be used to create a recovery disk. Application-consistent backup may still be needed for transactional workloads.

Incorrect Answers

A:

An ARM export preserves resource configuration and references but not the managed OS disk blocks. It cannot recreate the previous installed OS state after an in-guest upgrade damages the disk.

B:

Serial logs and screenshots can help diagnose boot problems, but they are not block-level managed-disk recovery copies. A snapshot or suitable backup must capture the disk state.

D:

Encryption keys protect data at rest; they are not a preserved older disk image or a rollback point. A managed-disk snapshot addresses the point-in-time recovery requirement.

Question 39

A compliance team requires encryption at host for VM disk-related temporary and cache data in addition to Azure managed disk server-side encryption. Which VM setting should be considered when supported?

  1. Enable storage service encryption with a customer-managed key but leave the VM-level encryption-at-host option disabled.
  2. Enable Azure Disk Encryption for the guest OS and it encrypts Azure host temporary disks and cache at the platform layer.
  3. Enable encryption at host for the supported VM size and disks.
  4. Enable guest BitLocker alone and it encrypts Azure host-level managed disk caches outside the guest.

Explanation

Correct Answer

C:

Encryption at host addresses host-level VM data flows such as temporary disks and disk cache at rest. It is distinct from standard managed-disk storage-side encryption.

Incorrect Answers

A:

Customer-managed managed-disk encryption protects supported storage data; it does not itself enable host-layer encryption for temporary disks and caches.

B:

Guest disk encryption and encryption-at-host cover different layers and must not be treated as interchangeable.

D:

Guest-level volume encryption is not equivalent to encryption at host for the platform disk cache and temporary disk storage flows. Select encryption at host where the compliance requirement explicitly covers those layers.

Question 40

An Azure VM cannot be resized to a selected SKU while running, and the portal indicates the change requires deallocation. What is the next appropriate administrative step after scheduling downtime?

  1. Stop and deallocate the VM, resize to an available supported SKU, then start and validate it.
  2. Restart the VM from its guest operating system and retry the new SKU while leaving it allocated to the existing host.
  3. Increase the storage performance tier for the managed OS disk and the VM compute SKU automatically changes to the desired size.
  4. Apply a resource-group ReadOnly management lock and retry VM resize, and the lock will grant the required compute operation.

Explanation

Correct Answer

A:

Deallocation releases allocated compute resources and allows supported changes that cannot occur on the running host. The selected SKU must be available in the target region/cluster.

Incorrect Answers

B:

An in-guest restart does not release the VM allocation. The scenario requires Azure stop/deallocate before selecting an available size.

C:

Disk performance and VM compute size are separately configured. A VM resize may require deallocation and available capacity.

D:

ReadOnly locks block management writes and cannot make a resize succeed. The required next step is deallocation and a supported SKU.