HOTSPOT (Drag and Drop is not supported)You have a Microsoft Entra tenant named contoso.com that contains multiple enterprise apps.Your company has a business partner that has a Microsoft Entra tenant named fabrikam.com.You need to recommend an identity governance solution that will provide users in fabrikam.com with access to the enterprise apps in contoso.com. The solution must meet the following requirements:-Ensure that administrators in fabrikam.com can provide the fabrikam.com users with access to the contoso.com enterprise apps.-Automatically provision identities for the fabrikam.com users to enable access to the contoso.com enterprise apps.-Provide policy-based management of access assignments, approvals, and expirations.-Minimize administrative effort.What should you include in the recommendation? To answer, select the appropriate options in the answer area.Note: Each correct selection is worth one point.Hot Area:
Answer(s): A
Box 1: Cross-tenant synchronizationFor identity provisioning:Cross-tenant synchronization automates creating, updating, and deleting Microsoft Entra B2B collaboration users across tenants in an organization. It enables users to access applications and collaborate across tenants, while still allowing the organization to evolve.Here are the primary goals of cross-tenant synchronization:Seamless collaboration for a multitenant organizationAutomate lifecycle management of B2B collaboration users in a multitenant organizationAutomatically remove B2B accounts when a user leaves the organizationBox 2: Entitlement managementFor access managementProvide policy-based management of access assignments, approvals, and expirations.The best solution for policy-based management of access assignments, approvals, and expiration in Azure is Microsoft Entra ID Governance Entitlement Management (formerly Azure AD Entitlement Management).Entitlement Management enables organizations to manage the lifecycle of access to groups, applications, and SharePoint sites for both internal and external users through a centralized, policy-driven approach.Entitlement management provides the most comprehensive, end-to-end automation for the specific requirements of policy-driven access assignments, approvals, and expiration.Why Entitlement Management is Best:Policy-Based Access: You can define policies that determine who can request access (e.g., all employees, specific external partners), the requestor information required, and approval workflows.Approvals: It supports multi-stage approval workflows, allowing designated sponsors or managers to approve access requests.Expiration: You can set access assignments to expire automatically on a specific date, after a set number of days, or never, forcing users to renew access if needed.Lifecycle Management: It automates access requests, assignments, and reviews (recertification).Access Packages: By grouping resources into "Access Packages," you can apply a single policy to govern the entire access lifecycle for that package.Incorrect:* Access reviewAccess Reviews is a component of Entra ID Governance that allows you to periodically review access, ensuring that access is removed if no longer necessary.* Privileged Identity Management (PIM)Privileged Identity Management (PIM) is used sed specifically for managing high-privilege administrative roles with JIT (just-in-time) access and time-bound expiration, but entitlement management is broader for general resource access.
https://learn.microsoft.com/en-us/entra/identity/multi-tenant-organizations/cross-tenant-synchronization-overvie w https://learn.microsoft.com/en-us/entra/id-governance/entitlement-management-overview
You have an Azure API Management instance named APIM1.You need to verify the identity of external users who call the APIs in APIM1. The solution must meet the following requirements:-Follow modern secure coding practices.-Minimize code changes to the backend APIs.-Prevent anonymous users from accessing the APIs.-Ensure that you can block access for a specific user if their authentication method is compromised. -What should you use?-
Answer(s): B
To meet these secure development requirements, you should use client certificates.Verifies Identity Individually: Mutual TLS (mTLS) allows the Azure API Management (APIM) gateway to uniquely map and verify the explicit identity of individual external callers.Minimizes Backend Changes: APIM can be configured to natively handle the TLS handshake and validation policy (validate-client-certificate) at the gateway layer. The backend APIs do not need code updates to handle cryptographic verification.Prevents Anonymous Access: Setting up a mandatory client certificate validation policy at the gateway ensures any requests without a valid certificate are rejected immediately.Easy to Block If Compromised: If a specific user's credential or private key is compromised, you can instantly block their access by removing their thumbprint from your gateway's validation list or checking against a Certificate Revocation List (CRL).Incorrect:[Not A, not C]API Keys & Query String Authentication: These methods transfer secrets in plain text or headers/URLs, which violates modern secure coding practices. They are easily intercepted, cached in logs, or forwarded inadvertently.[Not D]Shared Access Signatures (SAS): SAS is a mechanism designed primarily for delegating fine-grained access to Azure storage resources or specific service buses, rather than serving as a standard standard authentication framework for external consumer APIs.
https://www.azadvertizer.net/azpolicyadvertizer/8ac833bd-f505-48d5-887e-c993a1d3eea0.html
DRAG DROP (Drag and Drop is not supported)You have two app registrations named App1 and App2 in Azure AD. App1 supports role-based access control (RBAC) and includes a role named Writer.You need to ensure that when App2 authenticates to access App1, the tokens issued by Microsoft Entra ID include the Writer role claim.Which blade should you use to modify each app registration? To answer, drag the appropriate blades to the correct app registrations. Each blade 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:
Box 1: App rolesApp1 supports role-based access control (RBAC) and includes a role named Writer.Implement role-based access controlDefine app rolesThe first step for implementing RBAC for an application is to define the app roles for it and assign users or groups to it. After defining the app roles and assigning users or groups to them, access the role assignments in the tokens coming into the application and act on them accordingly.Box 2: Token configurationYou need to ensure that when App2 authenticates to access App1, the tokens issued by Microsoft Entra ID include the Writer role claim.Configure optional claimsYou can configure optional claims for your application through the Azure portal or application manifest.-1. Go to the Azure portal.-2. Search for and select Microsoft Entra ID.-3. Under Manage, select App registrations.-4. Choose the application for which you want to configure optional claims based on your scenario and desired outcome.5. Under Manage, select Token configuration6. Etc.
https://learn.microsoft.com/en-us/azure/active-directory/develop/howto-implement-rbac-for-apps https://learn.microsoft.com/en-us/azure/active-directory/develop/optional-claims
Note: This section contains one or more sets of questions with the same scenario and problem. Each question presents a unique solution to the problem. You must determine whether the solution meets the stated goals. More than one solution in the set might solve the problem. It is also possible that none of the solutions in the set solve the problem.After you answer a question in this section, you will NOT be able to return. As a result, these questions do not appear on the Review Screen.Your company, named Contoso, Ltd., has a Microsoft Entra tenant named contoso.com that uses Privileged Identity Management (PIM) and is linked to an Azure subscription named Sub1.You use Azure Backup to back up all the resources in Sub1 to a Recovery Services vault named Vault1.An external company named Fabrikam, Inc. provides security management services to Contoso. Fabrikam has a Microsoft Entra tenant named fabrikam.com and an Azure subscription.You need to prevent a compromised administrator account in contoso.com from modifying backup policies in and deleting backups from Sub1.Solution: You configure a PIM role assignment that requires approval for activation by an administrator in contoso.com.Does this meet the goal?
Correct:* You configure Multi-user authorization (MUA) in Sub1 by using a Resource Guard from fabrikam.com.Incorrect:* In Vault1, you generate a security PIN for critical operations.* You configure a PIM role assignment that requires approval for activation by an administrator in contoso.com.Note: Azure Resource GuardAzure Resource Guard is a security feature that provides an additional layer of protection for critical Azure backup and disaster recovery operations. It helps prevent unauthorized or accidental changes to your backup and recovery configurations, mitigating risks associated with malicious or unintentional modifications.Purpose:Azure Resource Guard is designed to enhance the security of Recovery Services vaults and their associated backup vaults. It allows you to implement multi-user authorization (MUA) on protected operations, reducing the risk of accidental or malicious data loss.How it works:Resource Guard acts as a gatekeeper for critical operations, requiring approvals or permissions before sensitive changes can be made. This helps ensure that only authorized individuals can modify backup settings, delete backups, or perform other critical actions.Key benefits:Reduces the risk of accidental data loss or corruption.*-> Enhances security posture by preventing unauthorized changes to backup configurations.*-> Enables multi-user authorization, requiring approvals for sensitive operations.Provides a granular level of control over backup and recovery operations.
https://learn.microsoft.com/en-us/azure/backup/multi-user-authorization-concept
You plan to deploy an application named App1 that will run on five Azure virtual machines. Additional virtual machines will be deployed later to run App1.You need to recommend a solution to meet the following requirements for the virtual machines that will run App1:-Ensure that the virtual machines can authenticate to Microsoft Entra ID to gain access to an Azure key vault, Azure Logic Apps instances, and an Azure SQL database.-Avoid assigning new roles and permissions for Azure services when you deploy additional virtual machines.-Avoid storing secrets and certificates on the virtual machines.-Minimize administrative effort for managing identities.Which type of identity should you include in the recommendation?
Answer(s): D
Managed identities provide an identity for applications to use when connecting to resources that support Microsoft Entra authentication.A user-assigned managed identity:Can be shared.The same user-assigned managed identity can be associated with more than one Azure resource.Common usage:Workloads that run on multiple resources and can share a single identity.For example, a workload where multiple virtual machines need to access the same resource.Incorrect:Not A: A system-assigned managed identity can’t be shared. It can only be associated with a single Azure resource.Typical usage:Workloads that are contained within a single Azure resource.Workloads for which you need independent identities.For example, an application that runs on a single virtual machine.
https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/overview
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.