Free AZ-305 Exam Braindumps
Designing Microsoft Azure Infrastructure Solutions Questions 10–14 (page: 5)

Updated On: 16-Nov-2026
View Related Case Study

You have an application that is used by 6,000 users to validate their vacation requests. The application manages its own credential store.
Users must enter a username and password to access the application. The application does not support identity federation.
You need to implement single sign-on (SSO) authentication by using a Microsoft Entra application registration.
Which SSO method should you use?

  1. header-based
  2. SAML
  3. password-based
  4. OpenID Connect

Answer(s): C

Explanation:

Password - On-premises applications can use a password-based method for SSO. This choice works when applications are configured for Application Proxy.
With password-based SSO, users sign in to the application with a username and password the first time they access it. After the first sign-on, Microsoft Entra ID provides the username and password to the application. Password-based SSO enables secure application password storage and replay using a web browser extension or mobile app. This option uses the existing sign-in process provided by the application, enables an administrator to manage the passwords, and doesn't require the user to know the password.
Incorrect:
Choosing an SSO method depends on how the application is configured for authentication. Cloud applications can use federation-based options, such as OpenID Connect, OAuth, and SAML.
Federation - When you set up SSO to work between multiple identity providers, it's called federation.


Reference:

https://docs.microsoft.com/en-us/azure/active-directory/manage-apps/what-is-single-sign-on



View Related Case Study

HOTSPOT (Drag and Drop is not supported)
You have an Azure subscription.
You plan to deploy five storage accounts that will store block blobs and five storage accounts that will host file shares. The file shares will be accessed by using the SMB protocol.
You need to recommend an access authorization solution for the storage accounts. The solution must meet the following requirements:
-Maximize security.
-Prevent the use of shared keys.
-Whenever possible, support time-limited access.
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:

  1. See Explanation section for answer.

Answer(s): A

Explanation:



Box 1: A shared access signature (SAS) and a stored access policy
Blobs
See note below.
User delegation SAS
A user delegation SAS is secured with Microsoft Entra credentials and also by the permissions specified for the SAS. A user delegation SAS applies to Blob storage only.
A shared access signature can take one of the following two forms:
Ad hoc SAS.
When you create an ad hoc SAS, the start time, expiry time, and permissions are specified in the SAS URI. Any type of SAS can be an ad hoc SAS.
Service SAS with stored access policy. A stored access policy is defined on a resource container, which can be a blob container, table, queue, or file share. The stored access policy can be used to manage constraints for one or more service shared access signatures.
When you associate a service SAS with a stored access policy, the SAS inherits the constraints—the start time, expiry time, and permissions—defined for the stored access policy.
Note
A user delegation SAS or an account SAS must be an ad hoc SAS. Stored access policies are not supported for the user delegation SAS or the account SAS.
Box 2: Microsoft Entra credentials
File shares
User delegation SAS
A user delegation SAS is secured with Microsoft Entra credentials and also by the permissions specified for the SAS. A user delegation SAS applies to Blob storage only.
Note: A shared access signature (SAS) provides secure delegated access to resources in your storage account. With a SAS, you have granular control over how a client can access your data. For example:
What resources the client may access.
What permissions they have to those resources.
How long the SAS is valid.
Types of shared access signatures
Azure Storage supports three types of shared access signatures:
User delegation SAS
Service SAS
Account SAS


Reference:

https://learn.microsoft.com/en-us/azure/storage/common/storage-sas-overview



View Related Case Study

You have an Azure subscription that contains 1,000 resources.
You need to generate compliance reports for the subscription. The solution must ensure that the resources can be grouped by department.
What should you use to organize the resources?

  1. application groups and quotas
  2. Azure Policy and tags
  3. administrative units and Azure Lighthouse
  4. resource groups and role assignments

Answer(s): B

Explanation:

