Question 170An acquired company has duplicate usernames across forests and proposes mapping accounts solely by display name during hybrid identity consolidation. Which technical distinction is decisive in this case? 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. Names are mutable and nonunique; hybrid identity synchronization needs correct object association. Hybrid identity depends on a functioning synchronization or federation path between on-premises identity and cloud services. ExplanationCorrect Answer C:Names are mutable and nonunique; hybrid identity synchronization needs correct object association. This is the principle behind: Design a supported unique identity matching and synchronization strategy using stable identifiers. The evidence to inspect is: Match a test user with a duplicate display name and verify its cloud object is not merged with another person. Other Answers A:Traditional AD DS domain control and Entra cloud identity are related but distinct services with different capabilities. By contrast, names are mutable and nonunique; hybrid identity synchronization needs correct object association. B:Hybrid cloud authorization needs the relevant user and group representation in the target directory. In the stated system, names are mutable and nonunique; hybrid identity synchronization needs correct object association. D:Hybrid identity depends on a functioning synchronization or federation path between on-premises identity and cloud services. In the stated system, names are mutable and nonunique; hybrid identity synchronization needs correct object association.
Question 171An acquired company has duplicate usernames across forests and proposes mapping accounts solely by display name during hybrid identity consolidation. Which observation best validates the chosen approach? Match a test user with a duplicate display name and verify its cloud object is not merged with another person. Test local domain authentication and cloud token sign-in separately using a synchronized user. 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. ExplanationCorrect Answer A:Match a test user with a duplicate display name and verify its cloud object is not merged with another person. This test checks the expected result of: Design a supported unique identity matching and synchronization strategy using stable identifiers. It matters because: Names are mutable and nonunique; hybrid identity synchronization needs correct object association. Other Answers B:Traditional AD DS domain control and Entra cloud identity are related but distinct services with different capabilities. The relevant acceptance check is to match a test user with a duplicate display name and verify its cloud object is not merged with another person. C:Hybrid cloud authorization needs the relevant user and group representation in the target directory. The failure is checked more directly by a test to match a test user with a duplicate display name and verify its cloud object is not merged with another person. D:Hybrid identity depends on a functioning synchronization or federation path between on-premises identity and cloud services. Proving this correction calls for a check to match a test user with a duplicate display name and verify its cloud object is not merged with another person.
Question 172An acquired company has duplicate usernames across forests and proposes mapping accounts solely by display name during hybrid identity consolidation. Which governance action most directly addresses the recurring risk? Review synchronization rules and conflict reports before adding forests. Alert on directory sync failures and investigate identity propagation delays. Maintain a supported hybrid identity design with explicit dependency ownership. Monitor synchronization scoping and provisioning failures for access-critical groups. ExplanationCorrect Answer A:Review synchronization rules and conflict reports before adding forests. Maintaining this control reduces recurrence because: Names are mutable and nonunique; hybrid identity synchronization needs correct object association. The immediate response remains: Design a supported unique identity matching and synchronization strategy using stable identifiers. Other Answers B:Hybrid identity depends on a functioning synchronization or federation path between on-premises identity and cloud services. A more direct preventive measure is to review synchronization rules and conflict reports before adding forests. C:Traditional AD DS domain control and Entra cloud identity are related but distinct services with different capabilities. The stronger recurring control is to review synchronization rules and conflict reports before adding forests. D:Hybrid cloud authorization needs the relevant user and group representation in the target directory. Reducing this risk requires a practice to review synchronization rules and conflict reports before adding forests.
Question 173A scheduled analytics process keeps running after its developer leaves because it uses an untracked personal account with a permanent password. Which action most directly resolves the security or identity requirement? 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. Register the application and grant only the requested Microsoft Entra app permissions through a controlled consent process. Give the process a governed workload identity and remove dependency on the departed developer. ExplanationCorrect Answer D:An employee account lifecycle must not silently control a production application's unattended identity. To confirm, disable the developer and verify the process uses its registered workload identity with the required scope. Other Answers A:Nonhuman automation identities need unique accountability, authorization, and lifecycle management. A more relevant action is to give the process a governed workload identity and remove dependency on the departed developer. B:Workload identities authenticate software and automation independently from a human user's lifecycle. The required change instead is to give the process a governed workload identity and remove dependency on the departed developer. C:Application permissions are distinct from tenant-wide administration, and consent scope determines what the app can do. This failure calls for a decision to give the process a governed workload identity and remove dependency on the departed developer.
Question 174A scheduled analytics process keeps running after its developer leaves because it uses an untracked personal account with a permanent password. 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. Nonhuman automation identities need unique accountability, authorization, and lifecycle management. Workload identities authenticate software and automation independently from a human user's lifecycle. An employee account lifecycle must not silently control a production application's unattended identity. ExplanationCorrect Answer D:An employee account lifecycle must not silently control a production application's unattended identity. This is the principle behind: Give the process a governed workload identity and remove dependency on the departed developer. The evidence to inspect is: Disable the developer and verify the process uses its registered workload identity with the required scope. Other Answers A:Application permissions are distinct from tenant-wide administration, and consent scope determines what the app can do. By contrast, an employee account lifecycle must not silently control a production application's unattended identity. B:Nonhuman automation identities need unique accountability, authorization, and lifecycle management. In the stated system, an employee account lifecycle must not silently control a production application's unattended identity. C:Workload identities authenticate software and automation independently from a human user's lifecycle. By contrast, an employee account lifecycle must not silently control a production application's unattended identity.
Question 175A scheduled analytics process keeps running after its developer leaves because it uses an untracked personal account with a permanent password. Which observation best validates the chosen approach? Disable the developer and verify the process uses its registered workload identity with the required scope. Inspect granted API scopes and verify an unrelated API remains inaccessible. Disable the employee account and confirm the automated job still authenticates as its own principal. Trace an agent request to its own identity and verify its permissions do not exceed the assigned task. ExplanationCorrect Answer A:Disable the developer and verify the process uses its registered workload identity with the required scope. This test checks the expected result of: Give the process a governed workload identity and remove dependency on the departed developer. It matters because: An employee account lifecycle must not silently control a production application's unattended identity. Other Answers B:Application permissions are distinct from tenant-wide administration, and consent scope determines what the app can do. Proving this correction calls for a check to disable the developer and verify the process uses its registered workload identity with the required scope. C:Workload identities authenticate software and automation independently from a human user's lifecycle. A more meaningful verification is to disable the developer and verify the process uses its registered workload identity with the required scope. D:Nonhuman automation identities need unique accountability, authorization, and lifecycle management. The relevant acceptance check is to disable the developer and verify the process uses its registered workload identity with the required scope.
Question 176A scheduled analytics process keeps running after its developer leaves because it uses an untracked personal account with a permanent password. Which governance action most directly addresses the recurring risk? Catalog service principals and assign owners independent of any one employee. Include agent and workload principals in identity inventory, access reviews and offboarding. Enforce application consent reviews and least-privilege service principal grants. Prohibit user passwords in unattended jobs and audit nonhuman app identities. ExplanationCorrect Answer A:Catalog service principals and assign owners independent of any one employee. Maintaining this control reduces recurrence because: An employee account lifecycle must not silently control a production application's unattended identity. The immediate response remains: Give the process a governed workload identity and remove dependency on the departed developer. Other Answers B:Nonhuman automation identities need unique accountability, authorization, and lifecycle management. The stronger recurring control is to catalog service principals and assign owners independent of any one employee. C:Application permissions are distinct from tenant-wide administration, and consent scope determines what the app can do. A more direct preventive measure is to catalog service principals and assign owners independent of any one employee. D:Workload identities authenticate software and automation independently from a human user's lifecycle. The lasting safeguard is to catalog service principals and assign owners independent of any one employee.
Question 177A collaboration application asks a cross-tenant guest to authenticate but the admins incorrectly assume inviting the guest automatically grants every site permission. Which action most directly resolves the security or identity requirement? Distinguish Entra directory roles from Azure resource RBAC assignments. Use Microsoft Entra B2B collaboration identities with scoped resource invitations. Grant only the specific application and resource permissions that the guest needs. Register the application and grant only the requested Microsoft Entra app permissions through a controlled consent process. ExplanationCorrect Answer C:Entra B2B directory presence and resource authorization are separate trust decisions. To confirm, check sign-in succeeded and that unassigned Teams or SharePoint resources remain unavailable. Other Answers A:Directory administration and Azure resource permissions are separate authorization planes. The required change instead is to grant only the specific application and resource permissions that the guest needs. B:External guest identities support collaboration without turning every invited partner into a normal internal employee identity. A more relevant action is to grant only the specific application and resource permissions that the guest needs. D:Application permissions are distinct from tenant-wide administration, and consent scope determines what the app can do. The corrective action for this requirement is to grant only the specific application and resource permissions that the guest needs.
Question 178A collaboration application asks a cross-tenant guest to authenticate but the admins incorrectly assume inviting the guest automatically grants every site permission. Which technical distinction is decisive in this case? Entra B2B directory presence and resource authorization are separate trust decisions. External guest identities support collaboration without turning every invited partner into a normal internal employee identity. Application permissions are distinct from tenant-wide administration, and consent scope determines what the app can do. Directory administration and Azure resource permissions are separate authorization planes. ExplanationCorrect Answer A:Entra B2B directory presence and resource authorization are separate trust decisions. This is the principle behind: Grant only the specific application and resource permissions that the guest needs. The evidence to inspect is: Check sign-in succeeded and that unassigned Teams or SharePoint resources remain unavailable. Other Answers B:External guest identities support collaboration without turning every invited partner into a normal internal employee identity. By contrast, entra B2B directory presence and resource authorization are separate trust decisions. C:Application permissions are distinct from tenant-wide administration, and consent scope determines what the app can do. By contrast, entra B2B directory presence and resource authorization are separate trust decisions. D:Directory administration and Azure resource permissions are separate authorization planes. In the stated system, entra B2B directory presence and resource authorization are separate trust decisions.
Question 179A collaboration application asks a cross-tenant guest to authenticate but the admins incorrectly assume inviting the guest automatically grants every site permission. Which observation best validates the chosen approach? Invite a test partner and confirm its directory user type and limited access to an approved team. Compare a test user's directory-role capabilities with its subscription-resource access. Inspect granted API scopes and verify an unrelated API remains inaccessible. Check sign-in succeeded and that unassigned Teams or SharePoint resources remain unavailable. ExplanationCorrect Answer D:Check sign-in succeeded and that unassigned Teams or SharePoint resources remain unavailable. This test checks the expected result of: Grant only the specific application and resource permissions that the guest needs. It matters because: Entra B2B directory presence and resource authorization are separate trust decisions. Other Answers A:External guest identities support collaboration without turning every invited partner into a normal internal employee identity. The relevant acceptance check is to check sign-in succeeded and that unassigned Teams or SharePoint resources remain unavailable. B:Directory administration and Azure resource permissions are separate authorization planes. A more meaningful verification is to check sign-in succeeded and that unassigned Teams or SharePoint resources remain unavailable. C:Application permissions are distinct from tenant-wide administration, and consent scope determines what the app can do. The failure is checked more directly by a test to check sign-in succeeded and that unassigned Teams or SharePoint resources remain unavailable.
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.