Question 140
Workload context: An AKS workload needs Azure SQL access using identity federation without distributing managed-identity credentials into pods. The implemented remedy is: Configure supported AKS workload identity federation with a Kubernetes service account and a federated managed identity. Which ongoing practice most specifically prevents recurrence of this failure: Pods fail when an obsolete secret in Kubernetes is removed.?
- Review Azure RBAC for Kubernetes scopes and audit cluster role bindings during upgrades.
- Review managed-identity roles and audit code for remaining shared keys or SAS credentials.
- Review service-account annotations, federated subjects and least-privilege database permissions.
- Review OIDC subject/audience trust and least-privilege scopes as repository branches change.
Explanation
Correct Answer
C:The preventive control is: Review service-account annotations, federated subjects and least-privilege database permissions. It targets the earlier cause: The workload is coupled to static credentials instead of the expected workload identity token trust. Confirm ongoing effectiveness by: Run a pod with the approved service-account binding and verify token-based SQL access, denying unbound pods.
Incorrect Answers
A:The key follow-up control is: Review Azure RBAC for Kubernetes scopes and audit cluster role bindings during upgrades. The preventive control is: Review service-account annotations, federated subjects and least-privilege database permissions.
B:The preventive control is: Review managed-identity roles and audit code for remaining shared keys or SAS credentials. The preventive control is: Review service-account annotations, federated subjects and least-privilege database permissions.
D:The preventive control is: Review OIDC subject/audience trust and least-privilege scopes as repository branches change. The preventive control is: Review service-account annotations, federated subjects and least-privilege database permissions.
Question 141
A solution architect is reviewing a workload: A tenant contains legacy VMs that require LDAP/Kerberos domain join but administrators do not want to operate domain controllers. The observed incident is: An application cannot use NTLM/Kerberos because only cloud-native Entra authentication is configured. Which architecture choice most directly removes the identified weakness?
- Use Microsoft Entra Domain Services managed domain capabilities for compatible domain join and LDAP/Kerberos workloads.
- Use Microsoft Entra B2B collaboration with an approved guest invitation and application-level assignment or access package.
- Publish the supported web app using Microsoft Entra Application Proxy and a healthy outbound connector group, with Entra preauthentication.
- Design a supported Entra hybrid identity synchronization/sign-in architecture with healthy synchronization and appropriate password hash or federation choices.
Explanation
Correct Answer
A:The targeted implementation is: Use Microsoft Entra Domain Services managed domain capabilities for compatible domain join and LDAP/Kerberos workloads. The problem is not generic resource availability: Microsoft Entra ID alone does not supply managed traditional domain controller protocols to legacy workloads. Verify the result by: Join a test VM and verify domain authentication while confirming domain controllers are service-managed.
Incorrect Answers
B:Using Microsoft Entra B2B collaboration with an approved guest invitation and application-level assignment or access package would not meet the need for managed domain compatibility.
C:Publishing the supported web app using Microsoft Entra Application Proxy and a healthy outbound connector group, with Entra preauthentication would not meet the need for managed domain compatibility.
D:This option does not address the stated problem. The problem is not generic resource availability: Microsoft Entra ID alone does not supply managed traditional domain controller protocols to legacy workloads.
Question 142
An architect proposes this change: Use Microsoft Entra Domain Services managed domain capabilities for compatible domain join and LDAP/Kerberos workloads. The workload context is: A tenant contains legacy VMs that require LDAP/Kerberos domain join but administrators do not want to operate domain controllers. Which evidence would most directly validate the change?
- Invite the vendor and verify access only to the approved app under the tenant's external collaboration policies.
- Create a test on-premises user and verify account attributes and selected sign-in method in Entra.
- Join a test VM and verify domain authentication while confirming domain controllers are service-managed.
- Test an external login against Entra and verify the connector reaches the internal URL without an inbound internet firewall rule.
Explanation
Correct Answer
C:The acceptance test is specific: Join a test VM and verify domain authentication while confirming domain controllers are service-managed. Its purpose is to establish that the proposed architecture works: Use Microsoft Entra Domain Services managed domain capabilities for compatible domain join and LDAP/Kerberos workloads.
Incorrect Answers
A:The alternative test targets: Use Microsoft Entra B2B collaboration with an approved guest invitation and application-level assignment or access package. The scenario's actual proposed remedy is: Use Microsoft Entra Domain Services managed domain capabilities for compatible domain join and LDAP/Kerberos workloads. Verify that one by: Join a test VM and verify domain authentication while confirming domain controllers are service-managed.
B:The acceptance test is specific: Join a test VM and verify domain authentication while confirming domain controllers are service-managed.
D:The alternative test targets: Publish the supported web app using Microsoft Entra Application Proxy and a healthy outbound connector group, with Entra preauthentication. The scenario's actual proposed remedy is: Use Microsoft Entra Domain Services managed domain capabilities for compatible domain join and LDAP/Kerberos workloads. Verify that one by: Join a test VM and verify domain authentication while confirming domain controllers are service-managed.
Question 143
During architecture troubleshooting, a team reports: An application cannot use NTLM/Kerberos because only cloud-native Entra authentication is configured. Context: A tenant contains legacy VMs that require LDAP/Kerberos domain join but administrators do not want to operate domain controllers. Which underlying design mistake explains the observed behavior most precisely?
- The application was published by direct inbound exposure instead of Entra-aware proxy preauthentication.
- The hybrid identity provisioning path between AD and Entra is missing or not healthy.
- External collaboration was treated as a permanent internal employee account rather than a governed guest identity.
- Microsoft Entra ID alone does not supply managed traditional domain controller protocols to legacy workloads.
Explanation
Correct Answer
D:The recorded behavior follows from: Microsoft Entra ID alone does not supply managed traditional domain controller protocols to legacy workloads. The appropriate mitigation would be: Use Microsoft Entra Domain Services managed domain capabilities for compatible domain join and LDAP/Kerberos workloads. Verify with: Join a test VM and verify domain authentication while confirming domain controllers are service-managed.
Incorrect Answers
A:The alternative diagnosis “The application was published by direct inbound exposure instead of Entra-aware proxy preauthentication” does not match the observed symptom: An application cannot use NTLM/Kerberos because only cloud-native Entra authentication is configured. Context: A tenant contains legacy VMs that require LDAP/Kerberos domain join but administrators do not want to operate domain controllers. The recorded behavior follows from: Microsoft Entra ID alone does not supply managed traditional domain controller protocols to legacy workloads. The appropriate mitigation would be: Use Microsoft Entra Domain Services managed domain capabilities for compatible domain join and LDAP/Kerberos workloads. The evidence instead supports “Microsoft Entra ID alone does not supply managed traditional domain controller protocols to legacy workloads”.
B:The alternative diagnosis “The hybrid identity provisioning path between AD and Entra is missing or not healthy” does not match the observed symptom: An application cannot use NTLM/Kerberos because only cloud-native Entra authentication is configured. Context: A tenant contains legacy VMs that require LDAP/Kerberos domain join but administrators do not want to operate domain controllers. The recorded behavior follows from: Microsoft Entra ID alone does not supply managed traditional domain controller protocols to legacy workloads. The appropriate mitigation would be: Use Microsoft Entra Domain Services managed domain capabilities for compatible domain join and LDAP/Kerberos workloads. The evidence instead supports “Microsoft Entra ID alone does not supply managed traditional domain controller protocols to legacy workloads”.
C:The alternative diagnosis “External collaboration was treated as a permanent internal employee account rather than a governed guest identity” does not match the observed symptom: An application cannot use NTLM/Kerberos because only cloud-native Entra authentication is configured. Context: A tenant contains legacy VMs that require LDAP/Kerberos domain join but administrators do not want to operate domain controllers. The recorded behavior follows from: Microsoft Entra ID alone does not supply managed traditional domain controller protocols to legacy workloads. The appropriate mitigation would be: Use Microsoft Entra Domain Services managed domain capabilities for compatible domain join and LDAP/Kerberos workloads. The evidence instead supports “Microsoft Entra ID alone does not supply managed traditional domain controller protocols to legacy workloads”.
Question 144
The design change is: Use Microsoft Entra Domain Services managed domain capabilities for compatible domain join and LDAP/Kerberos workloads. The original failure was: An application cannot use NTLM/Kerberos because only cloud-native Entra authentication is configured. Which ongoing control best prevents recurrence of the same root cause?
- Monitor connector health, published app preauthentication and Conditional Access exclusions.
- Require guest access reviews and expiration/removal when the contractual engagement ends.
- Track managed-domain synchronization and secure LDAP exposure and access controls.
- Monitor sync health and privileged account filtering during directory topology changes.
Explanation
Correct Answer
C:This is an ongoing protection specific to the fault: Track managed-domain synchronization and secure LDAP exposure and access controls. The recurrence risk is: Microsoft Entra ID alone does not supply managed traditional domain controller protocols to legacy workloads. It should be checked using: Join a test VM and verify domain authentication while confirming domain controllers are service-managed.
Incorrect Answers
A:The alternative diagnosis “Monitor connector health, published app preauthentication and Conditional Access exclusions” does not match the observed symptom: The design change is: Use Microsoft Entra Domain Services managed domain capabilities for compatible domain join and LDAP/Kerberos workloads. The original failure was: An application cannot use NTLM/Kerberos because only cloud-native Entra authentication is configured. Which ongoing control best prevents recurrence of the same root cause?. This is an ongoing protection specific to the fault: Track managed-domain synchronization and secure LDAP exposure and access controls. The recurrence risk is: Microsoft Entra ID alone does not supply managed traditional domain controller protocols to legacy workloads. The evidence instead supports “Track managed-domain synchronization and secure LDAP exposure and access controls”.
B:The alternative diagnosis “Require guest access reviews and expiration/removal when the contractual engagement ends” does not match the observed symptom: The design change is: Use Microsoft Entra Domain Services managed domain capabilities for compatible domain join and LDAP/Kerberos workloads. The original failure was: An application cannot use NTLM/Kerberos because only cloud-native Entra authentication is configured. Which ongoing control best prevents recurrence of the same root cause?. This is an ongoing protection specific to the fault: Track managed-domain synchronization and secure LDAP exposure and access controls. The recurrence risk is: Microsoft Entra ID alone does not supply managed traditional domain controller protocols to legacy workloads. The evidence instead supports “Track managed-domain synchronization and secure LDAP exposure and access controls”.
D:The alternative diagnosis “Monitor sync health and privileged account filtering during directory topology changes” does not match the observed symptom: The design change is: Use Microsoft Entra Domain Services managed domain capabilities for compatible domain join and LDAP/Kerberos workloads. The original failure was: An application cannot use NTLM/Kerberos because only cloud-native Entra authentication is configured. Which ongoing control best prevents recurrence of the same root cause?. This is an ongoing protection specific to the fault: Track managed-domain synchronization and secure LDAP exposure and access controls. The recurrence risk is: Microsoft Entra ID alone does not supply managed traditional domain controller protocols to legacy workloads. The evidence instead supports “Track managed-domain synchronization and secure LDAP exposure and access controls”.
Question 145
A design workshop has this requirement: A company needs quarterly certification of guest access to a sensitive finance group, with automatic removal of rejected memberships. Operators currently observe: Former contractors remain group members after repeated manual spreadsheet audits. Select the ONE design remedy that best addresses the root cause.
- Enable assignment required on the enterprise application and assign only authorized users or groups to permitted app roles.
- Use Microsoft Entra B2B collaboration with an approved guest invitation and application-level assignment or access package.
- Use Azure Key Vault Managed HSM and its supported key policies or access roles for the signing workload.
- Use Entra ID Governance access reviews with an appropriate reviewer, recurrence and auto-apply result configuration.
Explanation
Correct Answer
D:This option addresses the actual design defect: There is no automated time-based group entitlement review/remediation process. The correction is: Use Entra ID Governance access reviews with an appropriate reviewer, recurrence and auto-apply result configuration. Confirm the outcome with: Run a review cycle and verify a denied membership is removed according to its configured settings.
Incorrect Answers
A:The alternative diagnosis “Enable assignment required on the enterprise application and assign only authorized users or groups to permitted app roles” does not match the observed symptom: Former contractors remain group members after repeated manual spreadsheet audits. This option addresses the actual design defect: There is no automated time-based group entitlement review/remediation process. The correction is: Use Entra ID Governance access reviews with an appropriate reviewer, recurrence and auto-apply result configuration. The evidence instead supports “Use Entra ID Governance access reviews with an appropriate reviewer, recurrence and auto-apply result configuration”.
B:The alternative diagnosis “Use Microsoft Entra B2B collaboration with an approved guest invitation and application-level assignment or access package” does not match the observed symptom: Former contractors remain group members after repeated manual spreadsheet audits. This option addresses the actual design defect: There is no automated time-based group entitlement review/remediation process. The correction is: Use Entra ID Governance access reviews with an appropriate reviewer, recurrence and auto-apply result configuration. The evidence instead supports “Use Entra ID Governance access reviews with an appropriate reviewer, recurrence and auto-apply result configuration”.
C:The alternative diagnosis “Use Azure Key Vault Managed HSM and its supported key policies or access roles for the signing workload” does not match the observed symptom: Former contractors remain group members after repeated manual spreadsheet audits. This option addresses the actual design defect: There is no automated time-based group entitlement review/remediation process. The correction is: Use Entra ID Governance access reviews with an appropriate reviewer, recurrence and auto-apply result configuration. The evidence instead supports “Use Entra ID Governance access reviews with an appropriate reviewer, recurrence and auto-apply result configuration”.
Question 146
The planned architecture is: Use Entra ID Governance access reviews with an appropriate reviewer, recurrence and auto-apply result configuration. Workload context: A company needs quarterly certification of guest access to a sensitive finance group, with automatic removal of rejected memberships. Which acceptance test demonstrates that the required behavior works?
- Test sign-in as an unassigned user and as an assigned group member to confirm the boundary.
- Run a review cycle and verify a denied membership is removed according to its configured settings.
- Create or use a key in the managed HSM and verify signing operations without private key export.
- Invite the vendor and verify access only to the approved app under the tenant's external collaboration policies.
Explanation
Correct Answer
B:The acceptance test is specific: Run a review cycle and verify a denied membership is removed according to its configured settings. Its purpose is to establish that the proposed architecture works: Use Entra ID Governance access reviews with an appropriate reviewer, recurrence and auto-apply result configuration.
Incorrect Answers
A:Testing sign-in as an unassigned user and as an assigned group member to confirm the boundary would not run a review cycle and verify a denied membership is removed according to its configured settings.
C:The alternative test targets: Use Azure Key Vault Managed HSM and its supported key policies or access roles for the signing workload. The scenario's actual proposed remedy is: Use Entra ID Governance access reviews with an appropriate reviewer, recurrence and auto-apply result configuration. Verify that one by: Run a review cycle and verify a denied membership is removed according to its configured settings.
D:Its purpose is to establish that the proposed architecture works: Use Entra ID Governance access reviews with an appropriate reviewer, recurrence and auto-apply result configuration.
Question 147
The customer states: A company needs quarterly certification of guest access to a sensitive finance group, with automatic removal of rejected memberships. An incident reveals: Former contractors remain group members after repeated manual spreadsheet audits. What cause best accounts for this evidence?
- There is no automated time-based group entitlement review/remediation process.
- The security boundary does not enforce non-exportable managed-HSM key operations.
- The app allows unsolicited user sign-in when assignment gating is not enforced.
- External collaboration was treated as a permanent internal employee account rather than a governed guest identity.
Explanation
Correct Answer
A:The incident is explained by: There is no automated time-based group entitlement review/remediation process. The reported symptom is: Former contractors remain group members after repeated manual spreadsheet audits. The corresponding design fix is: Use Entra ID Governance access reviews with an appropriate reviewer, recurrence and auto-apply result configuration.
Incorrect Answers
B:The security boundary does not enforce non-exportable managed-HSM key operations. There is no automated time-based group entitlement review/remediation process.
C:The app allows unsolicited user sign-in when assignment gating is not enforced. There is no automated time-based group entitlement review/remediation process.
D:External collaboration was treated as a permanent internal employee account rather than a governed guest identity. There is no automated time-based group entitlement review/remediation process.
Question 148
Workload context: A company needs quarterly certification of guest access to a sensitive finance group, with automatic removal of rejected memberships. The implemented remedy is: Use Entra ID Governance access reviews with an appropriate reviewer, recurrence and auto-apply result configuration. Which ongoing practice most specifically prevents recurrence of this failure: Former contractors remain group members after repeated manual spreadsheet audits.?
- Review HSM activation, RBAC and key-rotation/audit events for authorized users.
- Require guest access reviews and expiration/removal when the contractual engagement ends.
- Audit group membership and application role mappings after business unit reorganizations.
- Inspect review completion and apply results after reviewer changes.
Explanation
Correct Answer
D:The preventive control is: Inspect review completion and apply results after reviewer changes. It targets the earlier cause: There is no automated time-based group entitlement review/remediation process. Confirm ongoing effectiveness by: Run a review cycle and verify a denied membership is removed according to its configured settings.
Incorrect Answers
A:It targets the earlier cause: There is no automated time-based group entitlement review/remediation process.
B:Requiring guest access reviews and expiration/removal when the contractual engagement ends would not inspect review completion and apply results after reviewer changes.
C:Auditing group membership and application role mappings after business unit reorganizations would not inspect review completion and apply results after reviewer changes.
Question 149
A solution architect is reviewing a workload: An application connects from a locked-down subnet to Azure Key Vault; public network access must remain disabled. The observed incident is: The app reports DNS or connectivity failure after Key Vault public endpoints are disabled. Which architecture choice most directly removes the identified weakness?
- Use Azure Key Vault Managed HSM and its supported key policies or access roles for the signing workload.
- Grant the service principal the appropriate Key Vault RBAC data-plane role at the vault scope and use approved network controls.
- Provide a Key Vault private endpoint and correct private DNS zone integration and apply allowed RBAC and firewall settings.
- Enable and enforce appropriate Key Vault soft-delete and purge protection policies and a controlled retention window.
Explanation
Correct Answer
C:This option addresses the actual design defect: Private endpoint connectivity and private DNS were not established for the vault. The correction is: Provide a Key Vault private endpoint and correct private DNS zone integration and apply allowed RBAC and firewall settings. Confirm the outcome with: Resolve the vault hostname to a private IP and successfully fetch an approved secret from the subnet.
Incorrect Answers
A:The problem is not generic resource availability: The security boundary does not enforce non-exportable managed-HSM key operations. This option addresses the actual design defect: Private endpoint connectivity and private DNS were not established for the vault.
B:The design that removes it is: Grant the service principal the appropriate Key Vault RBAC data-plane role at the vault scope and use approved network controls. This option addresses the actual design defect: Private endpoint connectivity and private DNS were not established for the vault.
D:The design that removes it is: Enable and enforce appropriate Key Vault soft-delete and purge protection policies and a controlled retention window. This option addresses the actual design defect: Private endpoint connectivity and private DNS were not established for the vault.
Question 150
An architect proposes this change: Provide a Key Vault private endpoint and correct private DNS zone integration and apply allowed RBAC and firewall settings. The workload context is: An application connects from a locked-down subnet to Azure Key Vault; public network access must remain disabled. Which evidence would most directly validate the change?
- Create or use a key in the managed HSM and verify signing operations without private key export.
- Resolve the vault hostname to a private IP and successfully fetch an approved secret from the subnet.
- Obtain an application token and test writing a permitted secret while confirming an unrelated vault is denied.
- Delete a test secret and confirm recovery is available while immediate purge is blocked during retention.
Explanation
Correct Answer
B:The decisive evidence is: Resolve the vault hostname to a private IP and successfully fetch an approved secret from the subnet. This measures the mechanism of the planned change, not an unrelated Azure service: Provide a Key Vault private endpoint and correct private DNS zone integration and apply allowed RBAC and firewall settings.
Incorrect Answers
A:That observation pertains to a separate failure: An audit finds sensitive signing keys exported into general-purpose application configuration. Its cause is: The security boundary does not enforce non-exportable managed-HSM key operations. It does not confirm the result of this design. The direct proof would be: Resolve the vault hostname to a private IP and successfully fetch an approved secret from the subnet.
C:The decisive evidence is: Resolve the vault hostname to a private IP and successfully fetch an approved secret from the subnet.
D:That observation pertains to a separate failure: A deleted secret cannot be recovered after an administrator permanently purges it. Its cause is: Vault deletion safeguards or retention policies were not enforced for critical secrets. It does not confirm the result of this design. The direct proof would be: Resolve the vault hostname to a private IP and successfully fetch an approved secret from the subnet.
Designing Microsoft Azure Infrastructure Solutions (AZ-305) Practice Tests