Question 570A team confuses virtual network service endpoints with private endpoint IP assignments on a storage account. Which change best addresses this retired Azure security topic? Configure and validate the private endpoint and disable public network access as required Select the access model deliberately and test the resulting service routing and firewall behavior Correct the Private DNS zone linkage and record resolution for the database service Inspect route propagation BGP advertisements and the gateway connection policy before changing NSGs ExplanationCorrect Answer B:The relevant technical principle is: Service Endpoints extend subnet identity to service firewall rules while Private Endpoints provide a private IP interface. The appropriate correction is to select the access model deliberately and test the resulting service routing and firewall behavior. Verify it by checking that the service firewall admits only the intended subnet and DNS behavior matches the chosen model. Incorrect Answers A:Private Endpoints expose supported platform services through private IPs but public endpoints require separate restriction. The operative distinction here is: Service Endpoints extend subnet identity to service firewall rules while Private Endpoints provide a private IP interface. The targeted change is: Select the access model deliberately and test the resulting service routing and firewall behavior. C:Private endpoint connectivity depends on consistent service DNS resolution and reachable VNet links. The operative distinction here is: Service Endpoints extend subnet identity to service firewall rules while Private Endpoints provide a private IP interface. The targeted change is: Select the access model deliberately and test the resulting service routing and firewall behavior. D:A successful VPN tunnel indicates transport establishment but not complete route exchange. The operative distinction here is: Service Endpoints extend subnet identity to service firewall rules while Private Endpoints provide a private IP interface. The targeted change is: Select the access model deliberately and test the resulting service routing and firewall behavior.
Question 571A data team permits permanent SAS tokens with no revocation mechanism for external analytics partners. After the team acts to use time-bounded delegation and documented revocation or stored access policy where applicable, which observation best demonstrates that the repair worked? The intended client mounts the authorized share and a different user fails access A partner can download only the authorized object and write/delete attempts are rejected A retired partner token stops working promptly after the approved access window Each app connects using its assigned database principal and the shared admin login is disabled ExplanationCorrect Answer C:The expected result is that A retired partner token stops working promptly after the approved access window. This confirms the applicable principle: Delegated data access requires a practical expiration and revocation design. Incorrect Answers A:Azure Files supports distinct SMB and REST access patterns with different identity requirements. This is not the decisive validation for the stated requirement. The relevant evidence is: A retired partner token stops working promptly after the approved access window. B:Shared Access Signatures should constrain permissions resource scope and lifetime. This is not the decisive validation for the stated requirement. The relevant evidence is: A retired partner token stops working promptly after the approved access window. D:Identity-based database access improves least privilege and avoids shared administrator secrets. This is not the decisive validation for the stated requirement. The relevant evidence is: A retired partner token stops working promptly after the approved access window.
Question 572A subnet hosting payment APIs permits inbound traffic from the internet on every TCP port. After the team acts to apply scoped NSG inbound rules permitting only the documented required application ports, which observation best demonstrates that the repair worked? An unknown subscription request remains rejected while the approved workload private link succeeds Effective routes show the approved appliance next hop and packet traces confirm traversal Traffic uses the intended inspection path and blocked destinations fail firewall enforcement Allowed application probes succeed while unrelated inbound port attempts are rejected ExplanationCorrect Answer D:The expected result is that allowed application probes succeed while unrelated inbound port attempts are rejected. This confirms the applicable principle: Network Security Groups filter traffic by rule priority direction protocol source destination and port. Incorrect Answers A:Private Endpoint connection states must be governed separately from data-plane authorization. This is not the decisive validation for the stated requirement. The relevant evidence is: Allowed application probes succeed while unrelated inbound port attempts are rejected. B:Subnet route tables can steer flows through an Azure virtual appliance for centralized inspection. This is not the decisive validation for the stated requirement. The relevant evidence is: Allowed application probes succeed while unrelated inbound port attempts are rejected. C:User-defined routes choose next hops but are not equivalent to security-filter rules. This is not the decisive validation for the stated requirement. The relevant evidence is: Allowed application probes succeed while unrelated inbound port attempts are rejected.
Question 573A developer assumes that a user-defined route automatically blocks traffic sent to a risky network. Which change best addresses this retired Azure security topic? Use NSG or firewall enforcement and separately configure a route to the inspection next hop Implement destination-specific outbound rules and validate required service exceptions Change to an appropriately tested prevention policy with necessary managed-rule tuning Apply scoped NSG inbound rules permitting only the documented required application ports ExplanationCorrect Answer A:The relevant technical principle is: User-defined routes choose next hops but are not equivalent to security-filter rules. The appropriate correction is to use NSG or firewall enforcement and separately configure a route to the inspection next hop. Verify it by checking that traffic uses the intended inspection path and blocked destinations fail firewall enforcement. Incorrect Answers B:Outbound NSG filtering can restrict workloads from communicating with unapproved networks. The operative distinction here is: User-defined routes choose next hops but are not equivalent to security-filter rules. The targeted change is: Use NSG or firewall enforcement and separately configure a route to the inspection next hop. C:WAF detection records suspicious traffic but does not itself block requests. The operative distinction here is: User-defined routes choose next hops but are not equivalent to security-filter rules. The targeted change is: Use NSG or firewall enforcement and separately configure a route to the inspection next hop. D:Network Security Groups filter traffic by rule priority direction protocol source destination and port. The operative distinction here is: User-defined routes choose next hops but are not equivalent to security-filter rules. The targeted change is: Use NSG or firewall enforcement and separately configure a route to the inspection next hop.
Question 574An Azure SQL team rotates the TDE customer-managed key without checking the new key version or Key Vault accessibility. Which change best addresses this retired Azure security topic? Configure Microsoft Entra authentication with scoped database identities where supported Validate protector key availability and managed identity access before cutover Enable Azure SQL auditing to an authorized protected destination and validate captured events Limit user delegation SAS issuance and validate resource scope permissions and duration ExplanationCorrect Answer B:The relevant technical principle is: Customer-managed TDE protectors create key-availability dependencies for database operations. The appropriate correction is to validate protector key availability and managed identity access before cutover. Verify it by checking that database availability and encryption state remain healthy after the tested key rotation. Incorrect Answers A:Identity-based database access improves least privilege and avoids shared administrator secrets. The operative distinction here is: Customer-managed TDE protectors create key-availability dependencies for database operations. The targeted change is: Validate protector key availability and managed identity access before cutover. C:Database auditing should preserve evidence of sensitive operations and accountable principal activity. The operative distinction here is: Customer-managed TDE protectors create key-availability dependencies for database operations. The targeted change is: Validate protector key availability and managed identity access before cutover. D:Delegated storage token generation requires both authorization of the issuer and constraints on tokens. The operative distinction here is: Customer-managed TDE protectors create key-availability dependencies for database operations. The targeted change is: Validate protector key availability and managed identity access before cutover.
Question 575An incident response team investigates a role change but has no record of the assigning principal. If this issue remains uncorrected, which outcome is the most direct avoidable risk? 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 Unauthorized elevation might remain unattributed and recur after remediation A stolen password or unmanaged endpoint could permit unauthorized security-policy changes ExplanationCorrect Answer C:The principal risk is that unauthorized elevation might remain unattributed and recur after remediation. The preventative response is to collect Azure Activity Log role assignment operations and correlate initiator identity and scope. This matters because management-plane audit evidence is needed to attribute authorization changes accurately. Incorrect Answers A:Emergency access must remain viable when normal authentication or policy configuration is unavailable. The immediate omission risk in this case is: Unauthorized elevation might remain unattributed and recur after remediation. B:User-assigned managed identities are separate resources and must be attached to the intended workload. The immediate omission risk in this case is: Unauthorized elevation might remain unattributed and recur after remediation. D:Conditional Access evaluates identity, resource, client context and session risk before granting access. The immediate omission risk in this case is: Unauthorized elevation might remain unattributed and recur after remediation.
Question 576An SOC dashboard uses stale Microsoft Defender alerts because no freshness monitor exists for the connector. After the team acts to set ingestion health checks and alert on unexpectedly missing or delayed source events, which observation best demonstrates that the repair worked? Expected test network telemetry reaches the intended workspace with current timestamps The target account displays the intended protection status and safe test telemetry routes correctly A new authorized test sign-in appears in the correct log table after remediation A safe event reaches the correct table inside the expected ingestion window ExplanationCorrect Answer D:The expected result is that A safe event reaches the correct table inside the expected ingestion window. This confirms the applicable principle: Detection visibility depends on continuous log freshness not simply a connected status. Incorrect Answers A:Data collection rules select telemetry resources and destinations rather than collecting all data implicitly. This is not the decisive validation for the stated requirement. The relevant evidence is: A safe event reaches the correct table inside the expected ingestion window. B:Defender for Storage assesses supported threat signals only for protected eligible storage. This is not the decisive validation for the stated requirement. The relevant evidence is: A safe event reaches the correct table inside the expected ingestion window. C:Microsoft Sentinel connector status depends on source authorization and data flow health. This is not the decisive validation for the stated requirement. The relevant evidence is: A safe event reaches the correct table inside the expected ingestion window.
Question 577A service application stores a long-lived client secret directly in an Azure DevOps YAML file. If this issue remains uncorrected, which outcome is the most direct avoidable risk? A leaked pipeline definition could expose reusable credentials for service impersonation Unreviewed audience expansion might expose authentication entry points to unintended organizations One compromised secret could provide access to several unrelated business workloads Reorganization could silently extend privileged access to sensitive logs ExplanationCorrect Answer A:The principal risk is that A leaked pipeline definition could expose reusable credentials for service impersonation. The preventative response is to replace the embedded secret with workload federation or managed identity where supported. This matters because federated and managed workload credentials avoid persistent secret exposure in deployment definitions. Incorrect Answers B:Application sign-in audience settings determine which Microsoft Entra tenants may issue tokens. The immediate omission risk in this case is: A leaked pipeline definition could expose reusable credentials for service impersonation. C:Separate principal identity enables granular access revocation and incident attribution. The immediate omission risk in this case is: A leaked pipeline definition could expose reusable credentials for service impersonation. D:Azure RBAC inheritance follows the management-group subscription resource-group resource hierarchy. The immediate omission risk in this case is: A leaked pipeline definition could expose reusable credentials for service impersonation.
Question 578An enterprise wants encrypted private connectivity over an ExpressRoute circuit without assuming the carrier encrypts payloads. Which change best addresses this retired Azure security topic? Implement destination-specific outbound rules and validate required service exceptions Plan an overlay encryption option such as IPsec over ExpressRoute where supported Correct the Private DNS zone linkage and record resolution for the database service Apply scoped NSG inbound rules permitting only the documented required application ports ExplanationCorrect Answer B:The relevant technical principle is: ExpressRoute offers private connectivity but does not by itself guarantee end-to-end payload encryption. The appropriate correction is to plan an overlay encryption option such as IPsec over ExpressRoute where supported. Verify it by checking that packet-level checks confirm protected tunnel traffic across the private circuit. Incorrect Answers A:Outbound NSG filtering can restrict workloads from communicating with unapproved networks. The operative distinction here is: ExpressRoute offers private connectivity but does not by itself guarantee end-to-end payload encryption. The targeted change is: Plan an overlay encryption option such as IPsec over ExpressRoute where supported. C:Private endpoint connectivity depends on consistent service DNS resolution and reachable VNet links. The operative distinction here is: ExpressRoute offers private connectivity but does not by itself guarantee end-to-end payload encryption. The targeted change is: Plan an overlay encryption option such as IPsec over ExpressRoute where supported. D:Network Security Groups filter traffic by rule priority direction protocol source destination and port. The operative distinction here is: ExpressRoute offers private connectivity but does not by itself guarantee end-to-end payload encryption. The targeted change is: Plan an overlay encryption option such as IPsec over ExpressRoute where supported.
Question 579A virtual network has two NSGs whose combined effect is assumed to be an unrestricted allow. If this issue remains uncorrected, which outcome is the most direct avoidable risk? Internet traffic could bypass enterprise egress inspection Stale allowlists could be mistaken for proof of private-endpoint enforcement A misunderstood rule chain may cause harmful blanket exceptions Uninspected traffic could cross the network because routing was mistaken for an access control ExplanationCorrect Answer C:The principal risk is that A misunderstood rule chain may cause harmful blanket exceptions. The preventative response is to evaluate subnet and NIC effective security rules rather than inspecting only one attached NSG. This matters because traffic must satisfy applicable security rules across both subnet and interface boundaries. Incorrect Answers A:Subnet route tables can steer flows through an Azure virtual appliance for centralized inspection. The immediate omission risk in this case is: A misunderstood rule chain may cause harmful blanket exceptions. B:Private endpoint connectivity is evaluated differently from public service IP firewall rules. The immediate omission risk in this case is: A misunderstood rule chain may cause harmful blanket exceptions. D:User-defined routes choose next hops but are not equivalent to security-filter rules. The immediate omission risk in this case is: A misunderstood rule chain may cause harmful blanket exceptions.
Question 580A privileged identity stays eligible for a full year despite a short emergency migration window. An engineer proposes to reduce PIM eligibility duration and require periodic access review against the migration plan. Which technical principle most strongly supports that proposal? Admin consent may authorize high-impact access far beyond a user's immediate reporting need Just-in-time privileged access reduces standing exposure while retaining auditable emergency elevation Custom role action lists determine permissible management-plane operations and must not include unrelated privileges Eligibility itself has a lifecycle and should not be broader than the legitimate business need ExplanationCorrect Answer D:The technical principle is: Eligibility itself has a lifecycle and should not be broader than the legitimate business need. It supports the proposed action to reduce PIM eligibility duration and require periodic access review against the migration plan. Confirmation evidence: access review removes unused eligibility and the final activation expires according to policy. Incorrect Answers A:Admin consent may authorize high-impact access far beyond a user's immediate reporting need. For the current requirement, the decisive mechanism is: Eligibility itself has a lifecycle and should not be broader than the legitimate business need. The related action is: Reduce PIM eligibility duration and require periodic access review against the migration plan. B:Just-in-time privileged access reduces standing exposure while retaining auditable emergency elevation. For the current requirement, the decisive mechanism is: Eligibility itself has a lifecycle and should not be broader than the legitimate business need. The related action is: Reduce PIM eligibility duration and require periodic access review against the migration plan. C:Custom role action lists determine permissible management-plane operations and must not include unrelated privileges. For the current requirement, the decisive mechanism is: Eligibility itself has a lifecycle and should not be broader than the legitimate business need. The related action is: Reduce PIM eligibility duration and require periodic access review against the migration plan.