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.
Question 281A team assigns Azure resource Owner to a service principal merely to create log analytics queries. An engineer proposes to replace the role with supported monitoring read permissions at the target workspace. Which technical principle most strongly supports that proposal? Service principals should receive specific resource permissions instead of broad management elevation Federated and managed workload credentials avoid persistent secret exposure in deployment definitions A managed identity receives tokens for resource access but still needs explicit target authorization Temporary role elevation should expire automatically when the approved task is complete ExplanationCorrect Answer A:The technical principle is: Service principals should receive specific resource permissions instead of broad management elevation. It supports the proposed action to replace the role with supported monitoring read permissions at the target workspace. Confirmation evidence: workspace queries succeed but role modification and resource deletion attempts fail. Incorrect Answers B:Federated and managed workload credentials avoid persistent secret exposure in deployment definitions. For the current requirement, the decisive mechanism is: Service principals should receive specific resource permissions instead of broad management elevation. The related action is: Replace the role with supported monitoring read permissions at the target workspace. C:A managed identity receives tokens for resource access but still needs explicit target authorization. For the current requirement, the decisive mechanism is: Service principals should receive specific resource permissions instead of broad management elevation. The related action is: Replace the role with supported monitoring read permissions at the target workspace. D:Temporary role elevation should expire automatically when the approved task is complete. For the current requirement, the decisive mechanism is: Service principals should receive specific resource permissions instead of broad management elevation. The related action is: Replace the role with supported monitoring read permissions at the target workspace.
Question 282A Key Vault stores a TLS certificate that must be renewed but no owner or expiry notification exists. Which change best addresses this retired Azure security topic? Inspect effective Azure Policy initiative and individual policy evaluation details Configure lifecycle ownership and expiration alerts for the certificate Evaluate management-group assignment inheritance and use an approved scoped policy exception if justified Onboard the supported GitLab group with scoped access and test findings visibility ExplanationCorrect Answer B:The relevant technical principle is: Certificate management needs proactive renewal and validation of dependent services. The appropriate correction is to configure lifecycle ownership and expiration alerts for the certificate. Verify it by checking that notification arrives ahead of expiry and the renewed certificate is deployed to the intended listener. Incorrect Answers A:An initiative aggregates policy definitions while compliance results can be traced to specific assignments. The operative distinction here is: Certificate management needs proactive renewal and validation of dependent services. The targeted change is: Configure lifecycle ownership and expiration alerts for the certificate. C:Azure Policy effects apply through their assignment scope and inherited governance hierarchy. The operative distinction here is: Certificate management needs proactive renewal and validation of dependent services. The targeted change is: Configure lifecycle ownership and expiration alerts for the certificate. D:Defender for Cloud DevOps Security can cover multiple source platforms when explicitly connected. The operative distinction here is: Certificate management needs proactive renewal and validation of dependent services. The targeted change is: Configure lifecycle ownership and expiration alerts for the certificate.
Question 283An App Service is deployed with public SCM/Kudu management access contrary to an internal-only operations policy. If this issue remains uncorrected, which outcome is the most direct avoidable risk? Unverified images could introduce malicious code into production pods One compromised app principal might obtain full database control An exposed deployment endpoint could allow unauthorized code changes Compromised application credentials could alter cluster workloads broadly ExplanationCorrect Answer C:The principal risk is that an exposed deployment endpoint could allow unauthorized code changes. The preventative response is to apply supported access restrictions and authentication protection to deployment endpoints. This matters because deployment and administrative endpoints are attack surfaces separate from the public business app. Incorrect Answers A:Container supply-chain integrity depends on trusted build and registry provenance. The immediate omission risk in this case is: An exposed deployment endpoint could allow unauthorized code changes. B:Database permissions should be assigned to legitimate application duties rather than a universal administrator. The immediate omission risk in this case is: An exposed deployment endpoint could allow unauthorized code changes. D:Kubernetes identities can be restricted by resource verb and namespace to enforce least privilege. The immediate omission risk in this case is: An exposed deployment endpoint could allow unauthorized code changes.
Question 284A newly created Azure subscription is not associated with the company's Defender for Cloud policy management scope. After the team acts to onboard the subscription and apply intended posture and assessment settings, which observation best demonstrates that the repair worked? Control mapping identifies assessed evidence and separately tracked manual requirements Each failed control has a reviewed affected-resource list an owner and closure evidence The test event matches the updated rule and produces an investigation alert The subscription appears in the relevant view with current security recommendations ExplanationCorrect Answer D:The expected result is that the subscription appears in the relevant view with current security recommendations. This confirms the applicable principle: Security posture coverage follows configured subscription scope rather than implicit organizational membership. Incorrect Answers A:Automated standards assess configured technical signals not all governance or legal obligations. This is not the decisive validation for the stated requirement. The relevant evidence is: The subscription appears in the relevant view with current security recommendations. B:Regulatory dashboards aggregate control assessments but human governance must resolve deviations. This is not the decisive validation for the stated requirement. The relevant evidence is: The subscription appears in the relevant view with current security recommendations. C:Scheduled analytics depend on valid fields tables thresholds and execution schedules. This is not the decisive validation for the stated requirement. The relevant evidence is: The subscription appears in the relevant view with current security recommendations.
Question 285An analytics vendor receives a delegation key to create broad blob SAS tokens for unrelated containers. An engineer proposes to limit user delegation SAS issuance and validate resource scope permissions and duration. Which technical principle most strongly supports that proposal? Delegated storage token generation requires both authorization of the issuer and constraints on tokens Storage account keys grant broad service authority and must never be embedded in untrusted clients Container security monitoring needs accountable triage rather than indiscriminate alert suppression Shared Access Signatures should constrain permissions resource scope and lifetime ExplanationCorrect Answer A:The technical principle is: Delegated storage token generation requires both authorization of the issuer and constraints on tokens. It supports the proposed action to limit user delegation SAS issuance and validate resource scope permissions and duration. Confirmation evidence: A scoped test token reads only the approved container object and expires promptly. Incorrect Answers B:Storage account keys grant broad service authority and must never be embedded in untrusted clients. For the current requirement, the decisive mechanism is: Delegated storage token generation requires both authorization of the issuer and constraints on tokens. The related action is: Limit user delegation SAS issuance and validate resource scope permissions and duration. C:Container security monitoring needs accountable triage rather than indiscriminate alert suppression. For the current requirement, the decisive mechanism is: Delegated storage token generation requires both authorization of the issuer and constraints on tokens. The related action is: Limit user delegation SAS issuance and validate resource scope permissions and duration. D:Shared Access Signatures should constrain permissions resource scope and lifetime. For the current requirement, the decisive mechanism is: Delegated storage token generation requires both authorization of the issuer and constraints on tokens. The related action is: Limit user delegation SAS issuance and validate resource scope permissions and duration.
Question 286A billing analyst can change security settings because a custom role includes wildcard Microsoft.Authorization actions. After the team acts to edit the custom role to permit only validated cost-reading operations and inspect assignable scopes, which observation best demonstrates that the repair worked? Revoking one compromised credential leaves other applications operational with independent identities Role definition inspection shows read-only billing actions and denied role-assignment writes A supervised emergency test succeeds while sign-in alerts and credential custody remain enforced The privileged test sign-in prompts for required protections and the unmanaged case is denied ExplanationCorrect Answer B:The expected result is that role definition inspection shows read-only billing actions and denied role-assignment writes. This confirms the applicable principle: Custom role action lists determine permissible management-plane operations and must not include unrelated privileges. Incorrect Answers A:Separate principal identity enables granular access revocation and incident attribution. This is not the decisive validation for the stated requirement. The relevant evidence is: Role definition inspection shows read-only billing actions and denied role-assignment writes. C:Emergency access must remain viable when normal authentication or policy configuration is unavailable. This is not the decisive validation for the stated requirement. The relevant evidence is: Role definition inspection shows read-only billing actions and denied role-assignment writes. D:Conditional Access evaluates identity, resource, client context and session risk before granting access. This is not the decisive validation for the stated requirement. The relevant evidence is: Role definition inspection shows read-only billing actions and denied role-assignment writes.
Question 287A financial records vault exposes unencrypted HTTP access to blob objects because TLS is optional in a legacy integration. An engineer proposes to enforce secure transfer required and upgrade clients to approved HTTPS requests. Which technical principle most strongly supports that proposal? Storage account keys grant broad service authority and must never be embedded in untrusted clients Customer-managed TDE protectors create key-availability dependencies for database operations Transport encryption is distinct from storage-at-rest encryption settings Shared Access Signatures should constrain permissions resource scope and lifetime ExplanationCorrect Answer C:The technical principle is: Transport encryption is distinct from storage-at-rest encryption settings. It supports the proposed action to enforce secure transfer required and upgrade clients to approved HTTPS requests. Confirmation evidence: HTTP requests are rejected while HTTPS clients connect using supported protocols. Incorrect Answers A:Storage account keys grant broad service authority and must never be embedded in untrusted clients. For the current requirement, the decisive mechanism is: Transport encryption is distinct from storage-at-rest encryption settings. The related action is: Enforce secure transfer required and upgrade clients to approved HTTPS requests. B:Customer-managed TDE protectors create key-availability dependencies for database operations. For the current requirement, the decisive mechanism is: Transport encryption is distinct from storage-at-rest encryption settings. The related action is: Enforce secure transfer required and upgrade clients to approved HTTPS requests. D:Shared Access Signatures should constrain permissions resource scope and lifetime. For the current requirement, the decisive mechanism is: Transport encryption is distinct from storage-at-rest encryption settings. The related action is: Enforce secure transfer required and upgrade clients to approved HTTPS requests.
Question 288A contractor's Microsoft Entra guest account remains active after the vendor engagement ended. 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 Choose delegated scopes for actions on behalf of signed-in users and validate consent boundaries Disable or remove the guest and revoke relevant sessions while validating access-review closure ExplanationCorrect Answer D:The relevant technical principle is: External identity lifecycle controls must revoke access when the legitimate sponsorship ends. The appropriate correction is to disable or remove the guest and revoke relevant sessions while validating access-review closure. Verify it by checking that the user fails a new sign-in and the sponsor review records removal of the stale guest. Incorrect Answers A:Custom role action lists determine permissible management-plane operations and must not include unrelated privileges. The operative distinction here is: External identity lifecycle controls must revoke access when the legitimate sponsorship ends. The targeted change is: Disable or remove the guest and revoke relevant sessions while validating access-review closure. B:Azure role-based access control should grant the fewest management actions at the smallest workable scope. The operative distinction here is: External identity lifecycle controls must revoke access when the legitimate sponsorship ends. The targeted change is: Disable or remove the guest and revoke relevant sessions while validating access-review closure. C:Delegated permissions act within a user's context while application permissions allow autonomous app access. The operative distinction here is: External identity lifecycle controls must revoke access when the legitimate sponsorship ends. The targeted change is: Disable or remove the guest and revoke relevant sessions while validating access-review closure.
Question 289An AKS namespace grants developers unrestricted ability to create privileged host-mounted pods. After the team acts to apply workload admission restrictions to prohibit unjustified privileged container settings, which observation best demonstrates that the repair worked? A privileged pod test is rejected while normal application deployment continues An inventory read succeeds but an attempted deployment deletion is denied Authorized administrators reach the private API while public endpoint probes fail Unprivileged queries show masked identifiers while approved authorized roles can perform required checks ExplanationCorrect Answer A:The expected result is that A privileged pod test is rejected while normal application deployment continues. This confirms the applicable principle: Privileged pods and host mounts can cross the isolation boundary between containers and nodes. Incorrect Answers B: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: A privileged pod test is rejected while normal application deployment continues. 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: A privileged pod test is rejected while normal application deployment continues. D:Dynamic data masking alters presentation for selected queries and is not complete encryption or access control. This is not the decisive validation for the stated requirement. The relevant evidence is: A privileged pod test is rejected while normal application deployment continues.
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.