AZ-305 · Question #10
AZ-305 Question #10: Real Exam Question with Answer & Explanation
Identity Requirements Recap The requirements are: Monthly review by a Fabrikam account manager of which Fabrikam guest users have access to App1 Remove guests who no longer need access Minimize development effort --- Dropdown 1: Service → Azure AD Identity Governance Why it's c
Question
Case Study 3 - Contoso Existing Environment: Technical Environment The on-premises network contains a single Active Directory domain named contoso.com. Contoso has a single Azure subscription. Existing Environment: Business Partnerships Contoso has a business partnership with Fabrikam, Inc. Fabrikam users access some Contoso applications over the internet by using Azure Active Directory (Azure AD) guest accounts. Requirements: Planned Changes Contoso plans to deploy two applications named App1 and App2 to Azure. Requirements: App1 App1 will be a Python web app hosted in Azure App Service that requires a Linux runtime. Users from Contoso and Fabrikam will access App1. App1 will access several services that require third-party credentials and access strings. The credentials and access strings are stored in Azure Key Vault. App1 will have six instances: three in the East US Azure region and three in the West Europe Azure region. 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. App1 will only be accessible from the internet. App1 has the following connection requirements: Connections to App1 must pass through a web application firewall (WAF). 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. Every hour, you will run a maintenance task by invoking a PowerShell script that copies files from all the App1 instances. The PowerShell script will run from a central location. Requirements: App2 App2 will be a NET app hosted in App Service that requires a Windows runtime. App2 has the following file storage requirements: Save files to an Azure Storage account. Replicate files to an on-premises location. Ensure that on-premises clients can read the files over the LAN by using the SMB protocol. 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. 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. Identity Requirements Contoso identifies the following requirements for managing Fabrikam access to resources: Every month, an account manager at Fabrikam must review which Fabrikam users have access permissions to App1. Accounts that no longer need permissions must be removed as guests. The solution must minimize development effort. Security Requirement All secrets used by Azure services must be stored in Azure Key Vault. Services that require credentials must have the credentials tied to the service instance. The credentials must NOT be shared between services. Hotspot Question What should you implement to meet the identity requirements? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point. Answer:
Options
- __typehotspot
- variantdropdown
Explanation
Identity Requirements Recap
The requirements are:
- Monthly review by a Fabrikam account manager of which Fabrikam guest users have access to App1
- Remove guests who no longer need access
- Minimize development effort
Dropdown 1: Service → Azure AD Identity Governance
Why it's correct: Identity Governance is the Azure AD service specifically designed to manage the lifecycle of access for both internal and external (guest) users. It provides tools to automate access reviews, entitlement management, and access removal — all without custom development.
Why the others are wrong:
| Option | Why Wrong |
|---|---|
| Identity Protection | Detects risky sign-ins and user risk (compromised credentials, impossible travel). It does not manage or review access permissions for guests. |
| Privileged Identity Management (PIM) | Manages privileged role assignments (e.g., Global Admin, Contributor) with just-in-time access. It's not designed for reviewing guest app permissions. |
| Azure Automation | Could theoretically run scripts to review/remove accounts, but requires significant custom development — violates "minimize development effort." |
Dropdown 2: Feature → Access Reviews
Why it's correct: Access Reviews (within Identity Governance) lets you create a recurring review — e.g., monthly — where a designated reviewer (the Fabrikam account manager) is notified to confirm or revoke each guest user's access. When a review completes, access can be automatically removed for accounts the reviewer denies. Zero custom code required.
Why the others are wrong:
| Option | Why Wrong |
|---|---|
| Access packages | Used to bundle and grant resources (apps, groups, SharePoint) to users via entitlement management. This is about provisioning access, not periodically reviewing and revoking it. |
| Approvals | A workflow step within access packages for requesting access. It handles initial approval, not ongoing periodic reviews. |
| Runbooks | Azure Automation scripts — again, requires development effort and ongoing maintenance. Not the right tool when a native no-code feature exists. |
Core Concept
The scenario describes a classic Access Review use case:
- External guest users (Fabrikam in Azure AD B2B)
- Periodic human review by a business stakeholder
- Automatic removal of stale access
This maps directly to: Azure AD Identity Governance → Access Reviews. The key differentiator on the exam is that Access Reviews = periodic recertification of existing access, while Access Packages = initial provisioning of access bundles.
Topics
Community Discussion
No community discussion yet for this question.