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.
Question 131A hosted web API needs to call Key Vault from an Azure-managed compute resource without storing any client secret in its deployment package. Which observation best validates the chosen approach? Run the job without the old secret and verify the leaked credential is rejected. Disable the employee account and confirm the automated job still authenticates as its own principal. Remove application secrets and test token-based authorized secret retrieval from the running workload. Compare a test user's directory-role capabilities with its subscription-resource access. ExplanationCorrect Answer C:Remove application secrets and test token-based authorized secret retrieval from the running workload. This test checks the expected result of: Use an Azure managed identity with an authorized Key Vault role. It matters because: Managed identities let Azure workloads receive identity tokens without maintaining developer-supplied credentials. Other Answers A:Workload identities and federated credentials avoid distributing long-lived app passwords to repositories. The relevant acceptance check is to remove application secrets and test token-based authorized secret retrieval from the running workload. B:Workload identities authenticate software and automation independently from a human user's lifecycle. The failure is checked more directly by a test to remove application secrets and test token-based authorized secret retrieval from the running workload. D:Directory administration and Azure resource permissions are separate authorization planes. Proving this correction calls for a check to remove application secrets and test token-based authorized secret retrieval from the running workload.
Question 132A hosted web API needs to call Key Vault from an Azure-managed compute resource without storing any client secret in its deployment package. Which governance action most directly addresses the recurring risk? Prohibit user passwords in unattended jobs and audit nonhuman app identities. Review directory roles and subscription RBAC in separate privileged-access processes. Use secret scanning and enforce short-lived identity federation for build systems. Prefer managed identities and periodically review workload access grants. ExplanationCorrect Answer D:Prefer managed identities and periodically review workload access grants. Maintaining this control reduces recurrence because: Managed identities let Azure workloads receive identity tokens without maintaining developer-supplied credentials. The immediate response remains: Use an Azure managed identity with an authorized Key Vault role. Other Answers A:Workload identities authenticate software and automation independently from a human user's lifecycle. A more direct preventive measure is to prefer managed identities and periodically review workload access grants. B:Directory administration and Azure resource permissions are separate authorization planes. The lasting safeguard is to prefer managed identities and periodically review workload access grants. C:Workload identities and federated credentials avoid distributing long-lived app passwords to repositories. Reducing this risk requires a practice to prefer managed identities and periodically review workload access grants.
Question 133A partner SaaS app requires an API permission, but the application developers give everyone global administrator roles to make the service work. Which action most directly resolves the security or identity requirement? 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. Distinguish Entra directory roles from Azure resource RBAC assignments. Create a dedicated app registration and service principal with approved Microsoft Graph permissions. ExplanationCorrect Answer B:Application permissions are distinct from tenant-wide administration, and consent scope determines what the app can do. To confirm, inspect granted API scopes and verify an unrelated API remains inaccessible. Other Answers A:Entra B2B directory presence and resource authorization are separate trust decisions. A more relevant action is to register the application and grant only the requested Microsoft Entra app permissions through a controlled consent process. C:Directory administration and Azure resource permissions are separate authorization planes. This failure calls for a decision to register the application and grant only the requested Microsoft Entra app permissions through a controlled consent process. D:An application principal represents software rather than an employee signing in interactively. A more relevant action is to register the application and grant only the requested Microsoft Entra app permissions through a controlled consent process.
Question 134A partner SaaS app requires an API permission, but the application developers give everyone global administrator roles to make the service work. Which technical distinction is decisive in this case? Directory administration and Azure resource permissions are separate authorization planes. An application principal represents software rather than an employee signing in interactively. Entra B2B directory presence and resource authorization are separate trust decisions. Application permissions are distinct from tenant-wide administration, and consent scope determines what the app can do. ExplanationCorrect Answer D:Application permissions are distinct from tenant-wide administration, and consent scope determines what the app can do. This is the principle behind: Register the application and grant only the requested Microsoft Entra app permissions through a controlled consent process. The evidence to inspect is: Inspect granted API scopes and verify an unrelated API remains inaccessible. Other Answers A:Directory administration and Azure resource permissions are separate authorization planes. In the stated system, application permissions are distinct from tenant-wide administration, and consent scope determines what the app can do. B:An application principal represents software rather than an employee signing in interactively. By contrast, application permissions are distinct from tenant-wide administration, and consent scope determines what the app can do. C:Entra B2B directory presence and resource authorization are separate trust decisions. By contrast, application permissions are distinct from tenant-wide administration, and consent scope determines what the app can do.
Question 135A partner SaaS app requires an API permission, but the application developers give everyone global administrator roles to make the service work. Which observation best validates the chosen approach? Inspect granted API scopes and verify an unrelated API remains inaccessible. Check sign-in succeeded and that unassigned Teams or SharePoint resources remain unavailable. Observe client-credential token issuance and deny access when the app permission is removed. Compare a test user's directory-role capabilities with its subscription-resource access. ExplanationCorrect Answer A:Inspect granted API scopes and verify an unrelated API remains inaccessible. This test checks the expected result of: Register the application and grant only the requested Microsoft Entra app permissions through a controlled consent process. It matters because: Application permissions are distinct from tenant-wide administration, and consent scope determines what the app can do. Other Answers B:Entra B2B directory presence and resource authorization are separate trust decisions. Proving this correction calls for a check to inspect granted API scopes and verify an unrelated API remains inaccessible. C:An application principal represents software rather than an employee signing in interactively. Proving this correction calls for a check to inspect granted API scopes and verify an unrelated API remains inaccessible. D:Directory administration and Azure resource permissions are separate authorization planes. The relevant acceptance check is to inspect granted API scopes and verify an unrelated API remains inaccessible.
Question 136A partner SaaS app requires an API permission, but the application developers give everyone global administrator roles to make the service work. Which governance action most directly addresses the recurring risk? Review directory roles and subscription RBAC in separate privileged-access processes. Enforce application consent reviews and least-privilege service principal grants. Review external-user access separately from identity invitations. Use application permission governance and service principal credential rotation. ExplanationCorrect Answer B:Enforce application consent reviews and least-privilege service principal grants. Maintaining this control reduces recurrence because: Application permissions are distinct from tenant-wide administration, and consent scope determines what the app can do. The immediate response remains: Register the application and grant only the requested Microsoft Entra app permissions through a controlled consent process. Other Answers A:Directory administration and Azure resource permissions are separate authorization planes. Reducing this risk requires a practice to enforce application consent reviews and least-privilege service principal grants. C:Entra B2B directory presence and resource authorization are separate trust decisions. The lasting safeguard is to enforce application consent reviews and least-privilege service principal grants. D:An application principal represents software rather than an employee signing in interactively. The lasting safeguard is to enforce application consent reviews and least-privilege service principal grants.
Question 137A consulting firm wants guest collaborators to use their home work accounts rather than provision full internal employee accounts for every project. Which action most directly resolves the security or identity requirement? Use an appropriate external customer identity solution and separate consumer identity from workforce administration. Monitor the supported hybrid identity synchronization and sign-in configuration. Use Microsoft Entra B2B collaboration identities with scoped resource invitations. Grant only the specific application and resource permissions that the guest needs. ExplanationCorrect Answer C:External guest identities support collaboration without turning every invited partner into a normal internal employee identity. To confirm, invite a test partner and confirm its directory user type and limited access to an approved team. Other Answers A:Customer-facing identity experiences differ in audience and governance from workforce Entra tenant administrator identities. A more relevant action is to use Microsoft Entra B2B collaboration identities with scoped resource invitations. B:Hybrid identity depends on a functioning synchronization or federation path between on-premises identity and cloud services. The corrective action for this requirement is to use Microsoft Entra B2B collaboration identities with scoped resource invitations. D:Entra B2B directory presence and resource authorization are separate trust decisions. The corrective action for this requirement is to use Microsoft Entra B2B collaboration identities with scoped resource invitations.
Question 138A consulting firm wants guest collaborators to use their home work accounts rather than provision full internal employee accounts for every project. 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. External guest identities support collaboration without turning every invited partner into a normal internal employee identity. Entra B2B directory presence and resource authorization are separate trust decisions. Customer-facing identity experiences differ in audience and governance from workforce Entra tenant administrator identities. ExplanationCorrect Answer B:External guest identities support collaboration without turning every invited partner into a normal internal employee identity. This is the principle behind: Use Microsoft Entra B2B collaboration identities with scoped resource invitations. The evidence to inspect is: Invite a test partner and confirm its directory user type and limited access to an approved team. Other Answers A:Hybrid identity depends on a functioning synchronization or federation path between on-premises identity and cloud services. In the stated system, external guest identities support collaboration without turning every invited partner into a normal internal employee identity. C:Entra B2B directory presence and resource authorization are separate trust decisions. In the stated system, external guest identities support collaboration without turning every invited partner into a normal internal employee identity. D:Customer-facing identity experiences differ in audience and governance from workforce Entra tenant administrator identities. By contrast, external guest identities support collaboration without turning every invited partner into a normal internal employee identity.
Question 139A consulting firm wants guest collaborators to use their home work accounts rather than provision full internal employee accounts for every project. Which observation best validates the chosen approach? Check sign-in succeeded and that unassigned Teams or SharePoint resources remain unavailable. Change an approved test user's attribute and verify the cloud representation and sign-in outcome. Invite a test partner and confirm its directory user type and limited access to an approved team. Enroll a mock shopper and confirm its account cannot administer workforce applications. ExplanationCorrect Answer C:Invite a test partner and confirm its directory user type and limited access to an approved team. This test checks the expected result of: Use Microsoft Entra B2B collaboration identities with scoped resource invitations. It matters because: External guest identities support collaboration without turning every invited partner into a normal internal employee identity. Other Answers A:Entra B2B directory presence and resource authorization are separate trust decisions. The relevant acceptance check is to invite a test partner and confirm its directory user type and limited access to an approved team. B:Hybrid identity depends on a functioning synchronization or federation path between on-premises identity and cloud services. The relevant acceptance check is to invite a test partner and confirm its directory user type and limited access to an approved team. D:Customer-facing identity experiences differ in audience and governance from workforce Entra tenant administrator identities. A more meaningful verification is to invite a test partner and confirm its directory user type and limited access to an approved team.
Question 140A consulting firm wants guest collaborators to use their home work accounts rather than provision full internal employee accounts for every project. Which governance action most directly addresses the recurring risk? Apply guest access reviews and automatic expiration at project completion. Alert on directory sync failures and investigate identity propagation delays. Keep customer and employee identity lifecycle policies separated. Review external-user access separately from identity invitations. ExplanationCorrect Answer A:Apply guest access reviews and automatic expiration at project completion. Maintaining this control reduces recurrence because: External guest identities support collaboration without turning every invited partner into a normal internal employee identity. The immediate response remains: Use Microsoft Entra B2B collaboration identities with scoped resource invitations. 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 apply guest access reviews and automatic expiration at project completion. C:Customer-facing identity experiences differ in audience and governance from workforce Entra tenant administrator identities. Reducing this risk requires a practice to apply guest access reviews and automatic expiration at project completion. D:Entra B2B directory presence and resource authorization are separate trust decisions. A more direct preventive measure is to apply guest access reviews and automatic expiration at project completion.