Free AZ-305 Exam Braindumps
Designing Microsoft Azure Infrastructure Solutions Questions 151–155 (page: 32)

Updated On: 10-Feb-2026

HOTSPOT (Drag and Drop is not supported)

You have an Azure subscription. The subscription contains an Azure SQL managed instance that stores employee details, including social security numbers and phone numbers.

You need to configure the managed instance to meet the following requirements:

The helpdesk team must see only the last four digits of an employee’s phone number.

Database administrators must be prevented from seeing the employees’ social security numbers.

What should you enable for each column in the managed instance? To answer, select the appropriate options in the answer area.

Note: Each correct selection is worth one point.

Hot Area:

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Box 1: Dynamic data masking
Phone numbers
The helpdesk team must see only the last four digits of an employee’s phone number.

Dynamic data masking helps prevent unauthorized access to sensitive data by enabling customers to designate how much of the sensitive data to reveal with minimal effect on the application layer. It’s a policy-based security feature that hides the sensitive data in the result set of a query over designated database fields, while the data in the database isn’t changed.

Masking functions: A set of methods that control the exposure of data for different scenarios.

* Credit card
Masking method, which exposes the last four digits of the designated fields and adds a constant string as a prefix in the form of a credit card.

XXXX-XXXX-XXXX-1234

Box 2: Always Encrypted
Social security numbers
Database administrators must be prevented from seeing the employees’ social security numbers.

Always Encrypted is a feature designed to protect sensitive data, such as credit card numbers or national/ regional identification numbers (for example, U.S. social security numbers), stored in Azure SQL Database, Azure SQL Managed Instance, and SQL Server databases. Always Encrypted allows clients to encrypt sensitive data inside client applications and never reveal the encryption keys to the Database Engine. This provides a separation between those who own the data and can view it, and those who manage the data but should have no access – on-premises database administrators, cloud database operators, or other high-privileged unauthorized users. As a result, Always Encrypted enables customers to confidently store their sensitive data in the cloud, and to reduce the likelihood of data theft by malicious insiders.


Reference:

https://learn.microsoft.com/en-us/sql/relational-databases/security/encryption/always-encrypted-database- engine https://learn.microsoft.com/en-us/azure/azure-sql/database/dynamic-data-masking-overview



DRAG DROP (Drag and Drop is not supported)

You have a 500-TB, on premises Microsoft SQL Server database named DB1.

You have an on-premises datacenter that contains virtual machines. The virtual machines host database, web, file and application resources.

You have an Azure subscription.

You need to migrate DB1 and the virtual machines to Azure. The solution must meet the following requirements:

During the migration of DB1, data cannot be transmitted over the internet, and the impact on the internet must be minimized.
The migration of the virtual machines must support a test migration before the production migration.

During the migration of the virtual machines, downtime must be minimized.

What should you use for each migration? To answer, drag the appropriate services to the correct targets. Each service 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:

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Box 1: Data Migration Assistant (DMA)
DB1

The Data Migration Assistant (DMA) helps you upgrade to a modern data platform by detecting compatibility issues that can affect database functionality when you:

Upgrade to a new version of SQL Server
Migrate to Azure SQL Database
Migrate to Azure SQL Managed Instance
DMA recommends performance and reliability improvements for your target environment and allows you to move your schema, data, and uncontained objects from your source server to your target server.

Note: Data Migration Assistant (DMA) you can spend more than 24 hours to migrate 1 TB. DMA can take 26-28 hours to migrate 700 MB.

Incorrect:
* Azure Data box
Not necessary for a 500 GB data base.

The Microsoft Azure Data Box cloud solution lets you send terabytes of data into and out of Azure in a quick, inexpensive, and reliable way. The secure data transfer is accelerated by shipping you a proprietary Data Box storage device. Each storage device has a maximum usable storage capacity of 80 TB and is transported to your datacenter through a regional carrier. The device has a rugged casing to protect and secure data during the transit.

Box 2: Azure Migrate
Virtual machines

