Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.You need to deploy resources to host a stateless web app in an Azure subscription. The solution must meet the following requirements:Provide access to the .NET framework.Provide redundancy if an Azure region fails.Grant administrators access to the operating system to install custom application dependencies.Solution: You deploy a web app in an Isolated App Service plan.Does this meet the goal?
Answer(s): B
Instead: You deploy two Azure virtual machines to two Azure regions, and you create an Azure Traffic Manager profile.Note: Azure Traffic Manager is a DNS-based traffic load balancer that enables you to distribute traffic optimally to services across global Azure regions, while providing high availability and responsiveness.
https://docs.microsoft.com/en-us/azure/traffic-manager/traffic-manager-overview
You need to design a highly available Azure SQL database that meets the following requirements:Failover between replicas of the database must occur without any data loss.The database must remain available in the event of a zone outage.Costs must be minimized.Which deployment option should you use?
Answer(s): A
Correct:* Azure SQL Database Business Critical (if Premium and Serverless not options, as Business Critical is more expensive)* Azure SQL Database Premium (if not Database Serverless is an option. Premium is more expensive than Serverless)* Azure SQL Database ServerlessOrder of cost:1. Azure SQL Database Serverless (least expensive)2. Azure SQL Database Premium3. Azure SQL Database Business Critical (most expensive)Incorrect:* Azure SQL Database Basic* Azure SQL Database Hyperscale* Azure SQL Database Standard* Azure SQL Managed Instance Business Critical* Azure SQL Managed Instance General PurposeNote on correct answers:* Azure SQL Database PremiumAzure SQL Database Premium tier supports multiple redundant replicas for each database that are automatically provisioned in the same datacenter within a region. This design leverages the SQL Server AlwaysON technology and provides resilience to server failures with 99.99% availability SLA and RPO=0.With the introduction of Azure Availability Zones, we are happy to announce that SQL Database now offers built-in support of Availability Zones in its Premium service tier.* Azure SQL Database ServerlessNow your new and existing serverless Azure SQL Databases allow for zone redundant configuration. This feature utilizes Azure Availability Zones to replicate databases across multiple physical locations within an Azure region. By selecting zone redundancy, you can make your serverless databases resilient to a much larger set of failures, including catastrophic datacenter outages – without any changes of the application logic.Note: The SQL Database serverless compute tier optimizes price-performance and simplifies performance management for single databases with intermittent, unpredictable usage by auto-scaling compute and billing for compute used per second.Serverless is a compute tier for single databases in Azure SQL Database that automatically scales compute based on workload demand and bills for the amount of compute used per second. The serverless compute tier also automatically pauses databases during inactive periods when only storage is billed and automatically resumes databases when activity returnsNote on incorrect answers:* Azure SQL Database BasicNeed Premium for Availability Zones.* Azure SQL Database HyperscaleHyperscale is more expensive than Premium/ Database Serverless.* Azure SQL Managed Instance Business CriticalAzure SQL Managed Instance Business Critical is more expensive.* Azure SQL Managed Instance General PurposeZone redundant configuration that is free on Azure SQL Premium is not available on Azure SQL Managed Instance.Note: There are two high availability architectural models:* Standard availability model that is based on a separation of compute and storage. It relies on high availability and reliability of the remote storage tier. This architecture targets budget-oriented business applications that can tolerate some performance degradation during maintenance activities.* Premium availability model that is based on a cluster of database engine processes. It relies on the fact that there is always a quorum of available database engine nodes. This architecture targets mission-critical applications with high IO performance, high transaction rate and guarantees minimal performance impact to your workload during maintenance activities.Note: Zone-redundant configuration for the general purpose service tier is offered for both serverless and provisioned compute. This configuration utilizes Azure Availability Zones to replicate databases across multiple physical locations within an Azure region.By selecting zone-redundancy, you can make yournew and existing serverless and provisioned generalpurpose single databases and elastic pools resilient to a much larger set of failures, including catastrophic datacenter outages, without any changes of the application logic.
https://azure.microsoft.com/en-us/blog/azure-sql-database-now-offers-zone-redundant-premium-databases- and-elastic-pools/https://docs.microsoft.com/en-us/azure/azure-sql/database/high-availability-sla
HOTSPOT (Drag and Drop is not supported)You have an on-premises Microsoft SQL Server database named SQL1.You plan to migrate SQL1 to Azure.You need to recommend a hosting solution for SQL1. The solution must meet the following requirements:Support the deployment of multiple secondary, read-only replicas.Support automatic replication between primary and secondary replicas.Support failover between primary and secondary replicas within a 15-minute recovery time objective (RTO).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:
Box 1: The Hyperscale service tierWe are excited to announce the General Availability (GA) of enabling Zone Redundancy for Azure SQL Hyperscale databases. The zone redundant configuration utilizes Azure Availability Zones to replicate databases across multiple physical locations within an Azure region. By selecting zone redundancy, you can make all layers of your Hyperscale databases resilient to a much larger set of failures, including catastrophic datacenter outages, without any changes of the application logic.Incorrect:* Azure SQL DatabaseAzure SQL Database Standard does not meet the requirements.* Azure SQL managed instanceZone-redundant configuration is not available in SQL Managed Instance..Box 2: Active geo-replicationActive geo-replication is a feature that lets you create a continuously synchronized readable secondary database for a primary database. The readable secondary database may be in the same Azure region as the primary, or, more commonly, in a different region. This kind of readable secondary database is also known as a geo-secondary or geo-replica.Active geo-replication is designed as a business continuity solution that lets you perform quick disaster recovery of individual databases in case of a regional disaster or a large scale outage. Once geo-replication is set up, you can initiate a geo-failover to a geo-secondary in a different Azure region. The geo-failover is initiated programmatically by the application or manually by the user.Note: Active geo-replication, available for Premium databases, provides the richest solution with the least risk of data loss and the most rapid recovery time. It extends standard geo-replication with up to 4 geo-replicated secondaries that are online and readable at all times, and which can also be used for load balancing or to provide low-latency access to replicated data anywhere in the world.Incorrect:* Auto-failover groupsFailover groups cannot be created between two servers in the same Azure region.* Standard Geo-ReplicationStandard Geo-Replication allows you to configure your database to asynchronously replicate committed transactions from the primary database to the secondary in a predefined Azure region.Standard geo-replication* for Standard and Premium databases extends the local HA system to create and maintain additional secondary replicas in a paired region. These secondaries are offline and not accessible unless there is a data center disruption, at which point they are brought online so that applications can be failed over to them.
https://techcommunity.microsoft.com/t5/azure-sql-blog/announcing-general-availability-ga-of-zone- redundancy-for-azure/ba-p/3590797https://learn.microsoft.com/en-us/azure/azure-sql/database/active-geo-replication-overview
HOTSPOT (Drag and Drop is not supported)You have two on-premises Microsoft SQL Server 2022 instances that host an Always On availability group named AG1. AG1 contains a single database named DB1.You have an Azure subscription that contains a virtual machine named VM1. VM1 runs Linux and contains a SQL Server 2019 instance.You need to migrate DB1 to VM1. The solution must minimize downtime on DB1.What should you do? To answer, select the appropriate options in the answer area.Note: Each correct selection is worth one point.Hot Area:
Box 1: Creating an Always On availability group on VM1Scenario steps (see step 8 below)Here’s how Contoso runs the migration:Step 1: Prepare a SQL Server Always On availability group cluster. Create a cluster for deploying two SQL Server VM nodes in Azure.Step 2: Deploy and set up the cluster. Prepare a SQL Server cluster in Azure. Databases migrate into this existing cluster.Step 3: Deploy Azure Load Balancer. Deploy a load balancer to balance traffic to the SQL Server nodes. Step 4: Prepare Azure for Azure Migrate. Create an Azure Storage account to hold replicated data. Step 5: Prepare on-premises Vmware for Azure Migrate. Prepare accounts for VM discovery and agent installation. Prepare on-premises VMs so that users can connect to Azure VMs after migration. Step 6: Replicate the on-premises VMs to Azure. Enable VM replication to Azure. Step 7: Migrate the database by way of Azure Database Migration Service. Migrate the database to Azure by using Azure Database Migration Service.Step 8: Protect the database with SQL Server Always On. Create an Always On availability group for the cluster.Step 9: Migrate the VM with Azure Migrate. Run a test migration to make sure everything’s working as expected. Then run a migration to Azure.Box 2: Azure MigrateYou can migrate your SQL Server Always On availability group to SQL Server on Azure VMs using the Azure Migrate: Server Migration tool. Using the migration tool, you will be able to migrate each replica in the availability group to an Azure VM hosting SQL Server, as well as the cluster metadata, availability group metadata and other necessary high availability components.
https://learn.microsoft.com/en-us/azure/azure-sql/migration-guides/virtual-machines/sql-server- availability-group-to-sql-on-azure-vm?view=azuresql https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/migrate/azure-best-practices/contoso- migration-rehost-vm-sql-ag
HOTSPOT (Drag and Drop is not supported)You are building an Azure web app that will store the Personally Identifiable Information (PII) of employees.You need to recommend an Azure SQL Database solution for the web app. The solution must meet the following requirements:Maintain availability in the event of a single datacenter outage.Support the encryption of specific columns that contain PII.Automatically scale up during payroll operations.Minimize costs.What should you include in the recommendations? To answer, select the appropriate options in the answer area.Note: Each correct selection is worth one point.Hot Area:
Box 1: Business Critical service tier and Serverless computer tier.Business CriticalOLTP applications with high transaction rate and low I/O latency. Offers highest resilience to failures and fast failovers using multiple synchronously updated replicas.Availability: 3 replicas, 1 Read Scale-out, zone-redundant HA, full local storageNote: Azure SQL Database is based on SQL Server Database Engine architecture that is adjusted for the cloud environment to ensure high availability even in cases of infrastructure failures. There are three architectural models that are used in Azure SQL Database:General Purpose/StandardBusiness Critical/PremiumHyperscaleIncorrect:* General Purpose and Serverless computer tierOffers budget oriented balanced compute and storage options.No Read Scale-out.** Hyperscale service tier and Provisioned compute tierExpensive.Most business workloads. Autoscaling storage size up to 100 TB, fast vertical and horizontal compute scaling, fast database restore.Box 2: Always EncryptedPII data needs to be tightly protected.In Azure, Most of the PaaS services already have a server-side encryption to protect data at rest like Transparent data encryption for Azure SQL Databases. For client side encryption, we can accomplish this natively with an encryption technology called Always encrypted for Azure SQL Database or any SQL Server datastore. There are several data tokenization solutions out in the marketplace which can tokenize this data as well but its only effective for small strings and integers. However, if your data contains large text columns which has PII information then these tokenization solutions are not so effective and can become a bottleneck. Example: Call center voice transcripts which may have sensitive information like a SSN or a Creditcard number etc. That’s where Always encrypted can handle this effectively out of the box.
https://learn.microsoft.com/en-us/azure/azure-sql/database/service-tier-hyperscale https://medium.com/@raghavender7/protecting-sensitive-pii-data-in-azure-sql-databases-5c83bca473fc
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.