Question 180A collaboration application asks a cross-tenant guest to authenticate but the admins incorrectly assume inviting the guest automatically grants every site permission. Which governance action most directly addresses the recurring risk? Review directory roles and subscription RBAC in separate privileged-access processes. Apply guest access reviews and automatic expiration at project completion. Review external-user access separately from identity invitations. Enforce application consent reviews and least-privilege service principal grants. ExplanationCorrect Answer C:Review external-user access separately from identity invitations. Maintaining this control reduces recurrence because: Entra B2B directory presence and resource authorization are separate trust decisions. The immediate response remains: Grant only the specific application and resource permissions that the guest needs. Other Answers A:Directory administration and Azure resource permissions are separate authorization planes. A more direct preventive measure is to review external-user access separately from identity invitations. B:External guest identities support collaboration without turning every invited partner into a normal internal employee identity. The lasting safeguard is to review external-user access separately from identity invitations. D:Application permissions are distinct from tenant-wide administration, and consent scope determines what the app can do. The stronger recurring control is to review external-user access separately from identity invitations.
Question 181A tenant has hundreds of inactive application registrations with client secrets whose owners are unknown. Which action most directly resolves the security or identity requirement? Create a dedicated app registration and service principal with approved Microsoft Graph permissions. Inventory app registrations and service principals, assign accountable owners, and disable unused credentials. Register the application and grant only the requested Microsoft Entra app permissions through a controlled consent process. Move workload authentication to managed or federated credentials where supported, and revoke the exposed secret. ExplanationCorrect Answer B:Applications and their service principals create identity attack surface even without interactive employees. To confirm, identify an orphaned application and verify its old credential can no longer request tokens. Other Answers A:An application principal represents software rather than an employee signing in interactively. A more relevant action is to inventory app registrations and service principals, assign accountable owners, and disable unused credentials. C:Application permissions are distinct from tenant-wide administration, and consent scope determines what the app can do. A more relevant action is to inventory app registrations and service principals, assign accountable owners, and disable unused credentials. D:Workload identities and federated credentials avoid distributing long-lived app passwords to repositories. A more relevant action is to inventory app registrations and service principals, assign accountable owners, and disable unused credentials.
Question 182A tenant has hundreds of inactive application registrations with client secrets whose owners are unknown. Which technical distinction is decisive in this case? Application permissions are distinct from tenant-wide administration, and consent scope determines what the app can do. An application principal represents software rather than an employee signing in interactively. Applications and their service principals create identity attack surface even without interactive employees. Workload identities and federated credentials avoid distributing long-lived app passwords to repositories. ExplanationCorrect Answer C:Applications and their service principals create identity attack surface even without interactive employees. This is the principle behind: Inventory app registrations and service principals, assign accountable owners, and disable unused credentials. The evidence to inspect is: Identify an orphaned application and verify its old credential can no longer request tokens. Other Answers A:Application permissions are distinct from tenant-wide administration, and consent scope determines what the app can do. In the stated system, applications and their service principals create identity attack surface even without interactive employees. B:An application principal represents software rather than an employee signing in interactively. In the stated system, applications and their service principals create identity attack surface even without interactive employees. D:Workload identities and federated credentials avoid distributing long-lived app passwords to repositories. In the stated system, applications and their service principals create identity attack surface even without interactive employees.
Question 183A tenant has hundreds of inactive application registrations with client secrets whose owners are unknown. Which observation best validates the chosen approach? Run the job without the old secret and verify the leaked credential is rejected. Identify an orphaned application and verify its old credential can no longer request tokens. Observe client-credential token issuance and deny access when the app permission is removed. Inspect granted API scopes and verify an unrelated API remains inaccessible. ExplanationCorrect Answer B:Identify an orphaned application and verify its old credential can no longer request tokens. This test checks the expected result of: Inventory app registrations and service principals, assign accountable owners, and disable unused credentials. It matters because: Applications and their service principals create identity attack surface even without interactive employees. Other Answers A:Workload identities and federated credentials avoid distributing long-lived app passwords to repositories. A more meaningful verification is to identify an orphaned application and verify its old credential can no longer request tokens. C:An application principal represents software rather than an employee signing in interactively. A more meaningful verification is to identify an orphaned application and verify its old credential can no longer request tokens. D:Application permissions are distinct from tenant-wide administration, and consent scope determines what the app can do. A more meaningful verification is to identify an orphaned application and verify its old credential can no longer request tokens.
Question 184A tenant has hundreds of inactive application registrations with client secrets whose owners are unknown. Which governance action most directly addresses the recurring risk? Enforce application consent reviews and least-privilege service principal grants. Require expiration, ownership and lifecycle review for registered applications. Use application permission governance and service principal credential rotation. Use secret scanning and enforce short-lived identity federation for build systems. ExplanationCorrect Answer B:Require expiration, ownership and lifecycle review for registered applications. Maintaining this control reduces recurrence because: Applications and their service principals create identity attack surface even without interactive employees. The immediate response remains: Inventory app registrations and service principals, assign accountable owners, and disable unused credentials. Other Answers A:Application permissions are distinct from tenant-wide administration, and consent scope determines what the app can do. The lasting safeguard is to require expiration, ownership and lifecycle review for registered applications. C:An application principal represents software rather than an employee signing in interactively. The lasting safeguard is to require expiration, ownership and lifecycle review for registered applications. D:Workload identities and federated credentials avoid distributing long-lived app passwords to repositories. The lasting safeguard is to require expiration, ownership and lifecycle review for registered applications.
Question 185A developer assumes a security group automatically exists in the resource's cloud directory because it was created in an isolated on-premises forest. Which action most directly resolves the security or identity requirement? Distinguish Entra directory roles from Azure resource RBAC assignments. Verify the group is included and correctly synchronized or provisioned before using it in cloud access assignments. Use Microsoft Entra ID as the cloud identity provider for supported applications. Monitor the supported hybrid identity synchronization and sign-in configuration. ExplanationCorrect Answer B:Hybrid cloud authorization needs the relevant user and group representation in the target directory. To confirm, check a synchronized group's object membership in Entra and attempt a resource access as an assigned member. Other Answers A:Directory administration and Azure resource permissions are separate authorization planes. This failure calls for a decision to verify the group is included and correctly synchronized or provisioned before using it in cloud access assignments. C:Entra ID manages cloud users, groups, apps, and access tokens, unlike a traditional local domain controller. The required change instead is to verify the group is included and correctly synchronized or provisioned before using it in cloud access assignments. D:Hybrid identity depends on a functioning synchronization or federation path between on-premises identity and cloud services. A more relevant action is to verify the group is included and correctly synchronized or provisioned before using it in cloud access assignments.
Question 186A developer assumes a security group automatically exists in the resource's cloud directory because it was created in an isolated on-premises forest. 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. Entra ID manages cloud users, groups, apps, and access tokens, unlike a traditional local domain controller. Hybrid cloud authorization needs the relevant user and group representation in the target directory. Directory administration and Azure resource permissions are separate authorization planes. ExplanationCorrect Answer C:Hybrid cloud authorization needs the relevant user and group representation in the target directory. This is the principle behind: Verify the group is included and correctly synchronized or provisioned before using it in cloud access assignments. The evidence to inspect is: Check a synchronized group's object membership in Entra and attempt a resource access as an assigned member. Other Answers A:Hybrid identity depends on a functioning synchronization or federation path between on-premises identity and cloud services. In the stated system, hybrid cloud authorization needs the relevant user and group representation in the target directory. B:Entra ID manages cloud users, groups, apps, and access tokens, unlike a traditional local domain controller. In the stated system, hybrid cloud authorization needs the relevant user and group representation in the target directory. D:Directory administration and Azure resource permissions are separate authorization planes. By contrast, hybrid cloud authorization needs the relevant user and group representation in the target directory.
Question 187A developer assumes a security group automatically exists in the resource's cloud directory because it was created in an isolated on-premises forest. Which observation best validates the chosen approach? Sign in to two registered cloud applications with one organizational account and review tokens. Check a synchronized group's object membership in Entra and attempt a resource access as an assigned member. Change an approved test user's attribute and verify the cloud representation and sign-in outcome. Compare a test user's directory-role capabilities with its subscription-resource access. ExplanationCorrect Answer B:Check a synchronized group's object membership in Entra and attempt a resource access as an assigned member. This test checks the expected result of: Verify the group is included and correctly synchronized or provisioned before using it in cloud access assignments. It matters because: Hybrid cloud authorization needs the relevant user and group representation in the target directory. Other Answers A:Entra ID manages cloud users, groups, apps, and access tokens, unlike a traditional local domain controller. Proving this correction calls for a check to check a synchronized group's object membership in Entra and attempt a resource access as an assigned member. C:Hybrid identity depends on a functioning synchronization or federation path between on-premises identity and cloud services. A more meaningful verification is to check a synchronized group's object membership in Entra and attempt a resource access as an assigned member. D:Directory administration and Azure resource permissions are separate authorization planes. The failure is checked more directly by a test to check a synchronized group's object membership in Entra and attempt a resource access as an assigned member.
Question 188A developer assumes a security group automatically exists in the resource's cloud directory because it was created in an isolated on-premises forest. Which governance action most directly addresses the recurring risk? Govern enterprise app registrations and identity assignments centrally. Monitor synchronization scoping and provisioning failures for access-critical groups. Review directory roles and subscription RBAC in separate privileged-access processes. Alert on directory sync failures and investigate identity propagation delays. ExplanationCorrect Answer B:Monitor synchronization scoping and provisioning failures for access-critical groups. Maintaining this control reduces recurrence because: Hybrid cloud authorization needs the relevant user and group representation in the target directory. The immediate response remains: Verify the group is included and correctly synchronized or provisioned before using it in cloud access assignments. Other Answers A:Entra ID manages cloud users, groups, apps, and access tokens, unlike a traditional local domain controller. A more direct preventive measure is to monitor synchronization scoping and provisioning failures for access-critical groups. C:Directory administration and Azure resource permissions are separate authorization planes. Reducing this risk requires a practice to monitor synchronization scoping and provisioning failures for access-critical groups. D:Hybrid identity depends on a functioning synchronization or federation path between on-premises identity and cloud services. The lasting safeguard is to monitor synchronization scoping and provisioning failures for access-critical groups.
Question 189An AI automation team creates a software agent that acts without a human present but records every action under a shared employee identity. Which action most directly resolves the security or identity requirement? Give the process a governed workload identity and remove dependency on the departed developer. 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. Classify the agent as a governed workload or agent identity and apply the supported nonhuman identity controls. ExplanationCorrect Answer D:Nonhuman automation identities need unique accountability, authorization, and lifecycle management. To confirm, trace an agent request to its own identity and verify its permissions do not exceed the assigned task. Other Answers A:An employee account lifecycle must not silently control a production application's unattended identity. This failure calls for a decision to classify the agent as a governed workload or agent identity and apply the supported nonhuman identity controls. B:Workload identities authenticate software and automation independently from a human user's lifecycle. The required change instead is to classify the agent as a governed workload or agent identity and apply the supported nonhuman identity controls. C:An application principal represents software rather than an employee signing in interactively. This failure calls for a decision to classify the agent as a governed workload or agent identity and apply the supported nonhuman identity controls.
Question 190An AI automation team creates a software agent that acts without a human present but records every action under a shared employee identity. Which technical distinction is decisive in this case? Workload identities authenticate software and automation independently from a human user's lifecycle. Nonhuman automation identities need unique accountability, authorization, and lifecycle management. An employee account lifecycle must not silently control a production application's unattended identity. An application principal represents software rather than an employee signing in interactively. ExplanationCorrect Answer B:Nonhuman automation identities need unique accountability, authorization, and lifecycle management. This is the principle behind: Classify the agent as a governed workload or agent identity and apply the supported nonhuman identity controls. The evidence to inspect is: Trace an agent request to its own identity and verify its permissions do not exceed the assigned task. Other Answers A:Workload identities authenticate software and automation independently from a human user's lifecycle. In the stated system, nonhuman automation identities need unique accountability, authorization, and lifecycle management. C:An employee account lifecycle must not silently control a production application's unattended identity. In the stated system, nonhuman automation identities need unique accountability, authorization, and lifecycle management. D:An application principal represents software rather than an employee signing in interactively. In the stated system, nonhuman automation identities need unique accountability, authorization, and lifecycle management.