test11 Flashcards
HOTSPOT -
You have an Azure subscription that contains an Azure Availability Set named WEBPROD-AS-USE2 as shown in the following exhibit.
PS Azure:> az vm availability-set list -g RG1
[
{
“id”: “/subscriptions/8372f433-2dcd-4361-b5ef-5b188fed87d0/resourceGroups/
RG1/providers/Microsoft.Compute/availabilitySets/WEBPROD-AS-USE2”,
“location”: “eastus2”,
“name”: “WEBPROD-AS-USE2”,
“platformFaultDomainCount”: 2,
“platformUpdateDomainCount”: 10,
“proximityPlacementGroup”: null,
“resourceGroup”: “RG1”,
“sku”: {
},
“capacity”: null,
“name”: “Aligned”,
“tier”: null,
“statuses”: null,
“tags”: {},
“type”: “Microsoft.Compute/availabilitySets”,
“virtualMachines”: []
}
]
Azure:/
You add 14 virtual machines to WEBPROD-AS-USE2.
Use the drop-down menus to select the answer choice that completes each statement based on the information presented in the graphic.
NOTE: Each correct selection is worth one point.
Hot Area:
Answer Area
When Microsoft performs planned maintenance in East US
2, the maximum number of unavailable virtual machines will
be [answer choice].
2
7
10
14
If the server rack in the Azure datacenter that hosts
WEBPROD-AS-USE2 experiences a power failure, the
maximum number of unavailable virtual machines will be
[answer choice].
2
7
10
14
The correct answers are:
For planned maintenance: 2 virtual machines
For power failure (fault domain): 7 virtual machines
Here’s why:
For Planned Maintenance:
The Availability Set has platformUpdateDomainCount = 10
With 14 VMs distributed across 10 update domains
VMs are distributed as evenly as possible across update domains
14 VMs ÷ 10 update domains ≈ 1.4 VMs per update domain
This means each update domain will have 1-2 VMs
During planned maintenance, Microsoft updates one update domain at a time
Therefore, maximum 2 VMs can be unavailable during planned maintenance
For Power Failure:
The Availability Set has platformFaultDomainCount = 2
Fault domains represent different physical hardware/rack infrastructure
14 VMs distributed across 2 fault domains
14 VMs ÷ 2 fault domains = 7 VMs per fault domain
If a rack (fault domain) experiences power failure
Therefore, maximum 7 VMs can be unavailable during a rack failure
Existing Environment
Contoso has an Azure subscription named Sub1 that is linked to an Azure Active Directory (Azure AD)
tenant. The network contains an on-premises Active Directory domain that syncs to the Azure AD
tenant.
The Azure AD tenant contains the users shown in the following table.
Name Type Role
User1 Member None
User2 Guest None
User3 Member None
User4 Member None
Sub1 contains two resource groups named RG1 and RG2 and the virtual networks shown in the
follow
Name Subnet Peered with
VNET1 Subnet1, Subnet2 VNET2
VNET2 Subnet1 VNET1, VNET3
VNET3 Subnet1 VNET2
VNET4 Subnet1 None
ing table.
User1 manages the resources in RG1. User4 manages the resources in RG2.
Sub1 contains virtual machines that run Windows Server 2019 as shown
https://www.certification-questions.com
Microsoft AZ-104
Name IP address Location Connected to
VM1 10.0.1.4 West US VNET1/Subnet1
VM2 10.0.2.4 West US VNET1/Subnet2
VM3 172.16.1.4 Central US VNET2/Subnet1
VM4 192.168.1.4 West US VNET3/Subnet1
VM5 10.0.22.4 East US VNET4/Subnet1
in the following table
No network security groups (NSGs) are associated to the network interfaces or the subnets.
Sub1 contains the storage accounts shown in the following table.
Name Kind Location File share Identity-access for
storage1 Storage (general purpose v1) West US sharea Azure Active Domain Ser (Azure AD D
storage2 StorageV2 (general purpose v2) East US shareb, sharec Disabled
storage3 BlobStorage East US 2 Not applicable Not applicable
storage4 FileStorage Central US shared Azure Active Domain Ser (Azure AD D
Requirements
Planned Changes
Contoso plans to implement the following changes:
Create a blob container named container1 and a file share named share1 that will use the Cool storage tier.
Create a storage account named storage5 and configure storage replication for the Blob service.
Create an NSG named NSG1 that will have the custom inbound security rules shown in the follow
Priority Port Protocol Source Destination
500 3389 TCP 10.0.2.0/24 Any
1000 Any ICMP Any Virtual Network
ing
table.
Associate NSG1 to the network interface of VM1.
Create an NSG named NSG2 that will have the custom outbound security rules shown
Priority Port Protocol Source Destination Action
200 3389 TCP 10.0.0.0/16 Virtual Network Deny
400 Any ICMP 10.0.2.0/24 10.0.1.0/24 Allow
n the
following table.
Associate NSG2 to VNET1/Subnet2.
Technical Requirements
Contoso must meet the following technical requirements:
Create container1 and share1.
Use the principle of least privilege.
Create an Azure AD security group named Group4.
Back up the Azure file shares and virtual machines by using Azure Backup.
Trigger an alert if VM1 or VM2 has less than 20 GB of free space on volume C.
Enable User1 to create Azure policy definitions and User2 to assign Azure policies to RG1.
Create an internal Basic Azure Load Balancer named LB1 and connect the load balancer to
VNET1/Subnet1
Enable flow logging for IP traffic from VM5 and retain the flow logs for a period of eight months.
Whenever possible, grant Group4 Azure role-based access control (Azure RBAC) read-only
permissions to the Azure file shares.
HOTSPOT -
You need to configure Azure Backup to back up the file shares and virtual machines.
What is the minimum number of Recovery Services vaults and backup policies you should create? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Hot Area:
Answer Area
Recovery Services vaults
1
2
3
4
7
Backup policies
1
2
3
4
5
6
For this scenario, the correct answers are:
Recovery Services vaults: 3
Backup policies: 3 [1]
Here’s why:
Recovery Services Vaults (3 needed):
Based on the locations of resources that need backup:
West US (VM1, VM2)
Central US (VM3, storage4/shared)
East US (storage2/shareb, sharec)
Recovery Services vaults must be in the same region as the resources they protect. You cannot back up resources from one region to a vault in another region.
Backup Policies (3 needed):
You need different backup policies for:
Azure VMs (one policy)
Azure Files in StorageV2 accounts (one policy for storage2 shares)
Azure Files in FileStorage accounts (one policy for storage4 share)
The reason for 3 policies:
Different resource types (VMs vs. File Shares) require different backup policies
Different storage account kinds (StorageV2 vs. FileStorage) may have different backup requirements
All VMs can share the same backup policy since they have similar requirements
This configuration:
Meets the technical requirement to “Back up the Azure file shares and virtual machines using Azure Backup”
Follows best practices for regional data residency
Provides appropriate separation of backup policies for different resource types
Is the minimum required number while still meeting all requirements
You have an Azure virtual machine named VM1.
You use Azure Backup to create a backup of VM1 named Backup1.
After creating Backup1, you perform the following changes to VM1:
✑ Modify the size of VM1.
✑ Copy a file named Budget.xls to a folder named Data.
✑ Reset the password for the built-in administrator account.
✑ Add a data disk to VM1.
An administrator uses the Replace existing option to restore VM1 from Backup1.
You need to ensure that all the changes to VM1 are restored.
Which change should you perform again?
A. Modify the size of VM1.
B. Reset the password for the built-in administrator account.
C. Add a data disk.
D. Copy Budget.xls to Data.
D. Copy Budget.xls to Data.
Reasoning:
When you restore an Azure virtual machine using the Replace existing option in Azure Backup, the following applies:
VM Size Changes:
The VM size is automatically restored to the size it had at the time of the backup. Any subsequent size changes will be lost after restoration.
Why incorrect: Since the VM size is restored, you don’t need to manually reapply the size change.
Built-in Administrator Password Reset:
Azure Backup does not capture OS-level settings like password resets for the built-in administrator account. However, after the restore, you can use Azure VM access reset tools if needed.
Why incorrect: This change is not stored in the backup, but Azure tools can reset it later.
Data Disk Addition:
Additional disks attached to a VM after the backup are not included. You would need to reattach them manually after restoration.
Why incorrect: The question asks specifically about changes to VM1. Attaching a new data disk is external to the VM’s original backup configuration.
File Copying (Correct Answer):
Azure VM backups capture the contents of the OS and data disks present during the backup. Files added after the backup are not included.
Why correct: Since Budget.xls was copied after the backup, it will not be restored and must be manually copied again.
Key Takeaways:
Azure Backup captures: VM configuration, OS disk, and attached data disks at the time of backup.
Not captured: Password resets, files added after the backup, and data disks attached later.
You have an Azure subscription that contains an Azure Backup vault named Backup1, a Recovery Services vault named Recovery1, and the resources shown in the
following table.
You plan to back up the resources.
Which resource can be backed up to Backup1, and which resource can be backed up to Recovery1? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Answer Area
Backup1:
App1
DB1
Disk1
VM1
Recovery1:
App1
DB1
Disk1
VM1
Name | Type |
|—|—|
| VM1 | Virtual machine |
| Disk1 | Disk |
| App1 | Azure App Service web app |
| DB1 | Azure SQL Database |
For this scenario, the correct selections for each vault are:
Backup1 (Azure Backup vault):
VM1
Recovery1 (Recovery Services vault):
DB1
Let me explain why these are the single best answers for each vault:
For Backup1 (Azure Backup vault):
VM1 is the best choice because:
Azure Backup vault is optimized for VM backups
It provides better performance for VM backups
It’s the newer, recommended solution for VM protection
While Disk1 can also be backed up here, VM backup includes the disks automatically
For Recovery1 (Recovery Services vault):
DB1 is the best choice because:
Azure SQL Database can ONLY be backed up to Recovery Services vault
It’s the traditional and proven solution for database workloads
SQL Database backup is a core functionality of Recovery Services vault
Why other options are not the best choice:
App1 (App Service) has its own native backup functionality
Disk1 is better protected as part of VM backup
While VM1 can be backed up to Recovery Services vault, Azure Backup vault is the newer, recommended solution
This answer focuses on the most appropriate and optimized choice for each vault type, considering:
Best practices
Microsoft recommendations
Optimal performance
Specific workload requirements
You have a Recovery Service vault that you use to test backups. The test backups contain two protected virtual machines.
You need to delete the Recovery Services vault.
What should you do first?
A. From the Recovery Service vault, delete the backup data.
B. Modify the disaster recovery properties of each virtual machine.
C. Modify the locks of each virtual machine.
D. From the Recovery Service vault, stop the backup of each backup item.
D. From the Recovery Service vault, stop the backup of each backup item.
To delete an Azure Recovery Services vault, you must first remove all dependencies. This includes stopping backup for each backup item (protected VM or other resources) and deleting backup data if needed.
Stop Backup of Each Backup Item:
Before deleting the vault, you must stop the backup of each item in the Recovery Services vault. This action removes the association between the VMs and the vault.
Why Not the Other Options?
A. Delete the backup data:
This is only allowed after stopping the backup. You cannot delete backup data while backups are still enabled.
B. Modify the disaster recovery properties of each VM:
Disaster recovery properties are unrelated to the deletion of the Recovery Services vault.
C. Modify the locks of each VM:
VM locks are related to preventing deletion or changes at the VM level, not to the vault itself.
You have an Azure subscription that has a Recovery Services vault named Vault1. The subscription contains the virtual machines shown in the following table:
Name Operating system Auto-shutdown
VM1 Windows Server 2012 R2 Off
VM2 Windows Server 2016 19:00
VM3 Ubuntu Server 18.04 LTS Off
VM4 Windows 10 19:00
You plan to schedule backups to occur every night at 23:00.
Which virtual machines can you back up by using Azure Backup?
A. VM1 and VM3 only
B. VM1, VM2, VM3 and VM4
C. VM1 and VM2 only
D. VM1 only
B. VM1, VM2, VM3 and VM4
Overview -
ADatum Corporation is consulting firm that has a main office in Montreal and branch offices in Seattle and New York.
Existing Environment -
Azure Environment -
ADatum has an Azure subscription that contains three resource groups named RG1, RG2, and RG3.
The subscription contains the storage accounts shown in the following table.
|—|—|—|—|—|—|
| storage1 | StorageV2 | West US | Yes | cont1 | share1 |
| storage2 | StorageV2 | West US | No | cont2 | share2 |
The subscription contains the virtual machines shown in the following table.
The subscription has an Azure container registry that contains the images shown in the following table.
| Name | Operating system |
|—|—|
| Image1 | Windows Server |
| Image2 | Linux |
The subscription contains the resources shown in the following table.
| Name | Description | In resource group |
|—|—|—|
| Workspace1 | Log Analytics workspace | RG1 |
| WebApp1 | Azure App Service web app | RG1 |
| VNet1 | Virtual network | RG2 |
| zone1.com | Azure Private DNS zone | RG3 |
Azure Key Vault -
The subscription contains an Azure key vault named Vault1.
Vault1 contains the certificates shown in the following table.
| Name | Content type | Key type | Key size |
|—|—|—|—|
| Cert1 | PKCS#12 | RSA | 2048 |
| Cert2 | PKCS#12 | RSA | 4096 |
| Cert3 | PEM | RSA | 2048 |
| Cert4 | PEM | RSA | 4096 |
Vault1 contains the keys shown in the following table.
| Name | Type | Description |
|—|—|—|
| Key1 | RSA | Has a key size of 4096 |
| Key2 | EC | Has Elliptic curve name set to P-256 |
Microsoft Entra Environment -
ADatum has a Microsoft Entra tenant named adatum.com that is linked to the Azure subscription and contains the users shown in the following table.
Name Microsoft Entra role Azure role
Admin1 Global Administrator None
Admin2 Attribute Definition Administrator None
Admin3 Attribute Assignment Administrator None
User1 None Reader for RG2 and RG3
The tenant contains the groups shown in the following table.
Name Type
Group1 Security group
Group2 Microsoft 365 group
The adatum.com tenant has a custom security attribute named Attribute1.
Planned Changes -
ADatum plans to implement the following changes:
- Configure a data collection rule (DCR) named DCR1 to collect only system events that have an event ID of 4648 from VM2 and VM4.
- In storage1, create a new container named cont2 that has the following access policies: o Three stored access policies named Stored1, Stored2, and Stored3 o A legal hold for immutable blob storage
- Whenever possible, use directories to organize storage account content.
- Grant User1 the permissions required to link Zone1 to VNet1.
- Assign Attribute1 to supported adatum.com resources.
- In storage2, create an encryption scope named Scope1.
- Deploy new containers by using Image1 or Image2.
Technical Requirements -
ADatum must meet the following technical requirements:
- Use TLS for WebApp1.
- Follow the principle of least privilege.
- Grant permissions at the required scope only.
- Ensure that Scope1 is used to encrypt storage services.
- Use Azure Backup to back up cont1 and share1 as frequently as possible.
- Whenever possible, use Azure Disk Encryption and a key encryption key (KEK) to encrypt the virtual machines.
You need to configure Azure Backup to meet the technical requirements for cont1 and share1.
To what should you set the backup frequency for each resource? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Answer area:
cont1 <answer>
Every hour
Every 4 hours
Every 6 hours
Every 12 hours
Daily</answer>
share1 <answer>
Every hour
Every 4 hours
Every 6 hours
Every 12 hours
Daily</answer>
Name | Size | Operating system | Description |
|—|—|—|—|
| VM1 | A | Red Hat Enterprise Linux (RHEL) | Uses ephemeral OS disks |
| VM2 | D | Windows Server 2022 | Has a basic volume |
| VM3 | B | Red Hat Enterprise Linux (RHEL) | Uses a standard SSDs |
| VM4 | M | Windows Server 2022 | Uses Write Accelerator disks |
| VM5 | E | Windows Server 2022 | Has a dynamic volume |
For this scenario, the correct backup frequencies are: [1]
cont1: Every 4 hours
share1: Daily
Here’s why:
For cont1 (Container):
Azure Backup for blob containers supports backup frequency as frequent as every 4 hours
The requirement states “as frequently as possible”
Therefore, Every 4 hours is the most frequent option available for blob containers
This provides the best possible RPO (Recovery Point Objective) for blob storage
For share1 (File Share):
Azure File Share backup only supports daily backup frequency
Even though the requirement asks for “as frequently as possible”
Daily is the only available option for Azure File Shares
This is a platform limitation for Azure File Share backups
Key considerations:
Platform limitations:
Blob containers: Minimum interval is 4 hours
File shares: Only supports daily backups
Technical requirements state:
“Use Azure Backup to back up cont1 and share1 as frequently as possible”
Must work within the platform limitations
Must be supported by Azure Backup service
Best practices:
Choose the most frequent backup option available for each resource type [2]
Consider the recovery point objectives (RPO)
Work within service limitations
Therefore, selecting “Every 4 hours” for cont1 and “Daily” for share1 represents the most frequent possible backup schedule while staying within Azure Backup service limitations.
You have a Recovery Service vault that you use to test backups. The test backups contain two protected virtual machines.
You need to delete the Recovery Services vault.
What should you do first?
A. From the Recovery Service vault, delete the backup data.
B. Modify the disaster recovery properties of each virtual machine.
C. Modify the locks of each virtual machine.
D. From the Recovery Service vault, stop the backup of each backup item.
The correct answer is D: From the Recovery Service vault, stop the backup of each backup item.
Here’s why this is the correct first step to delete a Recovery Services vault: [1]
Required Sequence to Delete a Recovery Services Vault:
Step 1: Stop backup for all protected items (This is option D)
Step 2: Delete the backup data/recovery points
Step 3: Delete the vault
Copy
Insert at cursor
plaintext
Why Option D is Correct:
You must first stop protection for all backup items
This removes the backup policy association
This is a prerequisite before you can delete backup data
This ensures a controlled decommissioning of backup protection
Important Notes:
You cannot delete a vault that contains protected items
Stopping backup is a prerequisite for all other deletion steps
This is a safety measure to prevent accidental data loss
The process must be done in the correct order
Therefore, option D is the correct first step as it’s the necessary prerequisite for deleting a Recovery Services vault.
You purchase a new Azure subscription named Subscription1.
You create a virtual machine named VM1 in Subscription1. VM1 is not protected by Azure Backup.
You need to protect VM1 by using Azure Backup. Backups must be created at 01:00 and stored for 30 days.
What should you do? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Answer Area
Location in which to store the backups:
A blob container
A file share
A Recovery Services vault
A storage account
Object to use to configure the protection for VM1:
A backup policy
A batch job
A batch schedule
A recovery plan
Location to store the backups:
A Recovery Services vault
Object to use to configure the protection for VM1:
A backup policy
Why correct:
Purpose-built for Azure Backup
Provides secure storage for backups
Supports VM backup natively
Includes built-in management features
Handles retention policies automatically
Object - Backup policy:
Why correct:
Defines backup schedule (01:00)
Sets retention period (30 days)
Can be applied to multiple VMs
Manages backup consistency
Handles automated backups
Why other options are incorrect:
Location options:
Blob container: Not designed for VM backups
File share: Cannot store VM backups
Storage account: No built-in backup management
Object options:
Batch job: For compute operations, not backup
Batch schedule: Not related to backup
Recovery plan: For disaster recovery scenarios
The combination of Recovery Services vault and backup policy provides: [2]
Proper storage location for backups
Scheduling capability (01:00)
Retention management (30 days)
Built-in security and management
Compliance with Azure Backup best practices
You have an Azure subscription that contains a virtual machine named VM1. You need to back up VM1. The solution must ensure that backups are stored across three availability zones in the primary region.
Question: Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.
Actions:
Configure a replication policy.
Set Replication to Zone-redundant storage (ZRS).
For VM1, create a backup policy and configure the backup.
Set Replication to Locally-redundant storage (LRS).
Create a Recovery Services vault.
Answer Area:
Answer Area:
Action 1: Create a Recovery Services vault.
Action 2: Set Replication to Zone-redundant storage (ZRS).
Action 3: For VM1, create a backup policy and configure the backup.
Explanation:
Create a Recovery Services vault: The first step is always to create a Recovery Services vault, which is required to manage the backup and restore operations for Azure resources, including virtual machines.
Set Replication to Zone-redundant storage (ZRS): To meet the requirement of ensuring backups are stored across three availability zones, you should configure the replication type to Zone-redundant storage (ZRS). This ensures the backup data is replicated across multiple zones in the primary region.
For VM1, create a backup policy and configure the backup: After setting up the vault and replication settings, the final step is to configure a backup policy for VM1, which includes defining the backup schedule and retention policy.
You have an Azure subscription that contains the resources shown in the following table.
Name Type Resource group Location
Vault1 Recovery services vault RG1 East US
VM1 Virtual machine RG1 East US
VM2 Virtual machine RG1 West US
All virtual machines run Windows Server 2016.
On VM1, you back up a folder named Folder1 as shown in the following exhibit.
Schedule Backup Wizard
Specify Backup Schedule (Files and Folders)
Getting started Define a schedule when you want to create a backup copy for
Select Items to Backup selected files and folders
Specify Backup Schedu… Schedule a backup every
Select Retention Policy… * Day ○ Week
Choose Initial Backup T…
Confirmation
Modify Backup Progress
At following times (Maximum allowed is three times a day)
6:00 AM 10:00 PM None
You plan to restore the backup to a different virtual machine.
You need to restore the backup to VM2.
What should you do first?
A. From VM1, install the Windows Server Backup feature.
B. From VM2, install the Microsoft Azure Recovery Services Agent.
C. From VM1, install the Microsoft Azure Recovery Services Agent.
D. From VM2, install the Windows Server Backup feature.
The correct answer is B. From VM2, install the Microsoft Azure Recovery Services Agent.
Explanation:
To restore a backup from Azure Recovery Services Vault to a different virtual machine (in this case, VM2), you need to have the Microsoft Azure Recovery Services Agent installed on the target virtual machine (VM2). This agent is responsible for communicating with the Recovery Services Vault and managing the restore process.
Here’s a brief overview of why the other options are not correct:
A. From VM1, install the Windows Server Backup feature.
This option is not relevant because the Windows Server Backup feature is not needed on VM1 for restoring backups to VM2.
C. From VM1, install the Microsoft Azure Recovery Services Agent.
This option is also incorrect because installing the agent on VM1 does not help in restoring the backup to VM2. The agent needs to be on the machine where the restore is taking place.
D. From VM2, install the Windows Server Backup feature.
While having Windows Server Backup can be useful for local backups, it is not necessary for restoring from Azure Recovery Services Vault. The Azure Recovery Services Agent is required instead.
You have an Azure subscription that contains a virtual machine name VM1.
VM1 has an operating system disk named Disk1 and a data disk named Disk2.
You need to back up Disk2 by using Azure Backup.
Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct
order.
Select and Place:
Actions
Configure a managed identity
Create an Azure Backup vault
Create a Recovery Services vault
Delegate permissions for the vault
Create a backup policy and configure the backup
Answer Area
Create a Recovery Services vault
Create a backup policy and configure the backup
Configure a managed identity
Explanation:
1. Create a Recovery Services vault:
This is the first step because the Recovery Services vault is required to store the backup data. You need to create this vault before you can perform any backup operations
2. Create a backup policy and configure the backup:
Once the vault is set up and permissions are delegated, you can create a backup policy that defines how and when the backups will occur. This policy is essential for configuring the backup of Disk2.
Your company has an Azure subscription that includes a Recovery Services vault.
You want to use Azure Backup to schedule a backup of your company’s virtual machines (VMs) to the Recovery Services vault.
Which of the following VMs can you back up? Choose all that apply.
A. VMs that run Windows 10.
B. VMs that run Windows Server 2012 or higher.
C. VMs that have NOT been shut down.
D. VMs that run Debian 8.2+.
E. VMs that have been shut down.
The correct options for VMs that can be backed up using Azure Backup are:
Correct Answers:
B. VMs that run Windows Server 2012 or higher.
D. VMs that run Debian 8.2+.
C. VMs that have NOT been shut down.
E. VMs that have been shut down.
Explanation:
B. VMs that run Windows Server 2012 or higher:
Azure Backup supports backing up Windows Server operating systems starting from Windows Server 2012 and later versions (e.g., 2016, 2019, 2022). This option is valid.
D. VMs that run Debian 8.2+:
Azure Backup also supports backing up certain Linux distributions, including Debian 8.2 and later versions. Therefore, this option is valid as well.
C. VMs that have NOT been shut down:
Azure Backup can back up VMs whether they are running or stopped. Therefore, this option is valid because it indicates that VMs can be backed up while they are running.
E. VMs that have been shut down:
Azure Backup can also back up VMs that are stopped (shut down). This option is valid as well, as it indicates that VMs can be backed up regardless of their power state.
Incorrect Answer:
A. VMs that run Windows 10:
Azure Backup does not support backing up Windows 10 VMs. It is primarily designed for server operating systems, not client operating systems like Windows 10.
Summary:
The valid options for VMs that can be backed up using Azure Backup are those running Windows Server 2012 or higher, those running Debian 8.2 or later, and VMs that can be in either running or stopped states.
HOTSPOT -
You have an Azure subscription named Subscription1 that contains a resource group named RG1.
In RG1, you create an internal load balancer named LB1 and a public load balancer named LB2.
You need to ensure that an administrator named Admin1 can manage LB1 and LB2. The solution must follow the principle of least privilege.
Which role should you assign to Admin1 for each task? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Hot Area:
Answer Area
To add a backend pool to LB1:
Contributor on LB1
Network Contributor on LB1
Network Contributor on RG1
Owner on LB1
To add a health probe to LB2:
Contributor on LB2
Network Contributor on LB2
Network Contributor on RG1
Owner on LB2
To ensure that Admin1 can manage the internal load balancer (LB1) and the public load balancer (LB2) while following the principle of least privilege, we need to assign the most appropriate roles for each task.
Answer Area
1. To add a backend pool to LB1:
Correct Option: Network Contributor on LB1
Reason: The Network Contributor role allows the user to manage network resources, including load balancers, without granting full access to the resource group or the ability to delete the load balancer. This is the least privilege required to add a backend pool specifically to LB1.
To add a health probe to LB2:
Correct Option: Network Contributor on LB2
Reason: Similar to LB1, the Network Contributor role on LB2 allows Admin1 to manage the health probes and other network-related settings for the public load balancer without giving broader permissions that are not necessary for this task.
You have an Azure Active Directory (Azure AD) tenant named contoso.com that contains the users shown in the following table:
User3 is the owner of Group1.
Group2 is a member of Group1.
You configure an access review named Review1 as shown in the following exhibit:
Create an access review
Access reviews enable reviewers to attest user’s membership in a group or access to an application.
* Review name Review1
Description
* Start date 2018-11-22
Frequency One time
Duration (in days)
End Never End by Occurrence
Number of times 0
* End date 2018-12-22
Users
Users to review Members of a group
Scope Guest users only
Everyone
* Group Group1
Reviewers
Reviewers Group owners
Programs
Link to program
Default program
Upon completion settings
Advanced settings
For each of the following statements, select Yes if the statement is true. Otherwise, select No.
NOTE: Each correct selection is worth one point.
Hot Area:
Answer Area
Statements
User3 can perform an access review of User1? yes/no
User3 can perform an access review of UserA ? yes/no
User3 can perform an access review of UserB? yes/no
Name | Type | Member of |
|—|—|—|
| User1 | Member | Group1 |
| User2 | Guest | Group1 |
| User3 | Member | None |
| UserA | Member | Group2 |
| UserB | Guest | Group2 |
To determine whether User3 can perform an access review of the specified users, we need to consider the roles and group memberships in the context of the access review configuration.
Access Review Configuration:
Review Name: Review1
Group: Group1
Scope: Guest users only
Reviewers: Group owners (User3 is the owner of Group1)
Answer Area
1. User3 can perform an access review of User1?
Answer: No
Reason: User1 is a member of Group1, but the access review is scoped to “Guest users only.” Since User1 is not a guest user, User3 cannot perform an access review on User1.
2. User3 can perform an access review of UserA?
Answer: No
Reason: UserA is a member of Group2, which is a member of Group1. However, UserA is not a guest user, and the access review is limited to guest users only. Therefore, User3 cannot perform an access review on UserA.
3. User3 can perform an access review of UserB?
Answer: Yes
Reason: UserB is a guest user and is a member of Group2, which is part of Group1. Since the access review is scoped to guest users, User3 can perform an access review on UserB.
Summary of Correct Selections:
User3 can perform an access review of User1? No
User3 can perform an access review of UserA? No
User3 can perform an access review of UserB? Yes
You have an Azure subscription named Subscription1 that contains the resources shown in the following table.
In storage1, you create a blob container named blob1 and a file share named share1.
Which resources can be backed up to Vault1 and Vault2? To answer, select the appropriate options in the answer area
NOTE: Each correct selection is worth one point.
Hot Area:
Answer Area
Can use Vault1 for backups:
VM1 only
VM1 and share1 only
VM1 and SQL1 only
VM1, storage1, and SQL1 only
VM1, blob1, share1, and SQL1
Can use Vault2 for backups:
storage1 only
share1 only
VM1 and share1 only
blob1 and share1 only
storage1 and SQL1 only
which option is correct in per question on answer area? why correct?
Name | Type | Location | Resource group |
|—|—|—|—|
| RG1 | Resource group | West US | Not applicable |
| RG2 | Resource group | West US | Not applicable |
| Vault1 | Recovery Services vault | Central US | RG1 |
| Vault2 | Recovery Services vault | West US | RG2 |
| VM1 | Virtual machine | Central US | RG2 |
| storage1 | Storage account | West US | RG1 |
| SQL1 | Azure SQL database | East US | RG2 |
Correct Answers:
Can use Vault1 for backups:
VM1 only
Can use Vault2 for backups:
share1 only
Explanation:
Understanding Recovery Services Vaults:
A Recovery Services vault in Azure is used for backing up supported workloads such as:
Virtual Machines (VMs)
Azure File Shares
Azure SQL databases
Backups are location-specific, meaning the Recovery Services vault must be in the same region as the resource being backed up.
Resources:
Vault1
Location: Central US
Eligible Resources for Backup: Only resources in Central US can be backed up to Vault1.
From the table:
VM1: Central US → Eligible for backup.
storage1 and its containers (blob1 and share1): Located in West US → Not eligible.
SQL1: Located in East US → Not eligible.
Therefore, only VM1 can use Vault1.
Vault2
Location: West US
Eligible Resources for Backup: Only resources in West US can be backed up to Vault2.
From the table:
storage1: West US → Can back up the Azure File Share (share1) but not blob storage because Azure Backup does not back up blob storage.
share1: Located in storage1 (West US) → Eligible.
VM1: Central US → Not eligible for Vault2 (region mismatch).
SQL1: East US → Not eligible.
Therefore, share1 only and VM1 are valid. Thus, the correct choice is share1.
You have an Azure subscription.
You plan to migrate 50 virtual machines from VMware vSphere to the subscription.
You create a Recovery Services vault.
What should you do next?
A. Configure an extended network.
B. Create a recovery plan.
C. Deploy an Open Virtualization Application (OVA) template to vSphere.
D. Configure a virtual network.
which option is correct? why?
To migrate virtual machines from VMware vSphere to an Azure subscription using a Recovery Services vault, the next step after creating the vault is to ensure that the virtual machines can communicate with Azure and are properly configured for migration.
Correct Option:
D. Configure a virtual network.
Explanation:
1. Configure a Virtual Network: Before migrating virtual machines to Azure, you need to set up a virtual network in Azure. This virtual network will provide the necessary network infrastructure for the migrated VMs to communicate with each other and with other Azure resources. It is essential to have a virtual network configured to ensure that the VMs can be properly integrated into the Azure environment.
Other Options:
A. Configure an extended network: This step is typically part of the migration process but is not the immediate next step after creating a Recovery Services vault.
B. Create a recovery plan: This is relevant for disaster recovery scenarios and is not the first step in the migration process.
C. Deploy an Open Virtualization Application (OVA) template to vSphere: This option is not applicable in the context of migrating VMs to Azure. OVA templates are used for packaging and distributing virtual appliances, not for migrating to Azure.
HOTSPOT -
You have an Azure App Service app named WebApp1 that contains two folders named Folder1 and Folder2.
You need to configure a daily backup of WebApp1. The solution must ensure that Folder2 is excluded from the backup.
What should you create first, and what should you use to exclude Folder2? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Hot Area:
Answer Area
First create:
A Backup vault
A Recovery Services vault
A resource group
To exclude Folder2, use:
An Azure Storage account
A_backup.filter file
A backup policy
A lock
A WebJob
To configure a daily backup of an Azure App Service app (WebApp1) while excluding a specific folder (Folder2), you need to consider the Azure services and features available for backup and exclusion.
Answer Area:
First create:
A Recovery Services vault
To exclude Folder2, use:
A_backup.filter file
Explanation:
1. First create: A Recovery Services vault
Reason: A Recovery Services vault is specifically designed for managing backups and recovery of Azure resources, including Azure App Services. It provides the necessary infrastructure to configure and manage backups for your app. A Backup vault is typically used for virtual machines and other resources, but for App Services, the Recovery Services vault is the correct choice.
To exclude Folder2, use: A_backup.filter file
Reason: The _backup.filter file is used to specify which files or folders should be included or excluded from the backup process. By creating this file and placing it in the root of your app’s directory, you can define the exclusion of Folder2 from the backup. This is the standard method for excluding specific content in Azure App Service backups.
Summary:
First create: A Recovery Services vault to manage the backup of WebApp1.
To exclude Folder2: Use A_backup.filter file to specify the exclusion of that folder from the backup process.