Question 1mediummultiple choice
Read the full Deploy and Manage Compute explanation →AZ-104 Deploy and Manage Azure Compute • Complete Question Bank
Complete AZ-104 Deploy and Manage Azure Compute question bank — all 0 questions with answers and detailed explanations.
Region capabilities: - East US 2: supports Availability Zones Requirements: - Deploy two identical web server VMs - Keep the service available if one datacenter fails - Use Azure Load Balancer for traffic distribution
Drag a concept onto its matching description — or click a concept then click the description.
Starts a stopped virtual machine without changing its disks or NICs.
Stops the VM and releases the compute host, which can reduce compute charges.
Moves the VM to a new Azure host to help resolve host-level issues.
Changes the VM size, such as moving from a smaller to a larger SKU.
Drag a concept onto its matching description — or click a concept then click the description.
az vm deallocate
az vm redeploy
az vm resize
az snapshot create
az vm disk attach
Recovery notes: - VM: vm-finance-01 - Data disk: disk-finance-logs was deleted accidentally - Snapshot: snap-finance-logs-2024-11-15 exists in the same subscription - Goal: restore the disk with minimal impact to the operating system disk
Drag a concept onto its matching description — or click a concept then click the description.
Runs a script on a VM without opening inbound management ports.
Installs software or applies configuration during VM provisioning.
Lets users sign in to a VM with Entra identities.
Resets local administrator credentials or SSH configuration on a VM.
VM summary: Name: vm-web-01 Current size: Standard_D2s_v5 Average CPU over 24 hours: 91% Average memory pressure: 87% Business requirement: increase compute capacity while keeping the OS disk, installed applications, and data intact
Command output: - Azure portal shows: DataDisk01 size = 512 GiB - Inside the guest OS, the partition still shows 256 GiB used and 256 GiB unallocated - The application cannot write to the extra space yet
Provisioning requirement: - A Windows VM is created from a marketplace image - IIS must be installed automatically on first boot - Application files must be copied from Azure Blob Storage - A bootstrap script named bootstrap.ps1 must run after the VM starts - No manual RDP steps are allowed
Deployment note: - A Windows Server VM was patched, had the monitoring agent installed, and includes line-of-business software. - The VM was generalized and captured for reuse. - The team wants future VMs to start from the same approved build.
Template excerpt:
```
resources:
- type: Microsoft.ContainerInstance/containerGroups
name: cg-transform
properties:
containers:
- name: transform
properties:
image: contoso.azurecr.io/transform:3.0
imageRegistryCredentials: []
```
Requirement: the image is stored in Azure Container Registry and no username, password, or connection string may be embedded in the deploymentContainer group configuration: - Name: cg-nightly-import - Container image: contoso.azurecr.io/importer:1.2 - Job behavior: the process imports files, exits with code 0 on success, and should not run again until the next scheduled deployment - Requirement: do not restart the container after successful completion
Drag a concept onto its matching description — or click a concept then click the description.
Best for one VM; the identity is deleted with the VM.
Can be attached to multiple VMs.
Lets an app get Azure tokens without storing secrets.
Grants permissions to an Azure resource at a chosen scope.
Drag a concept onto its matching description — or click a concept then click the description.
Spreads VMs across fault and update domains within one datacenter.
Places VMs in separate datacenters within the same Azure region.
Reusable source for creating the same VM build again.
Defines CPU, memory, and temporary storage resources.
Environment notes: - Region: East US 2 - Workload: two identical web VMs behind a load balancer - Requirement: the application must keep running if one datacenter in the region becomes unavailable - Current plan: both VMs would be placed in the same availability set
Drag a concept onto its matching description — or click a concept then click the description.
Used to deploy multiple new VMs from a prepared standard build.
Used to create a new VM that keeps the source machine's existing state.
Helps protect against host or maintenance failures inside one datacenter.
Helps protect against a full datacenter outage in a region.
Requirement note: - ProductionApp must stay online during a single datacenter outage. - Region: East US 2 - The region supports multiple availability zones. - Two Windows VMs will host the app tier.
Development environment notes: - The VM is recreated frequently from an image - The OS disk contents do not need to be preserved after the VM is deallocated - The team wants the lowest practical OS disk latency - Data durability is not the top priority for this VM
Deployment requirement: 1. Create a new Windows VM from a standard image. 2. Install IIS after the VM is provisioned. 3. Run C:\Setup\install.ps1 automatically. 4. No interactive logon is allowed during deployment.
Repository plan: - The operations team deploys the same VM and networking layout every sprint - Changes must be easy to review in pull requests - The team wants a declarative Azure deployment file - Current sample file is lengthy JSON and hard to maintain
Business requirement: - Three identical web VMs in one Azure region - The service must survive a datacenter outage - The environment can use zone-aware resources - The team wants to spread the VMs across separate physical locations
Scaling requirement: - Workload is stateless - Start with 2 instances - Increase capacity when average CPU stays above 70% for 10 minutes - Decrease capacity when demand drops - All instances should run the same image and configuration
Monitoring summary: - CPU averages 18% from 00:00 to 08:00 - CPU averages 74% from 09:00 to 17:00 - CPU averages 22% after 18:00 - The application is stateless and can run on any instance
Business requirement: - Application must survive a datacenter-level outage - Azure region supports availability zones - The workload can run from multiple instances - The team wants to place instances in separate fault domains if possible
Deployment notes: - Security team published a hardened image - The image has been validated for the organization - New VMs should start from that exact image - The administrator wants a straightforward image-based deployment
Source control folder:
- /infra/main.bicep
- /infra/parameters/prod.bicepparam
- /infra/modules/vm.bicep
Snippet:
resource vm 'Microsoft.Compute/virtualMachines@2023-09-01' = {
name: vmName
location: location
}
Goal: Reuse the same definition for every sprint release.Workload notes: - Region: East US - Two application VMs will run in the same region - Requirement: survive planned host maintenance and a host failure - Requirement: no need for datacenter-level resilience
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Drag steps to the numbered slots on the right, or tap a step then tap a slot.