Question 670A temporary support user receives permissions via two groups with overlapping broad and narrow roles. If this issue remains uncorrected, which outcome is the most direct avoidable risk? A stolen password or unmanaged endpoint could permit unauthorized security-policy changes A least-privilege assignment could be defeated by an overlooked inherited grant A tenant-wide policy mistake could lock responders out during an identity outage Mismatched principal selection may break workload availability or encourage key-based fallback ExplanationCorrect Answer B:The principal risk is that A least-privilege assignment could be defeated by an overlooked inherited grant. The preventative response is to inspect effective role assignments and remove the overbroad inherited group membership. This matters because the union of role assignments can increase privilege beyond any individual intended role. Incorrect Answers A:Conditional Access evaluates identity, resource, client context and session risk before granting access. The immediate omission risk in this case is: A least-privilege assignment could be defeated by an overlooked inherited grant. C:Emergency access must remain viable when normal authentication or policy configuration is unavailable. The immediate omission risk in this case is: A least-privilege assignment could be defeated by an overlooked inherited grant. D:User-assigned managed identities are separate resources and must be attached to the intended workload. The immediate omission risk in this case is: A least-privilege assignment could be defeated by an overlooked inherited grant.
Question 671A confidential production VM uses an administrator account shared across contractors for emergency maintenance. An engineer proposes to replace shared accounts with individual scoped identities and an auditable protected emergency procedure. Which technical principle most strongly supports that proposal? Defender for Cloud JIT reduces standing management-port exposure through temporary rules AKS control-plane exposure should match the documented management-network threat model Strong VM administration requires per-operator attribution and controlled break-glass access Azure Files supports distinct SMB and REST access patterns with different identity requirements ExplanationCorrect Answer C:The technical principle is: Strong VM administration requires per-operator attribution and controlled break-glass access. It supports the proposed action to replace shared accounts with individual scoped identities and an auditable protected emergency procedure. Confirmation evidence: maintenance activity records the responsible operator and the shared account is disabled. Incorrect Answers A:Defender for Cloud JIT reduces standing management-port exposure through temporary rules. For the current requirement, the decisive mechanism is: Strong VM administration requires per-operator attribution and controlled break-glass access. The related action is: Replace shared accounts with individual scoped identities and an auditable protected emergency procedure. B:AKS control-plane exposure should match the documented management-network threat model. For the current requirement, the decisive mechanism is: Strong VM administration requires per-operator attribution and controlled break-glass access. The related action is: Replace shared accounts with individual scoped identities and an auditable protected emergency procedure. D:Azure Files supports distinct SMB and REST access patterns with different identity requirements. For the current requirement, the decisive mechanism is: Strong VM administration requires per-operator attribution and controlled break-glass access. The related action is: Replace shared accounts with individual scoped identities and an auditable protected emergency procedure.
Question 672A new GitHub organization is onboarded for Defender for Cloud DevOps Security without repository permission review. Which change best addresses this retired Azure security topic? Enable suitable soft delete and purge protection before production use Onboard the hybrid hosts through supported integration and verify server plan coverage Enable the appropriate Defender for Servers plan for the intended protected scope Configure supported least-privilege GitHub connector permissions and validate repo coverage ExplanationCorrect Answer D:The relevant technical principle is: DevOps security findings depend on authorized connectors with appropriate repository scope. The appropriate correction is to configure supported least-privilege GitHub connector permissions and validate repo coverage. Verify it by checking that the intended repositories appear with current assessment status and unrelated repos remain excluded. Incorrect Answers A:Key Vault deletion protection reduces risk of irrecoverable loss of security-critical secrets and keys. The operative distinction here is: DevOps security findings depend on authorized connectors with appropriate repository scope. The targeted change is: Configure supported least-privilege GitHub connector permissions and validate repo coverage. B:Workload threat protection requires healthy asset connectors and appropriate plan selection. The operative distinction here is: DevOps security findings depend on authorized connectors with appropriate repository scope. The targeted change is: Configure supported least-privilege GitHub connector permissions and validate repo coverage. C:Cloud security posture and workload threat-protection plans have different enablement requirements. The operative distinction here is: DevOps security findings depend on authorized connectors with appropriate repository scope. The targeted change is: Configure supported least-privilege GitHub connector permissions and validate repo coverage.
Question 673A public-facing microservice receives traffic through both Front Door and a bypassable origin IP. An engineer proposes to restrict origin access to approved Front Door connectivity and enforce origin authentication. Which technical principle most strongly supports that proposal? Global edge controls rely on origins rejecting unapproved direct traffic Traffic must satisfy applicable security rules across both subnet and interface boundaries Allowing a port number alone does not prove the destination service is trustworthy TLS listener availability depends on valid configured server certificates and renewed trust ExplanationCorrect Answer A:The technical principle is: Global edge controls rely on origins rejecting unapproved direct traffic. It supports the proposed action to restrict origin access to approved Front Door connectivity and enforce origin authentication. Confirmation evidence: direct origin requests fail while validated Front Door-originated requests succeed. Incorrect Answers B:Traffic must satisfy applicable security rules across both subnet and interface boundaries. For the current requirement, the decisive mechanism is: Global edge controls rely on origins rejecting unapproved direct traffic. The related action is: Restrict origin access to approved Front Door connectivity and enforce origin authentication. C:Allowing a port number alone does not prove the destination service is trustworthy. For the current requirement, the decisive mechanism is: Global edge controls rely on origins rejecting unapproved direct traffic. The related action is: Restrict origin access to approved Front Door connectivity and enforce origin authentication. D:TLS listener availability depends on valid configured server certificates and renewed trust. For the current requirement, the decisive mechanism is: Global edge controls rely on origins rejecting unapproved direct traffic. The related action is: Restrict origin access to approved Front Door connectivity and enforce origin authentication.
Question 674A team uses Defender External Attack Surface Management but never validates whether discovered domains belong to the company. After the team acts to verify EASM discovery attribution and assign owners before taking action on suspected assets, which observation best demonstrates that the repair worked? Each failed control has a reviewed affected-resource list an owner and closure evidence Reviewed domains are associated with correct business units and unknown findings are triaged separately A test run writes only permitted case identifiers to the protected destination Control mapping identifies assessed evidence and separately tracked manual requirements ExplanationCorrect Answer B:The expected result is that reviewed domains are associated with correct business units and unknown findings are triaged separately. This confirms the applicable principle: External attack-surface discoveries require entity attribution and asset context. Incorrect Answers A:Regulatory dashboards aggregate control assessments but human governance must resolve deviations. This is not the decisive validation for the stated requirement. The relevant evidence is: Reviewed domains are associated with correct business units and unknown findings are triaged separately. C:Automation integrations must protect sensitive information under the same confidentiality rules as analysts. This is not the decisive validation for the stated requirement. The relevant evidence is: Reviewed domains are associated with correct business units and unknown findings are triaged separately. D:Automated standards assess configured technical signals not all governance or legal obligations. This is not the decisive validation for the stated requirement. The relevant evidence is: Reviewed domains are associated with correct business units and unknown findings are triaged separately.
Question 675A service publishes one exposed public IP but its DDoS plan covers only application-layer HTTP. If this issue remains uncorrected, which outcome is the most direct avoidable risk? Attackers could evade gateway inspection and WAF protections An unrelated consumer could gain access to a sensitive private service A network-layer flood may overwhelm service availability before HTTP inspection Policy drift could leave a regional network with weaker protections ExplanationCorrect Answer C:The principal risk is that A network-layer flood may overwhelm service availability before HTTP inspection. The preventative response is to assess Azure DDoS Protection for network-layer risks at relevant VNet public endpoints. This matters because volumetric and protocol-level denial-of-service require controls beyond a web WAF. Incorrect Answers A:Layer-7 gateway security is ineffective when the original service stays directly accessible. The immediate omission risk in this case is: A network-layer flood may overwhelm service availability before HTTP inspection. B:Private Link service connection approval governs which private endpoint consumers reach a provider. The immediate omission risk in this case is: A network-layer flood may overwhelm service availability before HTTP inspection. D:Central firewall policies can provide consistent baseline rules across multiple protected hubs. The immediate omission risk in this case is: A network-layer flood may overwhelm service availability before HTTP inspection.
Question 676A production automation script shares the same service principal credential with several independent applications. If this issue remains uncorrected, which outcome is the most direct avoidable risk? Unreviewed audience expansion might expose authentication entry points to unintended organizations An overconsented third-party application might read or modify unnecessary tenant data Persistent vendor rights could outlast the maintenance contract and enable harmful changes One compromised secret could provide access to several unrelated business workloads ExplanationCorrect Answer D:The principal risk is that one compromised secret could provide access to several unrelated business workloads. The preventative response is to create distinct scoped workload identities and rotate the shared secret out of circulation. This matters because separate principal identity enables granular access revocation and incident attribution. Incorrect Answers A:Application sign-in audience settings determine which Microsoft Entra tenants may issue tokens. The immediate omission risk in this case is: One compromised secret could provide access to several unrelated business workloads. B:Admin consent may authorize high-impact access far beyond a user's immediate reporting need. The immediate omission risk in this case is: One compromised secret could provide access to several unrelated business workloads. C:Just-in-time privileged access reduces standing exposure while retaining auditable emergency elevation. The immediate omission risk in this case is: One compromised secret could provide access to several unrelated business workloads.
Question 677A service application stores a long-lived client secret directly in an Azure DevOps YAML file. Which change best addresses this retired Azure security topic? Replace the embedded secret with workload federation or managed identity where supported Choose delegated scopes for actions on behalf of signed-in users and validate consent boundaries Review inherited role scope before moving sensitive resources into that group Grant the function's managed identity only the required vault data-plane access ExplanationCorrect Answer A:The relevant technical principle is: Federated and managed workload credentials avoid persistent secret exposure in deployment definitions. The appropriate correction is to replace the embedded secret with workload federation or managed identity where supported. Verify it by checking that A test deployment receives an authorized token without storing client secrets in source control. Incorrect Answers B:Delegated permissions act within a user's context while application permissions allow autonomous app access. The operative distinction here is: Federated and managed workload credentials avoid persistent secret exposure in deployment definitions. The targeted change is: Replace the embedded secret with workload federation or managed identity where supported. C:Azure RBAC inheritance follows the management-group subscription resource-group resource hierarchy. The operative distinction here is: Federated and managed workload credentials avoid persistent secret exposure in deployment definitions. The targeted change is: Replace the embedded secret with workload federation or managed identity where supported. D:A managed identity receives tokens for resource access but still needs explicit target authorization. The operative distinction here is: Federated and managed workload credentials avoid persistent secret exposure in deployment definitions. The targeted change is: Replace the embedded secret with workload federation or managed identity where supported.
Question 678A partner's site-to-site VPN uses overlapping on-premises address ranges that collide with Azure workloads. Which change best addresses this retired Azure security topic? Select the approved threat-intelligence behavior and validate controlled destination filtering Plan distinct address spaces or approved translation before establishing the connectivity Implement destination-specific outbound rules and validate required service exceptions Apply scoped NSG inbound rules permitting only the documented required application ports ExplanationCorrect Answer B:The relevant technical principle is: IPsec tunnel establishment cannot resolve ambiguous or overlapping destination addressing alone. The appropriate correction is to plan distinct address spaces or approved translation before establishing the connectivity. Verify it by checking that traffic reaches the correct network prefixes with no ambiguous effective route. Incorrect Answers A:Threat intelligence alert-only mode reports risk without necessarily preventing connections. The operative distinction here is: IPsec tunnel establishment cannot resolve ambiguous or overlapping destination addressing alone. The targeted change is: Plan distinct address spaces or approved translation before establishing the connectivity. C:Outbound NSG filtering can restrict workloads from communicating with unapproved networks. The operative distinction here is: IPsec tunnel establishment cannot resolve ambiguous or overlapping destination addressing alone. The targeted change is: Plan distinct address spaces or approved translation before establishing the connectivity. D:Network Security Groups filter traffic by rule priority direction protocol source destination and port. The operative distinction here is: IPsec tunnel establishment cannot resolve ambiguous or overlapping destination addressing alone. The targeted change is: Plan distinct address spaces or approved translation before establishing the connectivity.
Question 679An Azure SQL fleet is not included in its intended Defender for Databases protection scope. An engineer proposes to enable the appropriate database protection plan and assess coverage for the affected SQL resources. Which technical principle most strongly supports that proposal? Defender for Storage assesses supported threat signals only for protected eligible storage Azure Policy effects apply through their assignment scope and inherited governance hierarchy Database threat detection depends on selected plan and supported resource onboarding Workload threat protection requires healthy asset connectors and appropriate plan selection ExplanationCorrect Answer C:The technical principle is: Database threat detection depends on selected plan and supported resource onboarding. It supports the proposed action to enable the appropriate database protection plan and assess coverage for the affected SQL resources. Confirmation evidence: A protected SQL instance reports plan status and relevant security alerts reach the queue. Incorrect Answers A:Defender for Storage assesses supported threat signals only for protected eligible storage. For the current requirement, the decisive mechanism is: Database threat detection depends on selected plan and supported resource onboarding. The related action is: Enable the appropriate database protection plan and assess coverage for the affected SQL resources. B:Azure Policy effects apply through their assignment scope and inherited governance hierarchy. For the current requirement, the decisive mechanism is: Database threat detection depends on selected plan and supported resource onboarding. The related action is: Enable the appropriate database protection plan and assess coverage for the affected SQL resources. D:Workload threat protection requires healthy asset connectors and appropriate plan selection. For the current requirement, the decisive mechanism is: Database threat detection depends on selected plan and supported resource onboarding. The related action is: Enable the appropriate database protection plan and assess coverage for the affected SQL resources.
Question 680A vendor software client receives organization-wide admin consent for permissions used only by one reporting view. Which change best addresses this retired Azure security topic? Replace the embedded secret with workload federation or managed identity where supported Assign a narrow custom deployment role scoped to the intended resource rather than the subscription Choose delegated scopes for actions on behalf of signed-in users and validate consent boundaries Restrict consent to necessary API scopes and examine the application's enterprise permissions ExplanationCorrect Answer D:The relevant technical principle is: Admin consent may authorize high-impact access far beyond a user's immediate reporting need. The appropriate correction is to restrict consent to necessary API scopes and examine the application's enterprise permissions. Verify it by checking that enterprise application permission review shows only required reporting grants and resource scope. Incorrect Answers A:Federated and managed workload credentials avoid persistent secret exposure in deployment definitions. The operative distinction here is: Admin consent may authorize high-impact access far beyond a user's immediate reporting need. The targeted change is: Restrict consent to necessary API scopes and examine the application's enterprise permissions. B:Scoped deployment identities can manage their target resource without all subscription-write permissions. The operative distinction here is: Admin consent may authorize high-impact access far beyond a user's immediate reporting need. The targeted change is: Restrict consent to necessary API scopes and examine the application's enterprise permissions. C:Delegated permissions act within a user's context while application permissions allow autonomous app access. The operative distinction here is: Admin consent may authorize high-impact access far beyond a user's immediate reporting need. The targeted change is: Restrict consent to necessary API scopes and examine the application's enterprise permissions.