Question 290An enterprise wants encrypted private connectivity over an ExpressRoute circuit without assuming the carrier encrypts payloads. An engineer proposes to plan an overlay encryption option such as IPsec over ExpressRoute where supported. Which technical principle most strongly supports that proposal? Application Security Groups let rules refer to virtual machine groupings instead of brittle IP lists ExpressRoute offers private connectivity but does not by itself guarantee end-to-end payload encryption Private endpoint connectivity depends on consistent service DNS resolution and reachable VNet links Outbound NSG filtering can restrict workloads from communicating with unapproved networks ExplanationCorrect Answer B:The technical principle is: ExpressRoute offers private connectivity but does not by itself guarantee end-to-end payload encryption. It supports the proposed action to plan an overlay encryption option such as IPsec over ExpressRoute where supported. Confirmation evidence: packet-level checks confirm protected tunnel traffic across the private circuit. Incorrect Answers A:Application Security Groups let rules refer to virtual machine groupings instead of brittle IP lists. For the current requirement, the decisive mechanism is: ExpressRoute offers private connectivity but does not by itself guarantee end-to-end payload encryption. The related action 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. For the current requirement, the decisive mechanism is: ExpressRoute offers private connectivity but does not by itself guarantee end-to-end payload encryption. The related action is: Plan an overlay encryption option such as IPsec over ExpressRoute where supported. D:Outbound NSG filtering can restrict workloads from communicating with unapproved networks. For the current requirement, the decisive mechanism is: ExpressRoute offers private connectivity but does not by itself guarantee end-to-end payload encryption. The related action is: Plan an overlay encryption option such as IPsec over ExpressRoute where supported.
Question 291A web application runs behind Application Gateway but client requests bypass it through the backend public IP. An engineer proposes to restrict backend reachability to the approved gateway path and validate health probes. Which technical principle most strongly supports that proposal? Service endpoint lifecycles require DNS and connection-state consistency Allowing a port number alone does not prove the destination service is trustworthy Layer-7 gateway security is ineffective when the original service stays directly accessible TLS listener availability depends on valid configured server certificates and renewed trust ExplanationCorrect Answer C:The technical principle is: Layer-7 gateway security is ineffective when the original service stays directly accessible. It supports the proposed action to restrict backend reachability to the approved gateway path and validate health probes. Confirmation evidence: gateway-origin traffic reaches the backend but direct public requests are blocked. Incorrect Answers A:Service endpoint lifecycles require DNS and connection-state consistency. For the current requirement, the decisive mechanism is: Layer-7 gateway security is ineffective when the original service stays directly accessible. The related action is: Restrict backend reachability to the approved gateway path and validate health probes. B:Allowing a port number alone does not prove the destination service is trustworthy. For the current requirement, the decisive mechanism is: Layer-7 gateway security is ineffective when the original service stays directly accessible. The related action is: Restrict backend reachability to the approved gateway path and validate health probes. D:TLS listener availability depends on valid configured server certificates and renewed trust. For the current requirement, the decisive mechanism is: Layer-7 gateway security is ineffective when the original service stays directly accessible. The related action is: Restrict backend reachability to the approved gateway path and validate health probes.
Question 292A banking API still accepts TLS 1.0 connections from the internet despite an approved modern protocol baseline. Which change best addresses this retired Azure security topic? Rotate the listener certificate using controlled Key Vault integration or approved certificate deployment Configure supported Function App VNet integration with subnet and DNS settings Create specific application or network rules with documented destinations and logging Set the minimum supported TLS version on the application endpoint and test legacy-client rejection ExplanationCorrect Answer D:The relevant technical principle is: Transport-layer security configuration must enforce protocol strength at each public termination point. The appropriate correction is to set the minimum supported TLS version on the application endpoint and test legacy-client rejection. Verify it by checking that an obsolete TLS client fails the handshake while an approved modern client succeeds. Incorrect Answers A:TLS listener availability depends on valid configured server certificates and renewed trust. The operative distinction here is: Transport-layer security configuration must enforce protocol strength at each public termination point. The targeted change is: Set the minimum supported TLS version on the application endpoint and test legacy-client rejection. B:App Service VNet integration enables outbound routing into a VNet but does not automatically restrict inbound traffic. The operative distinction here is: Transport-layer security configuration must enforce protocol strength at each public termination point. The targeted change is: Set the minimum supported TLS version on the application endpoint and test legacy-client rejection. C:Allowing a port number alone does not prove the destination service is trustworthy. The operative distinction here is: Transport-layer security configuration must enforce protocol strength at each public termination point. The targeted change is: Set the minimum supported TLS version on the application endpoint and test legacy-client rejection.
Question 293A Key Vault is configured with public network access enabled even though it stores production database encryption keys. An engineer proposes to require the approved vault private endpoint or network access restrictions. Which technical principle most strongly supports that proposal? Vault network access is a separate security boundary from access to keys and secrets Azure Policy effects apply through their assignment scope and inherited governance hierarchy Security recommendation dispositions need verifiable justification and review Azure Policy audit detects conditions whereas deny and modify can enforce or change deployments ExplanationCorrect Answer A:The technical principle is: Vault network access is a separate security boundary from access to keys and secrets. It supports the proposed action to require the approved vault private endpoint or network access restrictions. Confirmation evidence: approved private clients can read authorized objects while public-origin requests fail. Incorrect Answers B:Azure Policy effects apply through their assignment scope and inherited governance hierarchy. For the current requirement, the decisive mechanism is: Vault network access is a separate security boundary from access to keys and secrets. The related action is: Require the approved vault private endpoint or network access restrictions. C:Security recommendation dispositions need verifiable justification and review. For the current requirement, the decisive mechanism is: Vault network access is a separate security boundary from access to keys and secrets. The related action is: Require the approved vault private endpoint or network access restrictions. D:Azure Policy audit detects conditions whereas deny and modify can enforce or change deployments. For the current requirement, the decisive mechanism is: Vault network access is a separate security boundary from access to keys and secrets. The related action is: Require the approved vault private endpoint or network access restrictions.
Question 294An enterprise security team sets PIM activation duration longer than its approved maintenance window. An engineer proposes to reduce eligible activation duration and align extension requests with accountable approvals. Which technical principle most strongly supports that proposal? Service principals should receive specific resource permissions instead of broad management elevation Temporary role elevation should expire automatically when the approved task is complete 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 ExplanationCorrect Answer B:The technical principle is: Temporary role elevation should expire automatically when the approved task is complete. It supports the proposed action to reduce eligible activation duration and align extension requests with accountable approvals. Confirmation evidence: privilege deactivates after the approved short window and subsequent actions are denied. Incorrect Answers A:Service principals should receive specific resource permissions instead of broad management elevation. For the current requirement, the decisive mechanism is: Temporary role elevation should expire automatically when the approved task is complete. The related action is: Reduce eligible activation duration and align extension requests with accountable approvals. C:Custom role action lists determine permissible management-plane operations and must not include unrelated privileges. For the current requirement, the decisive mechanism is: Temporary role elevation should expire automatically when the approved task is complete. The related action is: Reduce eligible activation duration and align extension requests with accountable approvals. D:Just-in-time privileged access reduces standing exposure while retaining auditable emergency elevation. For the current requirement, the decisive mechanism is: Temporary role elevation should expire automatically when the approved task is complete. The related action is: Reduce eligible activation duration and align extension requests with accountable approvals.
Question 295A resource-group role assignment is inherited by new resources containing confidential logs unexpectedly. Which change best addresses this retired Azure security topic? 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 Review inherited role scope before moving sensitive resources into that group Replace the embedded secret with workload federation or managed identity where supported ExplanationCorrect Answer C:The relevant technical principle is: Azure RBAC inheritance follows the management-group subscription resource-group resource hierarchy. The appropriate correction is to review inherited role scope before moving sensitive resources into that group. Verify it by checking that 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. The operative distinction here is: Azure RBAC inheritance follows the management-group subscription resource-group resource hierarchy. The targeted change is: Review inherited role scope before moving sensitive resources into that group. B:Azure role-based access control should grant the fewest management actions at the smallest workable scope. The operative distinction here is: Azure RBAC inheritance follows the management-group subscription resource-group resource hierarchy. The targeted change 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. The operative distinction here is: Azure RBAC inheritance follows the management-group subscription resource-group resource hierarchy. The targeted change is: Review inherited role scope before moving sensitive resources into that group.
Question 296A private endpoint request for a critical Key Vault is automatically approved from any subscription in the tenant. After the team acts to require explicit approved connection requests and verify requester subscription identity, which observation best demonstrates that the repair worked? The service firewall admits only the intended subnet and DNS behavior matches the chosen model VM public port scans fail while authenticated administrators use the approved management service The function resolves and reaches the private database without relying on a public connection An unknown subscription request remains rejected while the approved workload private link succeeds ExplanationCorrect Answer D:The expected result is that an unknown subscription request remains rejected while the approved workload private link succeeds. This confirms the applicable principle: Private Endpoint connection states must be governed separately from data-plane authorization. Incorrect Answers A:Service Endpoints extend subnet identity to service firewall rules while Private Endpoints provide a private IP interface. This is not the decisive validation for the stated requirement. The relevant evidence is: An unknown subscription request remains rejected while the approved workload private link succeeds. B:Private management paths reduce direct internet attack surface on compute resources. This is not the decisive validation for the stated requirement. The relevant evidence is: An unknown subscription request remains rejected while the approved workload private link succeeds. C:App Service VNet integration enables outbound routing into a VNet but does not automatically restrict inbound traffic. This is not the decisive validation for the stated requirement. The relevant evidence is: An unknown subscription request remains rejected while the approved workload private link succeeds.
Question 297A security operations team treats a Microsoft Defender for Cloud alert as confirmed compromise and isolates a host without corroboration. Which change best addresses this retired Azure security topic? Review alert entity context and perform authorized evidence-led triage before containment Use governed workflow automation with scoped identity and a reviewed response playbook Define specific supported data sources destinations and collection scope in a DCR Prioritize remediation by exposure severity and threat context alongside Secure Score effect ExplanationCorrect Answer A:The relevant technical principle is: Security alerts are investigation signals and response action should reflect validated risk. The appropriate correction is to review alert entity context and perform authorized evidence-led triage before containment. Verify it by checking that the case documents timeline supporting evidence and proportionate authorized containment. Incorrect Answers B:Cloud alert automation needs least-privilege execution and accountable response boundaries. The operative distinction here is: Security alerts are investigation signals and response action should reflect validated risk. The targeted change is: Review alert entity context and perform authorized evidence-led triage before containment. C:Data collection rules select telemetry resources and destinations rather than collecting all data implicitly. The operative distinction here is: Security alerts are investigation signals and response action should reflect validated risk. The targeted change is: Review alert entity context and perform authorized evidence-led triage before containment. D:Risk-based posture management weighs actual exposure rather than only aggregate score improvements. The operative distinction here is: Security alerts are investigation signals and response action should reflect validated risk. The targeted change is: Review alert entity context and perform authorized evidence-led triage before containment.
Question 298A security team attaches identical NSG rules to five unrelated subnets with different intended roles. If this issue remains uncorrected, which outcome is the most direct avoidable risk? Internet traffic could bypass enterprise egress inspection Duplicated IP-based rules could drift and expose newly added services Expired certificates could cause client failures and unsafe validation bypasses Assuming automatic transit can cause outages or ad hoc insecure bypass paths ExplanationCorrect Answer B:The principal risk is that duplicated IP-based rules could drift and expose newly added services. The preventative response is to define Application Security Groups and scope policy by workload function where supported. This matters because application Security Groups let rules refer to virtual machine groupings instead of brittle IP lists. 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: Duplicated IP-based rules could drift and expose newly added services. C:TLS listener availability depends on valid configured server certificates and renewed trust. The immediate omission risk in this case is: Duplicated IP-based rules could drift and expose newly added services. D:VNet peering alone does not create unrestricted transitive network connectivity. The immediate omission risk in this case is: Duplicated IP-based rules could drift and expose newly added services.
Question 299An app registration is configured for a single tenant but developers try to sign in customers from unrelated tenants. After the team acts to validate supported audience and tenant authorization requirements before enabling multi-tenant access, which observation best demonstrates that the repair worked? Enterprise application permission review shows only required reporting grants and resource scope The function retrieves the intended secret while a different identity remains denied Expected tenant users authenticate and unrelated tenants fail per the approved product design A new restricted log workspace does not grant unintended access through its parent scope ExplanationCorrect Answer C:The expected result is that expected tenant users authenticate and unrelated tenants fail per the approved product design. This confirms the applicable principle: Application sign-in audience settings determine which Microsoft Entra tenants may issue tokens. Incorrect Answers A: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: Expected tenant users authenticate and unrelated tenants fail per the approved product design. B: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: Expected tenant users authenticate and unrelated tenants fail per the approved product design. D:Azure RBAC inheritance follows the management-group subscription resource-group resource hierarchy. This is not the decisive validation for the stated requirement. The relevant evidence is: Expected tenant users authenticate and unrelated tenants fail per the approved product design.
Question 300A workload's system-assigned managed identity has Reader on a VM but developers expect it to mount Azure Files with data rights. After the team acts to grant the relevant storage data permission or authenticated SMB identity appropriate to the share, which observation best demonstrates that the repair worked? An inventory read succeeds but an attempted deployment deletion is denied A partner can download only the authorized object and write/delete attempts are rejected Authorized administrators reach the private API while public endpoint probes fail The approved workload reads the intended share while unrelated shares remain inaccessible ExplanationCorrect Answer D:The expected result is that the approved workload reads the intended share while unrelated shares remain inaccessible. This confirms the applicable principle: Azure management-plane Reader is not equivalent to file-share data authorization. Incorrect Answers A:Kubernetes identities can be restricted by resource verb and namespace to enforce least privilege. This is not the decisive validation for the stated requirement. The relevant evidence is: The approved workload reads the intended share while unrelated shares remain inaccessible. 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: The approved workload reads the intended share while unrelated shares remain inaccessible. C:AKS control-plane exposure should match the documented management-network threat model. This is not the decisive validation for the stated requirement. The relevant evidence is: The approved workload reads the intended share while unrelated shares remain inaccessible.