Microsoft AZ-305 - Microsoft Designing Microsoft Azure Infrastructure Solutions Certification Examination Exam

Box 1: 3 Scenario: App1 must meet the following requirements: Be hosted in an Azure region thatsupports availability zones. Maintain availability if two availability zones in the local Azure region fail. A host group is a resource that represents a collection of dedicated hosts. You create a host group in a region and an availability zone, and add hosts to it. Use Availability Zones for fault isolation Availability zones are unique physical locations within an Azure region. Each zone is made up of one or more datacenters equipped with independent power, cooling, and networking. A host group is created in a single availability zone. Once created, all hosts will be placed within that zone. To achieve high availability across zones, you need to create multiple host groups (one per zone) and spread your hosts accordingly. Box 2: 1 Scenario: App1 must meet the following requirements: Be hosted on Azure virtual machinesthatsupport automatic scaling. An Azure virtual machine scale set can automatically increase or decrease the number of VM instances that run your application. This automated and elastic behavior reduces the management overhead to monitor and optimize the performance of your application. Reference: https://docs.microsoft.com/en-us/azure/virtual-machines/dedicated-hosts

Parameter	Selected Value	Technical Reason
Number of host groups	3	A dedicated host group is a resource that represents a collection of dedicated hosts. Host groups are typically aligned to specific fault domains or availability zones within an Azure region to guarantee high availability and isolation requirements. Based on the highlighted answer selection, 3 distinct host groups are deployed.
Number of virtual machine scale sets	1	Azure Virtual Machine Scale Sets (VMSS) let you create and manage a group of load-balanced VMs. The selected configuration indicates that exactly 1 virtual machine scale set is configured to manage the scale and orchestration of the instances within this deployment.

Step	Action	Technical Significance
Step 1	Create an Azure policy definition that uses the deployIfNotExists effect.	Before a policy can enforce compliance, the rule template must exist. The deployIfNotExists effect evaluates resources and blocks/deploys sub-resources if the specified target conditions are missing.
Step 2	Create an Azure policy assignment.	Once defined, the policy must be actively targeted at a specific scope (such as a Management Group, Subscription, or Resource Group) by assigning it. This initiates evaluation against existing or incoming cloud resources.
Step 3	Invoke a remediation task.	For existing resources that were already deployed prior to the policy assignment and flagged as non-compliant, you must explicitly trigger a remediation task to apply the deployIfNotExists template and automatically bring them into compliance.

Scenario: All Azure SQL databasesin the production environment must have Transparent Data Encryption (TDE) enabled. Step 1: Create an Azure policy definition that uses the deployIfNotExists identity. The first step is to define the roles that deployIfNotExists and modify needs in the policy definition to successfully deploy the content of your included template. Step 2: Create an Azure policy assignment When creating an assignment using the portal, Azure Policy both generatesthe managed identity and grants it the roles defined in roleDefinitionIds. Step 3: Invoke a remediation task Resources that are non-compliant to a deployIfNotExists or modify policy can be put into a compliant state through Remediation. Remediation is accomplished by instructing Azure Policy to run the deployIfNotExists effect or the modify operations of the assigned policy on your existing resources and subscriptions, whether that assignment is to a management group, a subscription, a resource group, or an individual resource. During evaluation, the policy assignment with deployIfNotExists or modify effects determines if there are non-compliant resources orsubscriptions. When non-compliant resources orsubscriptions are found, the details are provided on the Remediation page.

Scenario: To access the resources in Azure, App1 must use the managed identity of the virtual machines that will host the app. Managed identities provide an identity for applicationsto use when connecting to resources that support Azure Active Directory (Azure AD) authentication. Applications may use the managed identity to obtain Azure AD tokens.

Private Endpointsecurely connect to storage accountsfrom on-premises networks that connect to the VNet using VPN or ExpressRoutes with private-peering. Private Endpoint also secure yourstorage account by configuring the storage firewall to block all connections on the public endpoint for the storage service.  

Requirement	Selected Option	Explanation
Registration for MFA	Azure AD Identity Protection	Azure AD Identity Protection can be used to deploy an MFA registration policy. This policy prompts users to securely register for multi-factor authentication the next time they sign in, ensuring an organized onboarding process.
Enforcement of MFA	Sign-in risk policy in Azure AD Identity Protection for the Litware.com tenant	To enforce authentication controls dynamically based on risk, a sign-in risk policy can be configured. This policy analyzes authentication attempts in real-time and automatically enforces an MFA challenge if suspicious or anomalous behavior is detected during sign-in.

Box 1: Azure AD Identity Protection Azure AD Identity Protection helps you manage the roll-out of Azure AD Multi-Factor Authentication 

(MFA) registration by configuring a Conditional Access policy to require MFA registration no matter what modern authentication app you are signing in to. Scenario: Users that manage the production environment by using the Azure portal must connect from a hybrid Azure AD-joined device and authenticate by using Azure Multi-Factor Authentication (MFA). Box 2: Sign-in risk policy... Scenario: The Litware.com tenant has a conditional access policy named capolicy1. Capolicy1 requiresthat when users manage the Azure subscription for a production environment by using the Azure portal, they must connect from a hybrid Azure AD-joined device. Identity Protection policies we have two risk policies that we can enable in our directory. Sign-in risk policy User risk policy