Free AZ-305 Exam Questions and Answers | by Exam-Dumps.net (Page: 4)

QUESTION: 1

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:

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

Reveal Solution Next Question

QUESTION: 2

You need to recommend a solution that meets the application development requirements.
What should you include in the recommendation?

the Azure App Configuration service
an Azure Container Registry instance
deployment slots
Continuous Integration/Continuous Deployment (CI/CD) sources

Answer(s): C

Explanation:

When you deploy your web app, web app on Linux, mobile back end, or API app to Azure App Service, you can use a separate deployment slot instead of the default production slot when you're running in the Standard, Premium, or Isolated App Service plan tier. Deployment slots are live apps with their own host names.
App content and configurations elements can be swapped between two deployment slots, including the production slot.
Deploying your application to a non-production slot has the following benefits:
* You can validate app changes in a staging deployment slot before swapping it with the production slot.
* Deploying an app to a slot first and swapping it into production makes sure that all instances of the slot are warmed up before being swapped into production.
This eliminates downtime when you deploy your app.
* After a swap, the slot with previously staged app now has the previous production app. If the changes swapped into the production slot aren't as you expect, you can perform the same swap immediately to get your "last known good site" back.
Note: Application Development Requirements
Application developers will constantly develop new versions of App1 and App2. The development process must meet the following requirements:
ג€¢ A staging instance of a new application version must be deployed to the application host before the new version is used in production.
ג€¢ After testing the new version, the staging version of the application will replace the production version.
ג€¢ The switch to the new application version from staging to production must occur without any downtime of the application.

Reference:

https://docs.microsoft.com/en-us/azure/app-service/deploy-staging-slots

Reveal Solution Next Question

QUESTION: 2

After you migrate App1 to Azure, you need to enforce the data modification requirements to meet the security and compliance requirements.
What should you do?

Create an access policy for the blob service.
Implement Azure resource locks.
Create Azure RBAC assignments.
Modify the access level of the blob service.

Answer(s): A

Explanation:

Scenario: Once App1 is migrated to Azure, you must ensure that new data can be written to the app, and the modification of new and existing data is prevented for a period of three years.
As an administrator, you can lock a subscription, resource group, or resource to prevent other users in your organization from accidentally deleting or modifying critical resources. The lock overrides any permissions the user might have.

Reference:

https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/lock-resources

Reveal Solution Next Question

QUESTION: 2

You need to recommend a solution that meets the data requirements for App1.
What should you recommend deploying to each availability zone that contains an instance of App1?

an Azure Cosmos DB that uses multi-region writes
an Azure Data Lake store that uses geo-zone-redundant storage (GZRS)
an Azure Storage account that uses geo-zone-redundant storage (GZRS)

Answer(s): A

Explanation:

Scenario: App1 has the following data requirements:
- Each instance will write data to a data store in the same availability zone as the instance.
- Data written by any App1 instance must be visible to all App1 instances.
Azure Cosmos DB: Each partition across all the regions is replicated. Each region contains all the data partitions of an Azure Cosmos container and can serve reads as well as serve writes when multi-region writes is enabled.
Incorrect Answers:
B, D: GZRS protects against failures. Geo-redundant storage (with GRS or GZRS) replicates your data to another physical location in the secondary region to protect against regional outages. However, that data is available to be read only if the customer or Microsoft initiates a failover from the primary to secondary region.
C: 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.

Reference:

https://docs.microsoft.com/en-us/azure/cosmos-db/high-availability

Reveal Solution Next Question

QUESTION: 2

What should you recommend to meet the monitoring requirements for App2?

VM insights
Azure Application Insights
Microsoft Sentinel
Container insights

Answer(s): B

Explanation:

Scenario: You need to monitor App2 to analyze how long it takes to perform different transactions within the application. The solution must not require changes to the application code.
Unified cross-component transaction diagnostics.
The unified diagnostics experience automatically correlates server-side telemetry from across all your Application Insights monitored components into a single view. It doesn't matter if you have multiple resources. Application Insights detects the underlying relationship and allows you to easily diagnose the application component, dependency, or exception that caused a transaction slowdown or failure.
Note: Components are independently deployable parts of your distributed/microservices application. Developers and operations teams have code-level visibility or access to telemetry generated by these application components.

Reference:

https://docs.microsoft.com/en-us/azure/azure-monitor/app/transaction-diagnostics

Reveal Solution Next Question

Microsoft AZ-305 Exam (page: 4) Microsoft Designing Azure Infrastructure Solutions Updated on: 28-Jul-2025

QUESTION: 1

Explanation:

Reference:

QUESTION: 2

Explanation:

Reference:

QUESTION: 2

Explanation:

Reference:

QUESTION: 2

Explanation:

Reference:

QUESTION: 2

Explanation:

Reference:

Microsoft AZ-305 Exam (page: 4)
Microsoft Designing Azure Infrastructure Solutions
Updated on: 28-Jul-2025