Action 1: Create an Azure Logic App

Action 2: Create an Azure Event Grid Trigger

Action 3: Create conditions and actions

Correct Answer:

Reference:
https://docs.microsoft.com/en-us/azure/event-grid/monitor-virtual-machine-changes-event-grid-logic-app

Comment: *

Name: *

Email: *

Verification: *

You have an Azure subscription that contains an Azure file share.
You have an on-premises server named Server1 that runs Windows Server 2016.
You plan to set up Azure File Sync between Server1 and the Azure file share.
You need to prepare the subscription for the planned Azure File Sync.
Which two actions should you perform in the Azure subscription? To answer, drag the appropriate actions to the correct targets. Each action may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.

Correct Answer:

Explanation
As per the official MS doc:
The recommended steps to onboard on Azure File Sync for the first with zero downtime while preserving full file fidelity and access control list (ACL) are as follows:
1. Deploy a Storage Sync Service. --> This needs to be done on Azure .
2. Create a sync group. --> This needs to be done on Azure
3. Install Azure File Sync agent on the server with the full data set. --> This needs to be done on server1.
4. Register that server and create a server endpoint on the share. --> This needs to be done on server1.
5. Let sync do the full upload to the Azure file share (cloud endpoint).
6. After the initial upload is complete, install Azure File Sync agent on each of the remaining servers.
7. Create new file shares on each of the remaining servers.
8. Create server endpoints on new file shares with cloud tiering policy, if desired. (This step requires additional storage to be available for the initial setup.)
9. Let Azure File Sync agent do a rapid restore of the full namespace without the actual data transfer. After the full namespace sync, sync engine will fill the local disk space based on the cloud tiering policy for the server endpoint.
10. Ensure sync completes and test your topology as desired.
11. Redirect users and applications to this new share.
12. You can optionally delete any duplicate shares on the servers.

First action: Create a Storage Sync Service
The deployment of Azure File Sync starts with placing a Storage Sync Service resource into a resource group of your selected subscription.

Second action: Create a sync group
A sync group defines the sync topology for a set of files. Endpoints within a sync group are kept in sync with each other. A sync group must contain one cloud endpoint, which represents an Azure file share and one or more server endpoints. A server endpoint represents a path on a registered server. A server can have server endpoints in multiple sync groups. You can create as many sync groups as you need to appropriately describe your desired sync topology.

Third action: Run Server Registration
Registering your Windows Server with a Storage Sync Service establishes a trust relationship between your server (or cluster) and the Storage Sync Service. A server can only be registered to one Storage Sync Service and can sync with other servers and Azure file shares associated with the same Storage Sync Service. ) Reference:
https://docs.microsoft.com/en-us/azure/storage/files/storage-sync-files-deployment-guide?tabs=azure-portal

Comment: *

Name: *

Email: *

Verification: *

You have an Azure subscription that contains a resource group named RG1.
You need to prevent administrators from inadvertently modifying the resources in RG1.
How should you complete the PowerShell command? To answer, select the options in the answer area.
NOTE: Each correct answer is worth one point.

Correct Answer:

Explanation:

Azure provides resource locks to prevent accidental changes or deletion of critical resources. This is a core governance feature covered in the Microsoft Azure Administrator (AZ-104) study materials under resource management and protection.
To prevent administrators from inadvertently modifying resources in a resource group, you must apply a ReadOnly lock at the resource group scope. A ReadOnly lock allows users to view resources but blocks any modification or deletion, even for users with high privileges, unless the lock is first removed.
There are two primary lock levels in Azure:
ReadOnly - Users can read resources but cannot modify or delete them.
CanNotDelete (Delete) - Users can modify resources but cannot delete them.
Since the requirement is to prevent modification, the correct lock level is ReadOnly, not DeleteResources or CanNotDelete.
From Microsoft Azure Administrator documentation:
"A ReadOnly lock prevents users from making changes to a resource. Authorized users can still remove the lock if needed." To create this lock using PowerShell, the correct cmdlet is New-AzResourceLock, which is used to create management locks at the subscription, resource group, or resource level.
Applying the lock to RG1 ensures all resources within the group inherit the protection, meeting the requirement with minimal administrative effort.
Correct PowerShell Command (Conceptual Form)
New-AzResourceLock `
-LockName LockGroup `
-LockLevel ReadOnly `
-ResourceGroupName RG1
Final Hotspot Selections
Cmdlet: New-AzResourceLock
LockName: LockGroup
LockLevel: ReadOnly
ResourceGroupName: RG1

Comment: *

Name: *

Email: *

Verification: *

You have the App Service plans shown in the following table.

You plan to create the Azure web apps shown in the following table.

You need to identify which App Service plans can be used for the web apps.
What should you identify? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.

Correct Answer:

Reference:
https://docs.microsoft.com/en-us/azure/app-service/quickstart-dotnetcore?pivots=platform-linux
https://docs.microsoft.com/en-us/azure/app-service/app-service-plan-manage#

Comment: *

Name: *

Email: *

Verification: *

You have two Azure subscriptions named Sub1 and Sub2 that are linked to separate Microsoft Entra tenants.
You have the virtual networks shown in the following table.

You have two Azure subscriptions named Sub1 and Sub2 that are linked to separate Microsoft Entra tenants.
You have the virtual networks shown in the following table.
Which virtual networks can you peer with VNet1?

• A.VNet2, VNet3, and VNet4 only
• B.VNet2 and VNet4 only
• C.VNet2only
• D.VNet2 and VNet3 only

Comment: *

Name: *

Email: *

Verification: *