Question 460A development vault is reachable from arbitrary networks despite storing sensitive production integration secrets. Which governance action most directly addresses the recurring risk? Maintain private DNS and endpoint approval tests across network changes. Document peering relationships, address-space conflicts, and reciprocal approvals before deployment. Review Key Vault access scopes and privilege changes during identity recertification. Test network ACL and private endpoint settings whenever vault connectivity changes. ExplanationCorrect Answer D:Test network ACL and private endpoint settings whenever vault connectivity changes. Maintaining this control reduces recurrence because: Network access rules constrain the path to a vault while authorization still governs what an identity can do. The immediate response remains: Configure supported Key Vault network restrictions or private connectivity in addition to identity access controls. Other Answers A:Private Link exposes a service through a private IP in a virtual network, unlike mere encryption of public traffic. The lasting safeguard is to test network ACL and private endpoint settings whenever vault connectivity changes. B:VNet peering connects Azure virtual networks over private routing while NSG and other controls still govern allowed traffic. The lasting safeguard is to test network ACL and private endpoint settings whenever vault connectivity changes. C:Permissions to retrieve secrets and permissions to administer or delete vault objects can be separated. The stronger recurring control is to test network ACL and private endpoint settings whenever vault connectivity changes.
Question 461An operator deletes a Key Vault secret and discovers that its recovery policy had never been reviewed before production use. Which action most directly resolves the security or identity requirement? Apply least-privilege Key Vault data access with the appropriate RBAC roles or supported permissions model. Enable the appropriate Key Vault soft-delete and purge-protection safeguards for required recovery objectives. Store the secret in Azure Key Vault and use an authorized application identity to retrieve its current value. Enable an appropriate Azure DDoS Protection plan for the exposed network and combine it with application security controls. ExplanationCorrect Answer B:Soft delete permits recovery during a retention period, while purge protection resists permanent destruction before the allowed point. To confirm, delete a controlled test secret and verify restoration while an unauthorized purge cannot bypass policy. Other Answers A:Permissions to retrieve secrets and permissions to administer or delete vault objects can be separated. The required change instead is to enable the appropriate Key Vault soft-delete and purge-protection safeguards for required recovery objectives. C:Key Vault separates secret storage and access authorization from application code and deployment artifacts. A more relevant action is to enable the appropriate Key Vault soft-delete and purge-protection safeguards for required recovery objectives. D:Network-layer volumetric attacks exhaust connectivity before application authentication can evaluate a request. This failure calls for a decision to enable the appropriate Key Vault soft-delete and purge-protection safeguards for required recovery objectives.
Question 462An operator deletes a Key Vault secret and discovers that its recovery policy had never been reviewed before production use. Which technical distinction is decisive in this case? Soft delete permits recovery during a retention period, while purge protection resists permanent destruction before the allowed point. Key Vault separates secret storage and access authorization from application code and deployment artifacts. Network-layer volumetric attacks exhaust connectivity before application authentication can evaluate a request. Permissions to retrieve secrets and permissions to administer or delete vault objects can be separated. ExplanationCorrect Answer A:Soft delete permits recovery during a retention period, while purge protection resists permanent destruction before the allowed point. This is the principle behind: Enable the appropriate Key Vault soft-delete and purge-protection safeguards for required recovery objectives. The evidence to inspect is: Delete a controlled test secret and verify restoration while an unauthorized purge cannot bypass policy. Other Answers B:Key Vault separates secret storage and access authorization from application code and deployment artifacts. By contrast, soft delete permits recovery during a retention period, while purge protection resists permanent destruction before the allowed point. C:Network-layer volumetric attacks exhaust connectivity before application authentication can evaluate a request. In the stated system, soft delete permits recovery during a retention period, while purge protection resists permanent destruction before the allowed point. D:Permissions to retrieve secrets and permissions to administer or delete vault objects can be separated. By contrast, soft delete permits recovery during a retention period, while purge protection resists permanent destruction before the allowed point.
Question 463An operator deletes a Key Vault secret and discovers that its recovery policy had never been reviewed before production use. Which observation best validates the chosen approach? Review attack telemetry and conduct an approved resilience test of the protected public endpoint. Verify a reader retrieves the approved secret and receives a denial when attempting to delete one. Rotate the test secret and confirm the application retrieves the authorized version without a code change. Delete a controlled test secret and verify restoration while an unauthorized purge cannot bypass policy. ExplanationCorrect Answer D:Delete a controlled test secret and verify restoration while an unauthorized purge cannot bypass policy. This test checks the expected result of: Enable the appropriate Key Vault soft-delete and purge-protection safeguards for required recovery objectives. It matters because: Soft delete permits recovery during a retention period, while purge protection resists permanent destruction before the allowed point. Other Answers A:Network-layer volumetric attacks exhaust connectivity before application authentication can evaluate a request. A more meaningful verification is to delete a controlled test secret and verify restoration while an unauthorized purge cannot bypass policy. B:Permissions to retrieve secrets and permissions to administer or delete vault objects can be separated. The relevant acceptance check is to delete a controlled test secret and verify restoration while an unauthorized purge cannot bypass policy. C:Key Vault separates secret storage and access authorization from application code and deployment artifacts. The failure is checked more directly by a test to delete a controlled test secret and verify restoration while an unauthorized purge cannot bypass policy.
Question 464An operator deletes a Key Vault secret and discovers that its recovery policy had never been reviewed before production use. Which governance action most directly addresses the recurring risk? Review Key Vault access scopes and privilege changes during identity recertification. Require vault recovery settings and retention compliance checks during provisioning. Use managed identities and secret-rotation procedures for application credentials. Include DDoS exposure and response procedures in public IP architecture reviews. ExplanationCorrect Answer B:Require vault recovery settings and retention compliance checks during provisioning. Maintaining this control reduces recurrence because: Soft delete permits recovery during a retention period, while purge protection resists permanent destruction before the allowed point. The immediate response remains: Enable the appropriate Key Vault soft-delete and purge-protection safeguards for required recovery objectives. Other Answers A:Permissions to retrieve secrets and permissions to administer or delete vault objects can be separated. A more direct preventive measure is to require vault recovery settings and retention compliance checks during provisioning. C:Key Vault separates secret storage and access authorization from application code and deployment artifacts. The lasting safeguard is to require vault recovery settings and retention compliance checks during provisioning. D:Network-layer volumetric attacks exhaust connectivity before application authentication can evaluate a request. Reducing this risk requires a practice to require vault recovery settings and retention compliance checks during provisioning.
Question 465A company enables DDoS protections but only looks at CPU metrics from the affected web server when responding to an attack. Which action most directly resolves the security or identity requirement? Enable an appropriate Azure DDoS Protection plan for the exposed network and combine it with application security controls. Review Azure DDoS attack metrics and diagnostic logs alongside application and network observations. Enable the supported WAF configuration on the Application Gateway actually forwarding the application traffic. Deploy and tune Azure Web Application Firewall policies in front of the web application. ExplanationCorrect Answer B:DDoS-specific telemetry reveals mitigation events and traffic patterns beyond guest operating system load. To confirm, correlate a safe test mitigation record with network flow and service availability measurements. Other Answers A:Network-layer volumetric attacks exhaust connectivity before application authentication can evaluate a request. This failure calls for a decision to review Azure DDoS attack metrics and diagnostic logs alongside application and network observations. C:A WAF policy protects only flows traversing its associated gateway or edge endpoint. This failure calls for a decision to review Azure DDoS attack metrics and diagnostic logs alongside application and network observations. D:A WAF evaluates HTTP request patterns and managed rules; an NSG port rule does not inspect injection payload semantics. The required change instead is to review Azure DDoS attack metrics and diagnostic logs alongside application and network observations.
Question 466A company enables DDoS protections but only looks at CPU metrics from the affected web server when responding to an attack. Which technical distinction is decisive in this case? A WAF evaluates HTTP request patterns and managed rules; an NSG port rule does not inspect injection payload semantics. A WAF policy protects only flows traversing its associated gateway or edge endpoint. Network-layer volumetric attacks exhaust connectivity before application authentication can evaluate a request. DDoS-specific telemetry reveals mitigation events and traffic patterns beyond guest operating system load. ExplanationCorrect Answer D:DDoS-specific telemetry reveals mitigation events and traffic patterns beyond guest operating system load. This is the principle behind: Review Azure DDoS attack metrics and diagnostic logs alongside application and network observations. The evidence to inspect is: Correlate a safe test mitigation record with network flow and service availability measurements. Other Answers A:A WAF evaluates HTTP request patterns and managed rules; an NSG port rule does not inspect injection payload semantics. In the stated system, dDoS-specific telemetry reveals mitigation events and traffic patterns beyond guest operating system load. B:A WAF policy protects only flows traversing its associated gateway or edge endpoint. In the stated system, dDoS-specific telemetry reveals mitigation events and traffic patterns beyond guest operating system load. C:Network-layer volumetric attacks exhaust connectivity before application authentication can evaluate a request. In the stated system, dDoS-specific telemetry reveals mitigation events and traffic patterns beyond guest operating system load.
Question 467A company enables DDoS protections but only looks at CPU metrics from the affected web server when responding to an attack. Which observation best validates the chosen approach? Review attack telemetry and conduct an approved resilience test of the protected public endpoint. Send harmless representative malicious-pattern tests and confirm the WAF logs or blocks them without blocking valid requests. Send a controlled rule-triggering HTTP request through the real gateway listener and check enforcement. Correlate a safe test mitigation record with network flow and service availability measurements. ExplanationCorrect Answer D:Correlate a safe test mitigation record with network flow and service availability measurements. This test checks the expected result of: Review Azure DDoS attack metrics and diagnostic logs alongside application and network observations. It matters because: DDoS-specific telemetry reveals mitigation events and traffic patterns beyond guest operating system load. Other Answers A:Network-layer volumetric attacks exhaust connectivity before application authentication can evaluate a request. A more meaningful verification is to correlate a safe test mitigation record with network flow and service availability measurements. B:A WAF evaluates HTTP request patterns and managed rules; an NSG port rule does not inspect injection payload semantics. The relevant acceptance check is to correlate a safe test mitigation record with network flow and service availability measurements. C:A WAF policy protects only flows traversing its associated gateway or edge endpoint. A more meaningful verification is to correlate a safe test mitigation record with network flow and service availability measurements.
Question 468A company enables DDoS protections but only looks at CPU metrics from the affected web server when responding to an attack. Which governance action most directly addresses the recurring risk? Retain incident-ready DDoS dashboards and escalation ownership for internet-facing workloads. Include DDoS exposure and response procedures in public IP architecture reviews. Review WAF rule updates and false-positive exclusions with application owners. Map each web listener to its required WAF policy during application onboarding. ExplanationCorrect Answer A:Retain incident-ready DDoS dashboards and escalation ownership for internet-facing workloads. Maintaining this control reduces recurrence because: DDoS-specific telemetry reveals mitigation events and traffic patterns beyond guest operating system load. The immediate response remains: Review Azure DDoS attack metrics and diagnostic logs alongside application and network observations. Other Answers B:Network-layer volumetric attacks exhaust connectivity before application authentication can evaluate a request. The stronger recurring control is to retain incident-ready DDoS dashboards and escalation ownership for internet-facing workloads. C:A WAF evaluates HTTP request patterns and managed rules; an NSG port rule does not inspect injection payload semantics. Reducing this risk requires a practice to retain incident-ready DDoS dashboards and escalation ownership for internet-facing workloads. D:A WAF policy protects only flows traversing its associated gateway or edge endpoint. The stronger recurring control is to retain incident-ready DDoS dashboards and escalation ownership for internet-facing workloads.
Question 469Two Azure virtual networks require private connectivity for approved services, but the architecture routes all traffic over public application endpoints. Which action most directly resolves the security or identity requirement? Design explicit supported routing or hub connectivity for the intended spoke-to-spoke access rather than assuming peering is transitive. Configure supported virtual network peering and authorize only the required cross-network connections. Segment workloads into appropriate subnets and enforce allowed cross-subnet traffic with network controls. Configure a supported Azure Private Endpoint and corresponding private DNS resolution plus resource access restrictions. ExplanationCorrect Answer B:VNet peering connects Azure virtual networks over private routing while NSG and other controls still govern allowed traffic. To confirm, test traffic between approved private addresses and verify the expected routes and access rules. Other Answers A:VNet peering by itself is not transitive; additional routing or connectivity architecture may be required. This failure calls for a decision to configure supported virtual network peering and authorize only the required cross-network connections. C:Azure virtual network topology and rule enforcement separate traffic; labels and naming do not create isolation. The corrective action for this requirement is to configure supported virtual network peering and authorize only the required cross-network connections. D:Private Link exposes a service through a private IP in a virtual network, unlike mere encryption of public traffic. This failure calls for a decision to configure supported virtual network peering and authorize only the required cross-network connections.
Question 470Two Azure virtual networks require private connectivity for approved services, but the architecture routes all traffic over public application endpoints. Which technical distinction is decisive in this case? VNet peering by itself is not transitive; additional routing or connectivity architecture may be required. Private Link exposes a service through a private IP in a virtual network, unlike mere encryption of public traffic. VNet peering connects Azure virtual networks over private routing while NSG and other controls still govern allowed traffic. Azure virtual network topology and rule enforcement separate traffic; labels and naming do not create isolation. ExplanationCorrect Answer C:VNet peering connects Azure virtual networks over private routing while NSG and other controls still govern allowed traffic. This is the principle behind: Configure supported virtual network peering and authorize only the required cross-network connections. The evidence to inspect is: Test traffic between approved private addresses and verify the expected routes and access rules. Other Answers A:VNet peering by itself is not transitive; additional routing or connectivity architecture may be required. By contrast, vNet peering connects Azure virtual networks over private routing while NSG and other controls still govern allowed traffic. B:Private Link exposes a service through a private IP in a virtual network, unlike mere encryption of public traffic. By contrast, vNet peering connects Azure virtual networks over private routing while NSG and other controls still govern allowed traffic. D:Azure virtual network topology and rule enforcement separate traffic; labels and naming do not create isolation. By contrast, vNet peering connects Azure virtual networks over private routing while NSG and other controls still govern allowed traffic.