Question 270An enterprise app retains unused high-privilege OAuth grants from an earlier integration phase. An engineer proposes to inventory granted scopes and remove those no longer required by the supported workflow. Which technical principle most strongly supports that proposal? Reviewing privileged eligibility is a continuous control distinct from sign-in authentication OAuth permission hygiene must reflect actual current application operations, not historic requests A managed identity receives tokens for resource access but still needs explicit target authorization Federated and managed workload credentials avoid persistent secret exposure in deployment definitions ExplanationCorrect Answer B:The technical principle is: OAuth permission hygiene must reflect actual current application operations, not historic requests. It supports the proposed action to inventory granted scopes and remove those no longer required by the supported workflow. Confirmation evidence: A test verifies required API calls succeed while formerly unnecessary scopes are absent. Incorrect Answers A:Reviewing privileged eligibility is a continuous control distinct from sign-in authentication. For the current requirement, the decisive mechanism is: OAuth permission hygiene must reflect actual current application operations, not historic requests. The related action is: Inventory granted scopes and remove those no longer required by the supported workflow. C:A managed identity receives tokens for resource access but still needs explicit target authorization. For the current requirement, the decisive mechanism is: OAuth permission hygiene must reflect actual current application operations, not historic requests. The related action is: Inventory granted scopes and remove those no longer required by the supported workflow. D:Federated and managed workload credentials avoid persistent secret exposure in deployment definitions. For the current requirement, the decisive mechanism is: OAuth permission hygiene must reflect actual current application operations, not historic requests. The related action is: Inventory granted scopes and remove those no longer required by the supported workflow.
Question 271A platform team enables infrastructure encryption but assumes it replaces required customer-managed key controls. After the team acts to validate independent infrastructure encryption and customer-managed key requirements, which observation best demonstrates that the repair worked? A privileged pod test is rejected while normal application deployment continues A partner can download only the authorized object and write/delete attempts are rejected Both encryption settings show expected values and recoverability is tested The intended client mounts the authorized share and a different user fails access ExplanationCorrect Answer C:The expected result is that both encryption settings show expected values and recoverability is tested. This confirms the applicable principle: Infrastructure-level double encryption and customer-managed keys address different encryption controls. Incorrect Answers A:Privileged pods and host mounts can cross the isolation boundary between containers and nodes. This is not the decisive validation for the stated requirement. The relevant evidence is: Both encryption settings show expected values and recoverability is tested. 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: Both encryption settings show expected values and recoverability is tested. D: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: Both encryption settings show expected values and recoverability is tested.
Question 272An engineer exports a Key Vault secret backup to a personal laptop without recording retention and jurisdiction restrictions. Which change best addresses this retired Azure security topic? Inspect effective Azure Policy initiative and individual policy evaluation details Retain framework-specific mapping and assessments rather than equating different standards Evaluate management-group assignment inheritance and use an approved scoped policy exception if justified Use an approved restricted backup destination and test vault object restore ExplanationCorrect Answer D:The relevant technical principle is: Key Vault object backup and restore must preserve custody and supported recovery constraints. The appropriate correction is to use an approved restricted backup destination and test vault object restore. Verify it by checking that A test secret restores through the approved process and backup access is auditable. Incorrect Answers A:An initiative aggregates policy definitions while compliance results can be traced to specific assignments. The operative distinction here is: Key Vault object backup and restore must preserve custody and supported recovery constraints. The targeted change is: Use an approved restricted backup destination and test vault object restore. B:Security control reuse does not make distinct compliance frameworks legally interchangeable. The operative distinction here is: Key Vault object backup and restore must preserve custody and supported recovery constraints. The targeted change is: Use an approved restricted backup destination and test vault object restore. C:Azure Policy effects apply through their assignment scope and inherited governance hierarchy. The operative distinction here is: Key Vault object backup and restore must preserve custody and supported recovery constraints. The targeted change is: Use an approved restricted backup destination and test vault object restore.
Question 273A web team deploys a restrictive Front Door WAF custom rule ahead of managed protections without reviewing priority. After the team acts to evaluate WAF custom rule ordering and managed rule interaction with safe validation traffic, which observation best demonstrates that the repair worked? The test suite proves blocked attacks and legitimate service calls follow intended rules Allowed endpoints work and an unrelated HTTPS destination is denied with a logged rule Rule comparison shows inherited baseline enforcement and audited regional deviations Authorized dependency calls succeed while a test to an unknown external host is denied ExplanationCorrect Answer A:The expected result is that the test suite proves blocked attacks and legitimate service calls follow intended rules. This confirms the applicable principle: WAF rule evaluation order influences whether specific traffic is allowed blocked or inspected. Incorrect Answers B:Allowing a port number alone does not prove the destination service is trustworthy. This is not the decisive validation for the stated requirement. The relevant evidence is: The test suite proves blocked attacks and legitimate service calls follow intended rules. C:Central firewall policies can provide consistent baseline rules across multiple protected hubs. This is not the decisive validation for the stated requirement. The relevant evidence is: The test suite proves blocked attacks and legitimate service calls follow intended rules. D:Outbound NSG filtering can restrict workloads from communicating with unapproved networks. This is not the decisive validation for the stated requirement. The relevant evidence is: The test suite proves blocked attacks and legitimate service calls follow intended rules.
Question 274A newly added spoke uses a default route to the internet rather than its required secure Virtual WAN hub. If this issue remains uncorrected, which outcome is the most direct avoidable risk? Legacy transport negotiation could expose sensitive application data to weak cryptography Spoke traffic might circumvent shared firewall policy Uninspected traffic could cross the network because routing was mistaken for an access control Internet traffic could bypass enterprise egress inspection ExplanationCorrect Answer B:The principal risk is that spoke traffic might circumvent shared firewall policy. The preventative response is to associate its connection with the approved secured virtual hub routing configuration. This matters because virtual WAN hub connection routing must be deliberately configured for centralized security intent. Incorrect Answers A:Transport-layer security configuration must enforce protocol strength at each public termination point. The immediate omission risk in this case is: Spoke traffic might circumvent shared firewall policy. C:User-defined routes choose next hops but are not equivalent to security-filter rules. The immediate omission risk in this case is: Spoke traffic might circumvent shared firewall policy. D:Subnet route tables can steer flows through an Azure virtual appliance for centralized inspection. The immediate omission risk in this case is: Spoke traffic might circumvent shared firewall policy.
Question 275An Azure Arc server remains listed as onboarded but has not uploaded assessment data since a network change. If this issue remains uncorrected, which outcome is the most direct avoidable risk? False compliance assurance could result from an incomplete control model Unscanned external-cloud assets may be overlooked in group security reporting An apparently connected device may be unmonitored for months An outdated credential could persist or cause unplanned authentication failures ExplanationCorrect Answer C:The principal risk is that an apparently connected device may be unmonitored for months. The preventative response is to investigate connector health and telemetry freshness before trusting the inventory status. This matters because asset presence is not equivalent to current posture visibility. Incorrect Answers A:Automated standards assess configured technical signals not all governance or legal obligations. The immediate omission risk in this case is: An apparently connected device may be unmonitored for months. B:Multicloud posture coverage depends on connector authorization and service integration. The immediate omission risk in this case is: An apparently connected device may be unmonitored for months. D:Version-specific references do not automatically track new Key Vault secret versions. The immediate omission risk in this case is: An apparently connected device may be unmonitored for months.
Question 276A GitLab group is excluded from security review because only the company's Azure DevOps tenant was connected. After the team acts to onboard the supported GitLab group with scoped access and test findings visibility, which observation best demonstrates that the repair worked? The target account displays the intended protection status and safe test telemetry routes correctly A simulated compromised operator cannot permanently erase protected recovery points A protected SQL instance reports plan status and relevant security alerts reach the queue The expected GitLab repositories show current supported security assessments ExplanationCorrect Answer D:The expected result is that the expected GitLab repositories show current supported security assessments. This confirms the applicable principle: Defender for Cloud DevOps Security can cover multiple source platforms when explicitly connected. Incorrect Answers A: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: The expected GitLab repositories show current supported security assessments. B:Backup protection requires resilience against compromise of a single powerful identity. This is not the decisive validation for the stated requirement. The relevant evidence is: The expected GitLab repositories show current supported security assessments. C:Database threat detection depends on selected plan and supported resource onboarding. This is not the decisive validation for the stated requirement. The relevant evidence is: The expected GitLab repositories show current supported security assessments.
Question 277A service publishes one exposed public IP but its DDoS plan covers only application-layer HTTP. After the team acts to assess Azure DDoS Protection for network-layer risks at relevant VNet public endpoints, which observation best demonstrates that the repair worked? DDoS telemetry and controlled response plans show protected public IP exposure Unapproved tenant requests remain pending or rejected while approved consumers connect Allowed endpoints work and an unrelated HTTPS destination is denied with a logged rule Rule comparison shows inherited baseline enforcement and audited regional deviations ExplanationCorrect Answer A:The expected result is that DDoS telemetry and controlled response plans show protected public IP exposure. This confirms the applicable principle: Volumetric and protocol-level denial-of-service require controls beyond a web WAF. Incorrect Answers B:Private Link service connection approval governs which private endpoint consumers reach a provider. This is not the decisive validation for the stated requirement. The relevant evidence is: DDoS telemetry and controlled response plans show protected public IP exposure. C:Allowing a port number alone does not prove the destination service is trustworthy. This is not the decisive validation for the stated requirement. The relevant evidence is: DDoS telemetry and controlled response plans show protected public IP exposure. D:Central firewall policies can provide consistent baseline rules across multiple protected hubs. This is not the decisive validation for the stated requirement. The relevant evidence is: DDoS telemetry and controlled response plans show protected public IP exposure.
Question 278A Sentinel playbook closes any incident labeled malware automatically without preserving evidence. If this issue remains uncorrected, which outcome is the most direct avoidable risk? Malformed analytic rules could silently miss active attacker behavior Automatic closure could erase critical investigation opportunities An incomplete scanner configuration can leave inventory falsely presumed assessed An apparently configured connector could stop recording important identity events ExplanationCorrect Answer B:The principal risk is that automatic closure could erase critical investigation opportunities. The preventative response is to require controlled human review or supported safe automation and documented close criteria. This matters because automated incident response must respect evidence integrity and approval boundaries. Incorrect Answers A:Scheduled analytics depend on valid fields tables thresholds and execution schedules. The immediate omission risk in this case is: Automatic closure could erase critical investigation opportunities. C:Agentless VM scanning relies on an authorized snapshot-based assessment workflow. The immediate omission risk in this case is: Automatic closure could erase critical investigation opportunities. D:Microsoft Sentinel connector status depends on source authorization and data flow health. The immediate omission risk in this case is: Automatic closure could erase critical investigation opportunities.
Question 279A newly created Azure subscription is not associated with the company's Defender for Cloud policy management scope. Which change best addresses this retired Azure security topic? Use Secure Score as a prioritization indicator and inspect individual workload findings Update and test the KQL logic against the current schema before re-enabling detections Onboard the subscription and apply intended posture and assessment settings Validate Azure Arc and Defender for Cloud onboarding for the intended hybrid servers ExplanationCorrect Answer C:The relevant technical principle is: Security posture coverage follows configured subscription scope rather than implicit organizational membership. The appropriate correction is to onboard the subscription and apply intended posture and assessment settings. Verify it by checking that the subscription appears in the relevant view with current security recommendations. Incorrect Answers A:Secure Score summarizes selected posture recommendations rather than guaranteeing threat absence. The operative distinction here is: Security posture coverage follows configured subscription scope rather than implicit organizational membership. The targeted change is: Onboard the subscription and apply intended posture and assessment settings. B:Scheduled analytics depend on valid fields tables thresholds and execution schedules. The operative distinction here is: Security posture coverage follows configured subscription scope rather than implicit organizational membership. The targeted change is: Onboard the subscription and apply intended posture and assessment settings. D:Hybrid posture assessment depends on correctly connected and reporting assets. The operative distinction here is: Security posture coverage follows configured subscription scope rather than implicit organizational membership. The targeted change is: Onboard the subscription and apply intended posture and assessment settings.
Question 280A subnet uses an outdated virtual appliance next hop after the firewall VM was readdressed. If this issue remains uncorrected, which outcome is the most direct avoidable risk? One application might fail while another silently reaches a less protected endpoint Internet traffic could bypass enterprise egress inspection Uninspected traffic could cross the network because routing was mistaken for an access control Traffic may blackhole or bypass a security inspection chokepoint ExplanationCorrect Answer D:The principal risk is that traffic may blackhole or bypass a security inspection chokepoint. The preventative response is to update the UDR next hop and validate appliance availability before restoring production flow. This matters because user-defined routes depend on a valid reachable next-hop address for forwarding. Incorrect Answers A:Private DNS resolution is scoped by explicit zone-to-VNet linkage. The immediate omission risk in this case is: Traffic may blackhole or bypass a security inspection chokepoint. B:Subnet route tables can steer flows through an Azure virtual appliance for centralized inspection. The immediate omission risk in this case is: Traffic may blackhole or bypass a security inspection chokepoint. C:User-defined routes choose next hops but are not equivalent to security-filter rules. The immediate omission risk in this case is: Traffic may blackhole or bypass a security inspection chokepoint.