Compliance Report using Azure Policy
Azure Policy is a powerful tool for Azure Governance. With Azure Policy we can define rules for all Azure Subscriptions the we manage. We can use this rules for simple limitation actions, like permitting only specific VM Series and Sizes that can be created and also more complex rule sets that helps you standardize the whole Azure deployment.
Enforce tags for resource creation
So, why tags? Why we need to add tags to all Azure resources? The Microsoft Azure environments are getting bigger and bigger and managed by multiple people and teams. That makes it difficult to understand who created a resource and what is the purpose of that resource. Another critical matter that we need tags is Cost Management. At the Azure Cost Management Portal, we can sort and arrange the resource cost using the Tags. This way we can provide an expense dashboard with the actual cost of the resources per department, project or whatever tags we have added to the Resource.


Reference:

https://www.cloudcorner.gr/microsoft/azure/compliance-report-using-azure-policy/
https://www.cloudcorner.gr/microsoft/azure-policy-enforce-tags-for-resource-creation/



View Related Case Study

HOTSPOT (Drag and Drop is not supported)
You have five Azure subscriptions. Each subscription is linked to a separate Microsoft Entra tenant and contains virtual machines that run Windows Server 2022.
You plan to collect Windows security events from the virtual machines and send them to a single Log Analytics workspace.
You need to recommend a solution that meets the following requirements:
-Collects event logs from multiple subscriptions
-Supports the use of data collection rules (DCRs) to define which events to collect
What should you recommend for each requirement? 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: Azure Event Grid
To collect the event logs:
Incorrect:
* Azure Lighthouse
Azure Lighthouse helps service providers efficiently build and deliver managed services.
Box 2: The Azure Monitor Agent
To support the DCRs:
You collect events and performance counters from virtual machines with Azure Monitor Agent.
You can define a data collection rule to send data from multiple machines to multiple Log Analytics workspaces, including workspaces in a different region or tenant. Create the data collection rule in the same region as your Log Analytics workspace.
How can I collect Windows security events by using Azure Monitor Agent?
There are two ways you can collect Security events using the new agent, when sending to a Log Analytics workspace:
You can use Azure Monitor Agent to natively collect Security Events, same as other Windows Events. These flow to the 'Event' table in your Log Analytics workspace.
If you have Microsoft Sentinel enabled on the workspace, the security events flow via Azure Monitor Agent into the SecurityEvent table instead (the same as using the Log Analytics agent). This scenario always requires the solution to be enabled first.


Reference:

https://learn.microsoft.com/en-us/azure/azure-monitor/agents/data-collection-rule-azure-monitor-agent https://learn.microsoft.com/en-us/azure/event-grid/enable-diagnostic-logs-topic



View Related Case Study

You have an Azure subscription. The subscription contains a tiered app named App1 that is distributed across multiple containers hosted in Azure Container Instances.
You need to deploy an Azure Monitor monitoring solution for App1. The solution must meet the following requirements:
-Support using synthetic transaction monitoring to simulate real user interactions and identify UI failures.
-Minimize development effort.
What two features can you include in the solution? Each correct answer presents a complete solution.
Note: Each correct selection is worth one point.

  1. Log Analytics Workspace Insights
  2. Function App
  3. Azure Monitor Application Insights
  4. Container insights
  5. Azure Monitor Network Insights

Answer(s): A,C

Explanation:

[C]
Azure Monitor Application Insights supports synthetic transaction monitoring to simulate user interactions and identify UI failures by using availability tests and Playwright-based tests to verify functionality and performance from different locations globally. You can configure these tests to perform various actions, such as opening URLs and performing complex user workflows, which then generate telemetry to report availability, performance, and failures.
[A]
Log Analytics Workspace Insights is a feature within Azure Monitor that provides a unified, graphical view of your Log Analytics workspace's usage, performance, health, connected agents, query activity, and change log. It offers a centralized dashboard to help you monitor and understand your workspaces, enabling operational teams to track health, identify trends, and ensure continuous improvement of your log collection and monitoring strategy.


Reference:

https://learn.microsoft.com/en-us/azure/azure-monitor/app/app-insights-overview https://learn.microsoft.com/en-us/azure/azure-monitor/logs/log-analytics-workspace-insights-overview



Viewing page 5 of 78
Viewing questions 21 - 25 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!