Question 150A hybrid organization wants Windows domain accounts to access Microsoft 365 but assumes Azure AD Domain Services is the same thing as a full on-premises AD DS replacement. 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. Entra ID manages cloud users, groups, apps, and access tokens, unlike a traditional local domain controller. Directory administration and Azure resource permissions are separate authorization planes. ExplanationCorrect Answer B:Traditional AD DS domain control and Entra cloud identity are related but distinct services with different capabilities. This is the principle behind: Select the documented hybrid Entra/AD DS integration suitable to domain and cloud sign-in requirements. The evidence to inspect is: Test local domain authentication and cloud token sign-in separately using a synchronized user. Other Answers A:Hybrid identity depends on a functioning synchronization or federation path between on-premises identity and cloud services. In the stated system, traditional AD DS domain control and Entra cloud identity are related but distinct services with different capabilities. C:Entra ID manages cloud users, groups, apps, and access tokens, unlike a traditional local domain controller. By contrast, traditional AD DS domain control and Entra cloud identity are related but distinct services with different capabilities. D:Directory administration and Azure resource permissions are separate authorization planes. By contrast, traditional AD DS domain control and Entra cloud identity are related but distinct services with different capabilities.
Question 151A hybrid organization wants Windows domain accounts to access Microsoft 365 but assumes Azure AD Domain Services is the same thing as a full on-premises AD DS replacement. Which observation best validates the chosen approach? Compare a test user's directory-role capabilities with its subscription-resource access. 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. Sign in to two registered cloud applications with one organizational account and review tokens. ExplanationCorrect Answer B:Test local domain authentication and cloud token sign-in separately using a synchronized user. This test checks the expected result of: Select the documented hybrid Entra/AD DS integration suitable to domain and cloud sign-in requirements. It matters because: Traditional AD DS domain control and Entra cloud identity are related but distinct services with different capabilities. Other Answers A:Directory administration and Azure resource permissions are separate authorization planes. The failure is checked more directly by a test to test local domain authentication and cloud token sign-in separately using a synchronized user. C:Hybrid identity depends on a functioning synchronization or federation path between on-premises identity and cloud services. A more meaningful verification is to test local domain authentication and cloud token sign-in separately using a synchronized user. D:Entra ID manages cloud users, groups, apps, and access tokens, unlike a traditional local domain controller. Proving this correction calls for a check to test local domain authentication and cloud token sign-in separately using a synchronized user.
Question 152A hybrid organization wants Windows domain accounts to access Microsoft 365 but assumes Azure AD Domain Services is the same thing as a full on-premises AD DS replacement. Which governance action most directly addresses the recurring risk? Alert on directory sync failures and investigate identity propagation delays. Review directory roles and subscription RBAC in separate privileged-access processes. Govern enterprise app registrations and identity assignments centrally. Maintain a supported hybrid identity design with explicit dependency ownership. ExplanationCorrect Answer D:Maintain a supported hybrid identity design with explicit dependency ownership. Maintaining this control reduces recurrence because: Traditional AD DS domain control and Entra cloud identity are related but distinct services with different capabilities. The immediate response remains: Select the documented hybrid Entra/AD DS integration suitable to domain and cloud sign-in requirements. Other Answers A:Hybrid identity depends on a functioning synchronization or federation path between on-premises identity and cloud services. Reducing this risk requires a practice to maintain a supported hybrid identity design with explicit dependency ownership. B:Directory administration and Azure resource permissions are separate authorization planes. The lasting safeguard is to maintain a supported hybrid identity design with explicit dependency ownership. C:Entra ID manages cloud users, groups, apps, and access tokens, unlike a traditional local domain controller. The stronger recurring control is to maintain a supported hybrid identity design with explicit dependency ownership.
Question 153An engineering team hardcodes a service principal's client secret in source control because the CI job needs to access Azure resources. Which action most directly resolves the security or identity requirement? Assign a supported service principal or managed identity with only required resource permissions. Use an Azure managed identity with an authorized Key Vault role. Create a dedicated app registration and service principal with approved Microsoft Graph permissions. Move workload authentication to managed or federated credentials where supported, and revoke the exposed secret. ExplanationCorrect Answer D:Workload identities and federated credentials avoid distributing long-lived app passwords to repositories. To confirm, run the job without the old secret and verify the leaked credential is rejected. Other Answers A:Workload identities authenticate software and automation independently from a human user's lifecycle. The required change instead is to move workload authentication to managed or federated credentials where supported, and revoke the exposed secret. B:Managed identities let Azure workloads receive identity tokens without maintaining developer-supplied credentials. The corrective action for this requirement is to move workload authentication to managed or federated credentials where supported, and revoke the exposed secret. C:An application principal represents software rather than an employee signing in interactively. This failure calls for a decision to move workload authentication to managed or federated credentials where supported, and revoke the exposed secret.
Question 154An engineering team hardcodes a service principal's client secret in source control because the CI job needs to access Azure resources. Which technical distinction is decisive in this case? Workload identities and federated credentials avoid distributing long-lived app passwords to repositories. 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. Managed identities let Azure workloads receive identity tokens without maintaining developer-supplied credentials. ExplanationCorrect Answer A:Workload identities and federated credentials avoid distributing long-lived app passwords to repositories. This is the principle behind: Move workload authentication to managed or federated credentials where supported, and revoke the exposed secret. The evidence to inspect is: Run the job without the old secret and verify the leaked credential is rejected. Other Answers B:An application principal represents software rather than an employee signing in interactively. By contrast, workload identities and federated credentials avoid distributing long-lived app passwords to repositories. C:Workload identities authenticate software and automation independently from a human user's lifecycle. In the stated system, workload identities and federated credentials avoid distributing long-lived app passwords to repositories. D:Managed identities let Azure workloads receive identity tokens without maintaining developer-supplied credentials. By contrast, workload identities and federated credentials avoid distributing long-lived app passwords to repositories.
Question 155An engineering team hardcodes a service principal's client secret in source control because the CI job needs to access Azure resources. 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. Observe client-credential token issuance and deny access when the app permission is removed. ExplanationCorrect Answer A:Run the job without the old secret and verify the leaked credential is rejected. This test checks the expected result of: Move workload authentication to managed or federated credentials where supported, and revoke the exposed secret. It matters because: Workload identities and federated credentials avoid distributing long-lived app passwords to repositories. Other Answers B:Workload identities authenticate software and automation independently from a human user's lifecycle. A more meaningful verification is to run the job without the old secret and verify the leaked credential is rejected. C:Managed identities let Azure workloads receive identity tokens without maintaining developer-supplied credentials. The failure is checked more directly by a test to run the job without the old secret and verify the leaked credential is rejected. D:An application principal represents software rather than an employee signing in interactively. Proving this correction calls for a check to run the job without the old secret and verify the leaked credential is rejected.
Question 156An engineering team hardcodes a service principal's client secret in source control because the CI job needs to access Azure resources. Which governance action most directly addresses the recurring risk? Use application permission governance and service principal credential rotation. Use secret scanning and enforce short-lived identity federation for build systems. Prohibit user passwords in unattended jobs and audit nonhuman app identities. Prefer managed identities and periodically review workload access grants. ExplanationCorrect Answer B:Use secret scanning and enforce short-lived identity federation for build systems. Maintaining this control reduces recurrence because: Workload identities and federated credentials avoid distributing long-lived app passwords to repositories. The immediate response remains: Move workload authentication to managed or federated credentials where supported, and revoke the exposed secret. Other Answers A:An application principal represents software rather than an employee signing in interactively. The lasting safeguard is to use secret scanning and enforce short-lived identity federation for build systems. C:Workload identities authenticate software and automation independently from a human user's lifecycle. The stronger recurring control is to use secret scanning and enforce short-lived identity federation for build systems. D:Managed identities let Azure workloads receive identity tokens without maintaining developer-supplied credentials. A more direct preventive measure is to use secret scanning and enforce short-lived identity federation for build systems.
Question 157An enterprise creates a new Azure subscription and assumes its subscription owner is automatically the same principal as the Microsoft Entra tenant Global Administrator. Which action most directly resolves the security or identity requirement? 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. Grant only the specific application and resource permissions that the guest needs. Assign a supported service principal or managed identity with only required resource permissions. ExplanationCorrect Answer B:Directory administration and Azure resource permissions are separate authorization planes. To confirm, compare a test user's directory-role capabilities with its subscription-resource access. Other Answers A:Application permissions are distinct from tenant-wide administration, and consent scope determines what the app can do. A more relevant action is to distinguish Entra directory roles from Azure resource RBAC assignments. C:Entra B2B directory presence and resource authorization are separate trust decisions. A more relevant action is to distinguish Entra directory roles from Azure resource RBAC assignments. D:Workload identities authenticate software and automation independently from a human user's lifecycle. The corrective action for this requirement is to distinguish Entra directory roles from Azure resource RBAC assignments.
Question 158An enterprise creates a new Azure subscription and assumes its subscription owner is automatically the same principal as the Microsoft Entra tenant Global Administrator. Which technical distinction is decisive in this case? 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. Directory administration and Azure resource permissions are separate authorization planes. Workload identities authenticate software and automation independently from a human user's lifecycle. ExplanationCorrect Answer C:Directory administration and Azure resource permissions are separate authorization planes. This is the principle behind: Distinguish Entra directory roles from Azure resource RBAC assignments. The evidence to inspect is: Compare a test user's directory-role capabilities with its subscription-resource access. Other Answers A:Entra B2B directory presence and resource authorization are separate trust decisions. In the stated system, directory administration and Azure resource permissions are separate authorization planes. B:Application permissions are distinct from tenant-wide administration, and consent scope determines what the app can do. In the stated system, directory administration and Azure resource permissions are separate authorization planes. D:Workload identities authenticate software and automation independently from a human user's lifecycle. By contrast, directory administration and Azure resource permissions are separate authorization planes.
Question 159An enterprise creates a new Azure subscription and assumes its subscription owner is automatically the same principal as the Microsoft Entra tenant Global Administrator. Which observation best validates the chosen approach? Disable the employee account and confirm the automated job still authenticates as its own principal. Check sign-in succeeded and that unassigned Teams or SharePoint resources remain unavailable. Compare a test user's directory-role capabilities with its subscription-resource access. Inspect granted API scopes and verify an unrelated API remains inaccessible. ExplanationCorrect Answer C:Compare a test user's directory-role capabilities with its subscription-resource access. This test checks the expected result of: Distinguish Entra directory roles from Azure resource RBAC assignments. It matters because: Directory administration and Azure resource permissions are separate authorization planes. Other Answers A:Workload identities authenticate software and automation independently from a human user's lifecycle. The failure is checked more directly by a test to compare a test user's directory-role capabilities with its subscription-resource access. B:Entra B2B directory presence and resource authorization are separate trust decisions. The relevant acceptance check is to compare a test user's directory-role capabilities with its subscription-resource access. D:Application permissions are distinct from tenant-wide administration, and consent scope determines what the app can do. The relevant acceptance check is to compare a test user's directory-role capabilities with its subscription-resource access.
Question 160An enterprise creates a new Azure subscription and assumes its subscription owner is automatically the same principal as the Microsoft Entra tenant Global Administrator. Which governance action most directly addresses the recurring risk? Prohibit user passwords in unattended jobs and audit nonhuman app identities. Enforce application consent reviews and least-privilege service principal grants. Review directory roles and subscription RBAC in separate privileged-access processes. Review external-user access separately from identity invitations. ExplanationCorrect Answer C:Review directory roles and subscription RBAC in separate privileged-access processes. Maintaining this control reduces recurrence because: Directory administration and Azure resource permissions are separate authorization planes. The immediate response remains: Distinguish Entra directory roles from Azure resource RBAC assignments. Other Answers A:Workload identities authenticate software and automation independently from a human user's lifecycle. Reducing this risk requires a practice to review directory roles and subscription RBAC in separate privileged-access processes. B:Application permissions are distinct from tenant-wide administration, and consent scope determines what the app can do. The stronger recurring control is to review directory roles and subscription RBAC in separate privileged-access processes. D:Entra B2B directory presence and resource authorization are separate trust decisions. The stronger recurring control is to review directory roles and subscription RBAC in separate privileged-access processes.