Question 160An enterprise peering design shares a private DNS zone with one spoke but leaves a second application VNet unlinked. Which change best addresses this retired Azure security topic? Apply scoped NSG inbound rules permitting only the documented required application ports Correct the Private DNS zone linkage and record resolution for the database service Configure and validate the private endpoint and disable public network access as required Link the approved private DNS zone to each VNet needing the private service ExplanationCorrect Answer D:The relevant technical principle is: Private DNS resolution is scoped by explicit zone-to-VNet linkage. The appropriate correction is to link the approved private DNS zone to each VNet needing the private service. Verify it by checking that the second application's DNS query resolves the authorized private endpoint address. Incorrect Answers A:Network Security Groups filter traffic by rule priority direction protocol source destination and port. The operative distinction here is: Private DNS resolution is scoped by explicit zone-to-VNet linkage. The targeted change is: Link the approved private DNS zone to each VNet needing the private service. B:Private endpoint connectivity depends on consistent service DNS resolution and reachable VNet links. The operative distinction here is: Private DNS resolution is scoped by explicit zone-to-VNet linkage. The targeted change is: Link the approved private DNS zone to each VNet needing the private service. C:Private Endpoints expose supported platform services through private IPs but public endpoints require separate restriction. The operative distinction here is: Private DNS resolution is scoped by explicit zone-to-VNet linkage. The targeted change is: Link the approved private DNS zone to each VNet needing the private service.
Question 161An internet-facing application has a publicly trusted certificate but the backend hop to its API uses plain HTTP. Which change best addresses this retired Azure security topic? Configure encrypted backend transport with appropriate certificate trust Define approved point-to-site routing and access restrictions for required management resources Rotate the listener certificate using controlled Key Vault integration or approved certificate deployment Set the minimum supported TLS version on the application endpoint and test legacy-client rejection ExplanationCorrect Answer A:The relevant technical principle is: Encryption at the public edge does not protect traffic on internal hops automatically. The appropriate correction is to configure encrypted backend transport with appropriate certificate trust. Verify it by checking that gateway-to-backend traces confirm HTTPS and trusted backend certificate validation. Incorrect Answers B:Remote-access VPN routing must match the organization's traffic-protection requirements. The operative distinction here is: Encryption at the public edge does not protect traffic on internal hops automatically. The targeted change is: Configure encrypted backend transport with appropriate certificate trust. C:TLS listener availability depends on valid configured server certificates and renewed trust. The operative distinction here is: Encryption at the public edge does not protect traffic on internal hops automatically. The targeted change is: Configure encrypted backend transport with appropriate certificate trust. D:Transport-layer security configuration must enforce protocol strength at each public termination point. The operative distinction here is: Encryption at the public edge does not protect traffic on internal hops automatically. The targeted change is: Configure encrypted backend transport with appropriate certificate trust.
Question 162A tag enforcement policy modifies resources but its managed identity lacks permissions to change tags. Which change best addresses this retired Azure security topic? Require controlled human review or supported safe automation and documented close criteria Grant a narrowly scoped remediation role and run a controlled remediation task Evaluate management-group assignment inheritance and use an approved scoped policy exception if justified Inspect effective Azure Policy initiative and individual policy evaluation details ExplanationCorrect Answer B:The relevant technical principle is: Policy modification and remediation require authorization for the policy assignment identity. The appropriate correction is to grant a narrowly scoped remediation role and run a controlled remediation task. Verify it by checking that the remediation task updates only target tags and reports success against sampled resources. Incorrect Answers A:Automated incident response must respect evidence integrity and approval boundaries. The operative distinction here is: Policy modification and remediation require authorization for the policy assignment identity. The targeted change is: Grant a narrowly scoped remediation role and run a controlled remediation task. C:Azure Policy effects apply through their assignment scope and inherited governance hierarchy. The operative distinction here is: Policy modification and remediation require authorization for the policy assignment identity. The targeted change is: Grant a narrowly scoped remediation role and run a controlled remediation task. D:An initiative aggregates policy definitions while compliance results can be traced to specific assignments. The operative distinction here is: Policy modification and remediation require authorization for the policy assignment identity. The targeted change is: Grant a narrowly scoped remediation role and run a controlled remediation task.
Question 163A billing analyst can change security settings because a custom role includes wildcard Microsoft.Authorization actions. Which change best addresses this retired Azure security topic? Create distinct scoped workload identities and rotate the shared secret out of circulation Use eligible time-bound privileged access with approval and activation evidence through PIM Edit the custom role to permit only validated cost-reading operations and inspect assignable scopes Replace subscription-wide Owner with the narrow VM operator role at the resource group ExplanationCorrect Answer C:The relevant technical principle is: Custom role action lists determine permissible management-plane operations and must not include unrelated privileges. The appropriate correction is to edit the custom role to permit only validated cost-reading operations and inspect assignable scopes. Verify it by checking that role definition inspection shows read-only billing actions and denied role-assignment writes. Incorrect Answers A:Separate principal identity enables granular access revocation and incident attribution. The operative distinction here is: Custom role action lists determine permissible management-plane operations and must not include unrelated privileges. The targeted change is: Edit the custom role to permit only validated cost-reading operations and inspect assignable scopes. B:Just-in-time privileged access reduces standing exposure while retaining auditable emergency elevation. The operative distinction here is: Custom role action lists determine permissible management-plane operations and must not include unrelated privileges. The targeted change is: Edit the custom role to permit only validated cost-reading operations and inspect assignable scopes. D:Azure role-based access control should grant the fewest management actions at the smallest workable scope. The operative distinction here is: Custom role action lists determine permissible management-plane operations and must not include unrelated privileges. The targeted change is: Edit the custom role to permit only validated cost-reading operations and inspect assignable scopes.
Question 164A resource owner disputes a Defender for Cloud finding but never supplies an auditable technical basis. An engineer proposes to use an approved exemption or remediation workflow backed by reproducible evidence. Which technical principle most strongly supports that proposal? Vault network access is a separate security boundary from access to keys and secrets Hybrid posture assessment depends on correctly connected and reporting assets Regulatory dashboards aggregate control assessments but human governance must resolve deviations Security recommendation dispositions need verifiable justification and review ExplanationCorrect Answer D:The technical principle is: Security recommendation dispositions need verifiable justification and review. It supports the proposed action to use an approved exemption or remediation workflow backed by reproducible evidence. Confirmation evidence: the exception log links a tested technical result and bounded approval period. Incorrect Answers A:Vault network access is a separate security boundary from access to keys and secrets. For the current requirement, the decisive mechanism is: Security recommendation dispositions need verifiable justification and review. The related action is: Use an approved exemption or remediation workflow backed by reproducible evidence. B:Hybrid posture assessment depends on correctly connected and reporting assets. For the current requirement, the decisive mechanism is: Security recommendation dispositions need verifiable justification and review. The related action is: Use an approved exemption or remediation workflow backed by reproducible evidence. C:Regulatory dashboards aggregate control assessments but human governance must resolve deviations. For the current requirement, the decisive mechanism is: Security recommendation dispositions need verifiable justification and review. The related action is: Use an approved exemption or remediation workflow backed by reproducible evidence.
Question 165An enterprise app retains unused high-privilege OAuth grants from an earlier integration phase. After the team acts to inventory granted scopes and remove those no longer required by the supported workflow, which observation best demonstrates that the repair worked? A test verifies required API calls succeed while formerly unnecessary scopes are absent Enterprise application permission review shows only required reporting grants and resource scope The function retrieves the intended secret while a different identity remains denied Review results identify approved business need and show removal of unneeded assignments ExplanationCorrect Answer A:The expected result is that A test verifies required API calls succeed while formerly unnecessary scopes are absent. This confirms the applicable principle: OAuth permission hygiene must reflect actual current application operations, not historic requests. Incorrect Answers B:Admin consent may authorize high-impact access far beyond a user's immediate reporting need. This is not the decisive validation for the stated requirement. The relevant evidence is: A test verifies required API calls succeed while formerly unnecessary scopes are absent. C:A managed identity receives tokens for resource access but still needs explicit target authorization. This is not the decisive validation for the stated requirement. The relevant evidence is: A test verifies required API calls succeed while formerly unnecessary scopes are absent. D:Reviewing privileged eligibility is a continuous control distinct from sign-in authentication. This is not the decisive validation for the stated requirement. The relevant evidence is: A test verifies required API calls succeed while formerly unnecessary scopes are absent.
Question 166A security team attaches identical NSG rules to five unrelated subnets with different intended roles. An engineer proposes to define Application Security Groups and scope policy by workload function where supported. Which technical principle most strongly supports that proposal? User-defined routes choose next hops but are not equivalent to security-filter rules Application Security Groups let rules refer to virtual machine groupings instead of brittle IP lists TLS listener availability depends on valid configured server certificates and renewed trust Outbound NSG filtering can restrict workloads from communicating with unapproved networks ExplanationCorrect Answer B:The technical principle is: Application Security Groups let rules refer to virtual machine groupings instead of brittle IP lists. It supports the proposed action to define Application Security Groups and scope policy by workload function where supported. Confirmation evidence: A new instance inherits authorized traffic outcomes without creating a new IP-specific allow rule. Incorrect Answers A:User-defined routes choose next hops but are not equivalent to security-filter rules. For the current requirement, the decisive mechanism is: Application Security Groups let rules refer to virtual machine groupings instead of brittle IP lists. The related action is: Define Application Security Groups and scope policy by workload function where supported. C:TLS listener availability depends on valid configured server certificates and renewed trust. For the current requirement, the decisive mechanism is: Application Security Groups let rules refer to virtual machine groupings instead of brittle IP lists. The related action is: Define Application Security Groups and scope policy by workload function where supported. D:Outbound NSG filtering can restrict workloads from communicating with unapproved networks. For the current requirement, the decisive mechanism is: Application Security Groups let rules refer to virtual machine groupings instead of brittle IP lists. The related action is: Define Application Security Groups and scope policy by workload function where supported.
Question 167A resource-group role assignment is inherited by new resources containing confidential logs unexpectedly. An engineer proposes to review inherited role scope before moving sensitive resources into that group. Which technical principle most strongly supports that proposal? Custom role action lists determine permissible management-plane operations and must not include unrelated privileges Just-in-time privileged access reduces standing exposure while retaining auditable emergency elevation Azure RBAC inheritance follows the management-group subscription resource-group resource hierarchy Federated and managed workload credentials avoid persistent secret exposure in deployment definitions ExplanationCorrect Answer C:The technical principle is: Azure RBAC inheritance follows the management-group subscription resource-group resource hierarchy. It supports the proposed action to review inherited role scope before moving sensitive resources into that group. Confirmation evidence: A new restricted log workspace does not grant unintended access through its parent scope. Incorrect Answers A:Custom role action lists determine permissible management-plane operations and must not include unrelated privileges. For the current requirement, the decisive mechanism is: Azure RBAC inheritance follows the management-group subscription resource-group resource hierarchy. The related action is: Review inherited role scope before moving sensitive resources into that group. B:Just-in-time privileged access reduces standing exposure while retaining auditable emergency elevation. For the current requirement, the decisive mechanism is: Azure RBAC inheritance follows the management-group subscription resource-group resource hierarchy. The related action is: Review inherited role scope before moving sensitive resources into that group. D:Federated and managed workload credentials avoid persistent secret exposure in deployment definitions. For the current requirement, the decisive mechanism is: Azure RBAC inheritance follows the management-group subscription resource-group resource hierarchy. The related action is: Review inherited role scope before moving sensitive resources into that group.
Question 168A virtual network has two NSGs whose combined effect is assumed to be an unrestricted allow. Which change best addresses this retired Azure security topic? Apply scoped NSG inbound rules permitting only the documented required application ports Revalidate the storage firewall and application DNS rather than preserving obsolete public-IP assumptions Implement destination-specific outbound rules and validate required service exceptions Evaluate subnet and NIC effective security rules rather than inspecting only one attached NSG ExplanationCorrect Answer D:The relevant technical principle is: Traffic must satisfy applicable security rules across both subnet and interface boundaries. The appropriate correction is to evaluate subnet and NIC effective security rules rather than inspecting only one attached NSG. Verify it by checking that effective-rule output explains the denied test packet and a narrow change resolves it. Incorrect Answers A:Network Security Groups filter traffic by rule priority direction protocol source destination and port. The operative distinction here is: Traffic must satisfy applicable security rules across both subnet and interface boundaries. The targeted change is: Evaluate subnet and NIC effective security rules rather than inspecting only one attached NSG. B:Private endpoint connectivity is evaluated differently from public service IP firewall rules. The operative distinction here is: Traffic must satisfy applicable security rules across both subnet and interface boundaries. The targeted change is: Evaluate subnet and NIC effective security rules rather than inspecting only one attached NSG. C:Outbound NSG filtering can restrict workloads from communicating with unapproved networks. The operative distinction here is: Traffic must satisfy applicable security rules across both subnet and interface boundaries. The targeted change is: Evaluate subnet and NIC effective security rules rather than inspecting only one attached NSG.
Question 169A security team enables Defender for Cloud free posture management and assumes paid server threat detections automatically operate. If this issue remains uncorrected, which outcome is the most direct avoidable risk? Security operators might miss server attack detections despite visible posture recommendations Overreacting to a noisy alert could disrupt legitimate production services Critical vulnerable software could persist unnoticed on protected servers Analysts may struggle to correlate alerts when entity identity is missing ExplanationCorrect Answer A:The principal risk is that security operators might miss server attack detections despite visible posture recommendations. The preventative response is to enable the appropriate Defender for Servers plan for the intended protected scope. This matters because cloud security posture and workload threat-protection plans have different enablement requirements. Incorrect Answers B:Threat detections provide leads and supporting evidence but require context-based adjudication. The immediate omission risk in this case is: Security operators might miss server attack detections despite visible posture recommendations. C:Vulnerability management requires current scan findings and actionable asset prioritization. The immediate omission risk in this case is: Security operators might miss server attack detections despite visible posture recommendations. D:Entity enrichment improves triage by linking events to identifiable resources and principals. The immediate omission risk in this case is: Security operators might miss server attack detections despite visible posture recommendations.
Question 170A production automation script shares the same service principal credential with several independent applications. After the team acts to create distinct scoped workload identities and rotate the shared secret out of circulation, which observation best demonstrates that the repair worked? The function retrieves the intended secret while a different identity remains denied Revoking one compromised credential leaves other applications operational with independent identities Enterprise application permission review shows only required reporting grants and resource scope Role activation records show approvals expiration and timely deactivation of vendor privileges ExplanationCorrect Answer B:The expected result is that revoking one compromised credential leaves other applications operational with independent identities. This confirms the applicable principle: Separate principal identity enables granular access revocation and incident attribution. Incorrect Answers A:A managed identity receives tokens for resource access but still needs explicit target authorization. This is not the decisive validation for the stated requirement. The relevant evidence is: Revoking one compromised credential leaves other applications operational with independent identities. C:Admin consent may authorize high-impact access far beyond a user's immediate reporting need. This is not the decisive validation for the stated requirement. The relevant evidence is: Revoking one compromised credential leaves other applications operational with independent identities. D:Just-in-time privileged access reduces standing exposure while retaining auditable emergency elevation. This is not the decisive validation for the stated requirement. The relevant evidence is: Revoking one compromised credential leaves other applications operational with independent identities.