HOTSPOT (Drag and Drop is not supported)You have an Azure subscription.You are designing a solution for containerized apps. The solution must meet the following requirements:-Automatically scale the apps by creating additional instances.-Minimize administrative effort to maintain nodes and clusters.-Ensure that containerized apps are highly available across multiple availability zones.-Provide a central location for the lifecycle management and storage of container images.What should you include in the solution? To answer, select the appropriate options in the answer area.Note: Each correct selection is worth one point.Hot Area:
Answer(s): A
Box 1: Azure Container AppsTo run the containerized apps:Azure Container Apps manages automatic horizontal scaling through a set of declarative scaling rules. As a container app revision scales out, new instances of the revision are created on-demand. These instances are known as replicas.Reliability in Azure Container AppsAzure Container Apps uses availability zones in regions where they're available to provide high-availability protection for your applications and data from data center failures.By enabling Container Apps' zone redundancy feature, replicas are automatically distributed across the zones in the region. Traffic is load balanced among the replicas. If a zone outage occurs, traffic is automatically routed to the replicas in the remaining zones.Box 2: Azure Container RegistryFor the lifecycle management and storage of container images:Azure Container RegistryA registry of Docker and Open Container Initiative (OCI) images, with support for all OCI artifacts.Simplify container lifecycle managementBuild, store, secure, scan, replicate, and manage container images and artifacts with a fully managed, geo-replicated instance of OCI distribution. Connect across environments, including Azure Kubernetes Service and Azure Red Hat OpenShift, and across Azure services like App Service, Machine Learning, and Batch.
https://learn.microsoft.com/en-us/azure/container-apps/scale-app https://learn.microsoft.com/en-us/azure/reliability/reliability-azure-container-apps https://azure.microsoft.com/en-us/products/container-registry
DRAG DROP (Drag and Drop is not supported)You have an Azure subscription.You are designing a deployment plan for the Azure App Service web apps shown in the following table.You need to recommend a database solution for the apps. The solution must meet the following requirements:-Provide zone redundancy.-Minimize costs and administrative effort.What should you include in the recommendation for each app? To answer, drag the appropriate database types to the correct apps. Each database type 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.Note: Each correct selection is worth one point.Select and Place:
Box 1: Azure Database for PostgreSQL flexible server in the general purpose tier.App1Will contain a PostgreSQL database that was migrated from an on-premises server and will fail over automatically.Incorrect:* Burstable compute tierZone-redundant is not supported for:Burstable compute tier.Regions with single-zone availability.* memory optimizer tier.More expensive.Box 2: Azure Cosmos DB for NoSQL and single-region writes with availability zones SLAApp2Will contain a PostgreSQL database that has write availability SLA of more than 99.995%.For single-region writes in Azure Cosmos DB for NoSQL with availability zones, it is 99.995% for writes, with a minimum of 1,000 RU/s and a potential for 1.25x RU/s for serverless.Incorrect:* Azure Cosmos DB for NoSQL and multiple-region, single-region writes without availability zones SLA Multi-Region Writes With Availability Zones: 99.999% availability SLA.This does not Minimize costs.For multi-region, single-region writes without an availability zone SLA, the Standard Provisioned Throughput model costs approximately $5.84 per 100 RU/s per month for each region in a general purpose account, and $11.68 per 100 RU/s per month for a business critical account. Storage costs are separate and are charged per gigabyte.* Azure Cosmos DB for NoSQL and single-region writes without availability zones SLAFor single-region writes in Azure Cosmos DB for NoSQL, the SLA is 99.99%* Azure Database for PostgreSQL flexible server in the Burstable tier.The Burstable tier best suits low-cost development and low concurrency workloads without continuous compute capacity. The General Purpose and Memory Optimized are better suited for production workloads requiring high concurrency, scale, and predictable performance.* Azure Database for PostgreSQL flexible server in the memory optimizer tier.The Azure Database for PostgreSQL flexible server in the Memory Optimized tier does not offer an SLA higher than 99.995%. The maximum SLA for zone-redundant configurations in the flexible server deployment model is 99.99%.* Azure Database for PostgreSQL flexible server in the General purpose tierThe Azure Database for PostgreSQL flexible server in the General Purpose tier does not offer an SLA higher than 99.995%; the maximum SLA available for flexible server is 99.99%, which requires the Zone-redundant high availability option, but this option is unavailable for the General Purpose tier.
https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/overview https://learn.microsoft.com/en-us/azure/reliability/reliability-postgresql-flexible-server
HOTSPOT (Drag and Drop is not supported)You plan to develop a new app that will store business critical data. The app must meet the following requirements:-Prevent new data from being modified for one year.-Maximize data resiliency.-Minimize read latency.What storage solution should you recommend for the app? To answer, select the appropriate options in the answer area.Note: Each correct selection is worth one point.Hot Area:
Box 1: Standard general-purpose v2Standard general-purpose v2 supports immutable storage.In general Standard general-purpose v2 is the preferred Microsoft recommendation.Box 2: Zone-redundant storage (ZRS)ZRS is more resilient compared to LRS.Note: RA-GRS is even more resilient, but it is not an option here.
https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blob-immutable-storage
HOTSPOT (Drag and Drop is not supported)You plan to deploy the backup policy shown in the following exhibit.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:
HOTSPOT (Drag and Drop is not supported)You have an Azure subscription.You plan to deploy two 100-virtual machine deployments as shown in the following table.You need to recommend a virtual machine grouping solution for the deployments.What should you include in the recommendation for each deployment? To answer, select the appropriate options in the answer area.Note: Each correct selection is worth one point.Hot Area:
Box 1: A virtual machine scale set in Flexible orchestration modeFlexible orchestration mode supports Ultra disks.Flexible orchestration mode supports a mix of Windows and Linux Servers.Note: The following list contains Ultra Disk's limitations:* Currently, Ultra Disks only support Single VM and Availability zone infrastructure options.* Ultra Disks don't support availability sets.* Etc.Incorrect:* Am availability setUltra Disks don't support availability sets.* Uniform orchestration for scale setsUniform orchestration for scale sets only support instances are the same operating system, not a mix of Windows and Linux Servers.Box 2: An availability set.Orchestration modes for Virtual Machine Scale Sets in AzureWhen you want to deploy Virtual Machines that are close together along with its disks to ensure the lowest latency possible, you can assign Azure Virtual Machines to a Proximity Placement Group.Some relationships Proximity Placement Groups have to resources are:* Assigning an Availability Set to a Proximity Placement Group so that Virtual Machines associated with an Availability Set leverage the Fault Domain and Update Domain capabilities of an Availability Set while also being located within the same “Network Spine” which is typically the same Datacenter. These Virtual Machines would carry a 99.95% SLA.* Etc.Note:Placing VMs in a single region reduces the physical distance between the instances. Placing them within a single availability zone will also bring them physically closer together. However, as the Azure footprint grows, a single availability zone might span multiple physical data centers, which might result in a network latency impacting your application.To get VMs as close as possible, achieving the lowest possible latency, you can deploy them within a proximity placement group.Using Proximity Placement GroupsA proximity placement group is a resource in Azure. You need to create one before using it with other resources. Once created, it could be used with virtual machines, availability sets, or Virtual Machine Scale Sets. You specify a proximity placement group when creating compute resources providing the proximity placement group ID.
https://learn.microsoft.com/en-us/azure/virtual-machines/disks-enable-ultra-ssd https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-orchestration-mo des https://www.shudnow.io/2022/04/09/pin-azure-vm-availability-sets-into-an-availability-zone/
Post your Comments and Discuss Microsoft AZ-305 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the AZ-305 content, but please register or login to continue.