Question 120A contractor changes departments and an internal application keeps access based solely on a stale locally copied employee table. Which governance action most directly addresses the recurring risk? Automate contractor access removal with termination workflows. Use identity lifecycle integrations and periodic stale-access reviews. Rotate trust keys and review cross-organization sign-in agreements. Protect group ownership and membership changes with approvals. ExplanationCorrect Answer B:Use identity lifecycle integrations and periodic stale-access reviews. Maintaining this control reduces recurrence because: Directory-backed identity and current entitlements prevent abandoned local copies from retaining obsolete access decisions. The immediate response remains: Refresh identity and entitlement data from an authoritative directory source with appropriate lifecycle hooks. Other Answers A:Changing credentials does not confer or remove role-based authorization by itself. A more direct preventive measure is to use identity lifecycle integrations and periodic stale-access reviews. C:Federated identity preserves the home organization's authentication while enabling delegated trust for the target application. A more direct preventive measure is to use identity lifecycle integrations and periodic stale-access reviews. D:Directory attributes and groups support access decisions only after a trusted identity is established. A more direct preventive measure is to use identity lifecycle integrations and periodic stale-access reviews.
Question 121An enterprise wants one cloud directory to authenticate staff to Microsoft 365 and custom SaaS without configuring a separate local Active Directory forest for each app. Which action most directly resolves the security or identity requirement? Monitor the supported hybrid identity synchronization and sign-in configuration. Use Microsoft Entra ID as the cloud identity provider for supported applications. Select the documented hybrid Entra/AD DS integration suitable to domain and cloud sign-in requirements. Verify the group is included and correctly synchronized or provisioned before using it in cloud access assignments. ExplanationCorrect Answer B:Entra ID manages cloud users, groups, apps, and access tokens, unlike a traditional local domain controller. To confirm, sign in to two registered cloud applications with one organizational account and review tokens. Other Answers A:Hybrid identity depends on a functioning synchronization or federation path between on-premises identity and cloud services. A more relevant action is to use Microsoft Entra ID as the cloud identity provider for supported applications. C:Traditional AD DS domain control and Entra cloud identity are related but distinct services with different capabilities. This failure calls for a decision to use Microsoft Entra ID as the cloud identity provider for supported applications. D:Hybrid cloud authorization needs the relevant user and group representation in the target directory. The required change instead is to use Microsoft Entra ID as the cloud identity provider for supported applications.
Question 122An enterprise wants one cloud directory to authenticate staff to Microsoft 365 and custom SaaS without configuring a separate local Active Directory forest for each app. Which technical distinction is decisive in this case? Hybrid identity depends on a functioning synchronization or federation path between on-premises identity and cloud services. Traditional AD DS domain control and Entra cloud identity are related but distinct services with different capabilities. Hybrid cloud authorization needs the relevant user and group representation in the target directory. Entra ID manages cloud users, groups, apps, and access tokens, unlike a traditional local domain controller. ExplanationCorrect Answer D:Entra ID manages cloud users, groups, apps, and access tokens, unlike a traditional local domain controller. This is the principle behind: Use Microsoft Entra ID as the cloud identity provider for supported applications. The evidence to inspect is: Sign in to two registered cloud applications with one organizational account and review tokens. Other Answers A:Hybrid identity depends on a functioning synchronization or federation path between on-premises identity and cloud services. By contrast, entra ID manages cloud users, groups, apps, and access tokens, unlike a traditional local domain controller. B:Traditional AD DS domain control and Entra cloud identity are related but distinct services with different capabilities. In the stated system, entra ID manages cloud users, groups, apps, and access tokens, unlike a traditional local domain controller. C:Hybrid cloud authorization needs the relevant user and group representation in the target directory. In the stated system, entra ID manages cloud users, groups, apps, and access tokens, unlike a traditional local domain controller.
Question 123An enterprise wants one cloud directory to authenticate staff to Microsoft 365 and custom SaaS without configuring a separate local Active Directory forest for each app. Which observation best validates the chosen approach? Check a synchronized group's object membership in Entra and attempt a resource access as an assigned member. Sign in to two registered cloud applications with one organizational account and review tokens. Test local domain authentication and cloud token sign-in separately using a synchronized user. Change an approved test user's attribute and verify the cloud representation and sign-in outcome. ExplanationCorrect Answer B:Sign in to two registered cloud applications with one organizational account and review tokens. This test checks the expected result of: Use Microsoft Entra ID as the cloud identity provider for supported applications. It matters because: Entra ID manages cloud users, groups, apps, and access tokens, unlike a traditional local domain controller. Other Answers A:Hybrid cloud authorization needs the relevant user and group representation in the target directory. Proving this correction calls for a check to sign in to two registered cloud applications with one organizational account and review tokens. C:Traditional AD DS domain control and Entra cloud identity are related but distinct services with different capabilities. The failure is checked more directly by a test to sign in to two registered cloud applications with one organizational account and review tokens. D:Hybrid identity depends on a functioning synchronization or federation path between on-premises identity and cloud services. A more meaningful verification is to sign in to two registered cloud applications with one organizational account and review tokens.
Question 124An enterprise wants one cloud directory to authenticate staff to Microsoft 365 and custom SaaS without configuring a separate local Active Directory forest for each app. Which governance action most directly addresses the recurring risk? Maintain a supported hybrid identity design with explicit dependency ownership. Monitor synchronization scoping and provisioning failures for access-critical groups. Alert on directory sync failures and investigate identity propagation delays. Govern enterprise app registrations and identity assignments centrally. ExplanationCorrect Answer D:Govern enterprise app registrations and identity assignments centrally. Maintaining this control reduces recurrence because: Entra ID manages cloud users, groups, apps, and access tokens, unlike a traditional local domain controller. The immediate response remains: Use Microsoft Entra ID as the cloud identity provider for supported applications. Other Answers A:Traditional AD DS domain control and Entra cloud identity are related but distinct services with different capabilities. The lasting safeguard is to govern enterprise app registrations and identity assignments centrally. B:Hybrid cloud authorization needs the relevant user and group representation in the target directory. The stronger recurring control is to govern enterprise app registrations and identity assignments centrally. C:Hybrid identity depends on a functioning synchronization or federation path between on-premises identity and cloud services. Reducing this risk requires a practice to govern enterprise app registrations and identity assignments centrally.
Question 125A manufacturer registers a nightly Azure automation and gives it an employee's password for unattended access to a storage service. Which action most directly resolves the security or identity requirement? Move workload authentication to managed or federated credentials where supported, and revoke the exposed secret. Classify the agent as a governed workload or agent identity and apply the supported nonhuman identity controls. Assign a supported service principal or managed identity with only required resource permissions. Create a dedicated app registration and service principal with approved Microsoft Graph permissions. ExplanationCorrect Answer C:Workload identities authenticate software and automation independently from a human user's lifecycle. To confirm, disable the employee account and confirm the automated job still authenticates as its own principal. Other Answers A:Workload identities and federated credentials avoid distributing long-lived app passwords to repositories. The corrective action for this requirement is to assign a supported service principal or managed identity with only required resource permissions. B:Nonhuman automation identities need unique accountability, authorization, and lifecycle management. The required change instead is to assign a supported service principal or managed identity with only required resource permissions. D:An application principal represents software rather than an employee signing in interactively. The corrective action for this requirement is to assign a supported service principal or managed identity with only required resource permissions.
Question 126A manufacturer registers a nightly Azure automation and gives it an employee's password for unattended access to a storage service. Which technical distinction is decisive in this case? Workload identities and federated credentials avoid distributing long-lived app passwords to repositories. Nonhuman automation identities need unique accountability, authorization, and lifecycle management. An application principal represents software rather than an employee signing in interactively. Workload identities authenticate software and automation independently from a human user's lifecycle. ExplanationCorrect Answer D:Workload identities authenticate software and automation independently from a human user's lifecycle. This is the principle behind: Assign a supported service principal or managed identity with only required resource permissions. The evidence to inspect is: Disable the employee account and confirm the automated job still authenticates as its own principal. Other Answers A:Workload identities and federated credentials avoid distributing long-lived app passwords to repositories. By contrast, workload identities authenticate software and automation independently from a human user's lifecycle. B:Nonhuman automation identities need unique accountability, authorization, and lifecycle management. In the stated system, workload identities authenticate software and automation independently from a human user's lifecycle. C:An application principal represents software rather than an employee signing in interactively. By contrast, workload identities authenticate software and automation independently from a human user's lifecycle.
Question 127A manufacturer registers a nightly Azure automation and gives it an employee's password for unattended access to a storage service. Which observation best validates the chosen approach? Run the job without the old secret and verify the leaked credential is rejected. Observe client-credential token issuance and deny access when the app permission is removed. Trace an agent request to its own identity and verify its permissions do not exceed the assigned task. Disable the employee account and confirm the automated job still authenticates as its own principal. ExplanationCorrect Answer D:Disable the employee account and confirm the automated job still authenticates as its own principal. This test checks the expected result of: Assign a supported service principal or managed identity with only required resource permissions. It matters because: Workload identities authenticate software and automation independently from a human user's lifecycle. Other Answers A:Workload identities and federated credentials avoid distributing long-lived app passwords to repositories. The failure is checked more directly by a test to disable the employee account and confirm the automated job still authenticates as its own principal. B:An application principal represents software rather than an employee signing in interactively. The failure is checked more directly by a test to disable the employee account and confirm the automated job still authenticates as its own principal. C:Nonhuman automation identities need unique accountability, authorization, and lifecycle management. A more meaningful verification is to disable the employee account and confirm the automated job still authenticates as its own principal.
Question 128A manufacturer registers a nightly Azure automation and gives it an employee's password for unattended access to a storage service. Which governance action most directly addresses the recurring risk? Use secret scanning and enforce short-lived identity federation for build systems. Prohibit user passwords in unattended jobs and audit nonhuman app identities. Use application permission governance and service principal credential rotation. Include agent and workload principals in identity inventory, access reviews and offboarding. ExplanationCorrect Answer B:Prohibit user passwords in unattended jobs and audit nonhuman app identities. Maintaining this control reduces recurrence because: Workload identities authenticate software and automation independently from a human user's lifecycle. The immediate response remains: Assign a supported service principal or managed identity with only required resource permissions. Other Answers A:Workload identities and federated credentials avoid distributing long-lived app passwords to repositories. The lasting safeguard is to prohibit user passwords in unattended jobs and audit nonhuman app identities. C:An application principal represents software rather than an employee signing in interactively. The lasting safeguard is to prohibit user passwords in unattended jobs and audit nonhuman app identities. D:Nonhuman automation identities need unique accountability, authorization, and lifecycle management. Reducing this risk requires a practice to prohibit user passwords in unattended jobs and audit nonhuman app identities.
Question 129A hosted web API needs to call Key Vault from an Azure-managed compute resource without storing any client secret in its deployment package. Which action most directly resolves the security or identity requirement? Use an Azure managed identity with an authorized Key Vault role. Assign a supported service principal or managed identity with only required resource permissions. Distinguish Entra directory roles from Azure resource RBAC assignments. Move workload authentication to managed or federated credentials where supported, and revoke the exposed secret. ExplanationCorrect Answer A:Managed identities let Azure workloads receive identity tokens without maintaining developer-supplied credentials. To confirm, remove application secrets and test token-based authorized secret retrieval from the running workload. Other Answers B:Workload identities authenticate software and automation independently from a human user's lifecycle. A more relevant action is to use an Azure managed identity with an authorized Key Vault role. C:Directory administration and Azure resource permissions are separate authorization planes. The corrective action for this requirement is to use an Azure managed identity with an authorized Key Vault role. D:Workload identities and federated credentials avoid distributing long-lived app passwords to repositories. The required change instead is to use an Azure managed identity with an authorized Key Vault role.
Question 130A hosted web API needs to call Key Vault from an Azure-managed compute resource without storing any client secret in its deployment package. Which technical distinction is decisive in this case? Workload identities and federated credentials avoid distributing long-lived app passwords to repositories. Managed identities let Azure workloads receive identity tokens without maintaining developer-supplied credentials. Workload identities authenticate software and automation independently from a human user's lifecycle. Directory administration and Azure resource permissions are separate authorization planes. ExplanationCorrect Answer B:Managed identities let Azure workloads receive identity tokens without maintaining developer-supplied credentials. This is the principle behind: Use an Azure managed identity with an authorized Key Vault role. The evidence to inspect is: Remove application secrets and test token-based authorized secret retrieval from the running workload. Other Answers A:Workload identities and federated credentials avoid distributing long-lived app passwords to repositories. In the stated system, managed identities let Azure workloads receive identity tokens without maintaining developer-supplied credentials. C:Workload identities authenticate software and automation independently from a human user's lifecycle. In the stated system, managed identities let Azure workloads receive identity tokens without maintaining developer-supplied credentials. D:Directory administration and Azure resource permissions are separate authorization planes. By contrast, managed identities let Azure workloads receive identity tokens without maintaining developer-supplied credentials.