Azure Migrate is the recommended and most comprehensive tool for migrating on-premises virtual machines to Azure, as it provides a central hub for discovery, assessment, and migration. It supports various VM types, including Vmware, Hyper-V, and physical servers, offering both agentless and agent-based migration options and tools to help with business case generation, cost reduction, and optimized VM sizing.


Reference:

https://learn.microsoft.com/sl-si/previous-versions/sql/dma/dma-overview https://learn.microsoft.com/en-us/azure/migrate/migrate-services-overview



View Related Case Study

HOTSPOT (Drag and Drop is not supported)

You are evaluating whether to use Azure Traffic Manager and Azure Application Gateway to meet the connection requirements for App1.

What is the minimum numbers of instances required for each service? To answer, select the appropriate options in the answer area.

Note: Each correct selection is worth one point.

Hot Area:

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Box 1: 1
App1 will only be accessible from the internet. App1 has the following connection requirements:

· Connections to App1 must be active-active load balanced between instances. · All connections to App1 from North America must be directed to the East US region. All other connections must be directed to the West Europe region.
App1 will have six instances: three in the East US Azure region and three in the West Europe Azure region.

Note: Azure Traffic Manager is a DNS-based traffic load balancer. This service allows you to distribute traffic to your public facing applications across the global Azure regions.

Box 2: 2
For production workloads, run at least two gateway instances. A single Application Gateway deployment can run multiple instances of the gateway. Use one Application Gateway in East US Region, and one in the West Europe region.


Reference:

https://docs.microsoft.com/en-us/azure/architecture/high-availability/reference-architecture-traffic-manager- application-gateway



View Related Case Study

HOTSPOT (Drag and Drop is not supported)

How should the migrated databases DB1 and DB2 be implemented in Azure?

Hot Area:

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Box 1: SQL Managed Instance
Scenario: Once migrated to Azure, DB1 and DB2 must meet the following requirements:
Maintain availability if two availability zones in the local Azure region fail.

Fail over automatically.

Minimize I/O latency.

The auto-failover groups feature allows you to manage the replication and failover of a group of databases on a server or all databases in a managed instance to another region. It is a declarative abstraction on top of the existing active geo-replication feature, designed to simplify deployment and management of geo-replicated databases at scale. You can initiate a geo-failover manually or you can delegate it to the Azure service based on a user-defined policy. The latter option allows you to automatically recover multiple related databases in a secondary region after a catastrophic failure or other unplanned event that results in full or partial loss of the SQL Database or SQL Managed Instance availability in the primary region.

Box 2: Business critical
SQL Managed Instance is available in two service tiers:
General purpose: Designed for applications with typical performance and I/O latency requirements. Business critical: Designed for applications with low I/O latency requirements and minimal impact of underlying maintenance operations on the workload.


Reference:

https://docs.microsoft.com/en-us/azure/azure-sql/database/auto-failover-group-overview https://docs.microsoft.com/en-us/azure/azure-sql/managed-instance/sql-managed-instance-paas-overview



View Related Case Study

HOTSPOT (Drag and Drop is not supported)

You design a solution for the web tier of WebApp1 as shown in the exhibit.



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:

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Box 1: Yes
Any new deployments to Azure must be redundant in case an Azure region fails.

Traffic Manager is resilient to failure, including the failure of an entire Azure region.

Box 2: No
Traffic Manager provides load balancing, but not auto-scaling.

Box 3: No
Automatic failover using Azure Traffic Manager: when you have complex architectures and multiple sets of resources capable of performing the same function, you can configure Azure Traffic Manager (based on DNS) to check the health of your resources and route the traffic from the non-healthy resource to the healthy resource.


Reference:

https://docs.microsoft.com/en-us/azure/traffic-manager/traffic-manager-overview https://docs.microsoft.com/en-us/azure/networking/disaster-recovery-dns-traffic-manager



Viewing page 32 of 67
Viewing questions 156 - 160 out of 382 questions


Post your Comments and Discuss Microsoft AZ-305 exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!