Question 340A data protection team rotates a vault key manually without tracking which storage services consume its versions. If this issue remains uncorrected, which outcome is the most direct avoidable risk? Unprivileged remediation jobs could leave widespread misleading noncompliance A stolen vault credential could be used from an unauthorized network Unscanned external-cloud assets may be overlooked in group security reporting Careless key rotation could make dependent encrypted services unavailable ExplanationCorrect Answer D:The principal risk is that careless key rotation could make dependent encrypted services unavailable. The preventative response is to define a key rotation policy and validate downstream service compatibility with version handling. This matters because cryptographic key rotation must consider dependent service encryption operations and version references. Incorrect Answers A:Policy modification and remediation require authorization for the policy assignment identity. The immediate omission risk in this case is: Careless key rotation could make dependent encrypted services unavailable. B:Vault network access is a separate security boundary from access to keys and secrets. The immediate omission risk in this case is: Careless key rotation could make dependent encrypted services unavailable. C:Multicloud posture coverage depends on connector authorization and service integration. The immediate omission risk in this case is: Careless key rotation could make dependent encrypted services unavailable.
Question 341A tenant has unmanaged keys in several subscriptions with no evidence of authorized rotation policy. If this issue remains uncorrected, which outcome is the most direct avoidable risk? Forgotten keys could expire or remain compromised without detection Unprivileged remediation jobs could leave widespread misleading noncompliance A stolen vault credential could be used from an unauthorized network A workload may lack behavioral threat monitoring despite successful vulnerability scans ExplanationCorrect Answer A:The principal risk is that forgotten keys could expire or remain compromised without detection. The preventative response is to create an inventory of Key Vault keys and assign accountable rotation policies by data classification. This matters because key governance should map purpose owner lifecycle and dependent resources for each key. Incorrect Answers B:Policy modification and remediation require authorization for the policy assignment identity. The immediate omission risk in this case is: Forgotten keys could expire or remain compromised without detection. C:Vault network access is a separate security boundary from access to keys and secrets. The immediate omission risk in this case is: Forgotten keys could expire or remain compromised without detection. D:Agentless scanning and runtime security sensors offer different evidence and coverage. The immediate omission risk in this case is: Forgotten keys could expire or remain compromised without detection.
Question 342An AKS workload uses a service account with cluster-admin privilege for simple read-only inventory. Which change best addresses this retired Azure security topic? Require narrow source-port access for the shortest authorized just-in-time window Apply Kubernetes RBAC granting only namespace-scoped read permissions to that service account Enable Azure Bastion or approved JIT access and remove persistent public RDP exposure Apply access restrictions and encryption to the audit and export destinations ExplanationCorrect Answer B:The relevant technical principle is: Kubernetes identities can be restricted by resource verb and namespace to enforce least privilege. The appropriate correction is to apply Kubernetes RBAC granting only namespace-scoped read permissions to that service account. Verify it by checking that an inventory read succeeds but an attempted deployment deletion is denied. Incorrect Answers A:Defender for Cloud JIT reduces standing management-port exposure through temporary rules. The operative distinction here is: Kubernetes identities can be restricted by resource verb and namespace to enforce least privilege. The targeted change is: Apply Kubernetes RBAC granting only namespace-scoped read permissions to that service account. C:Private or time-bound administrative access reduces exposure to credential attacks. The operative distinction here is: Kubernetes identities can be restricted by resource verb and namespace to enforce least privilege. The targeted change is: Apply Kubernetes RBAC granting only namespace-scoped read permissions to that service account. D:Audit logging and data protection of extracted query results are separate requirements. The operative distinction here is: Kubernetes identities can be restricted by resource verb and namespace to enforce least privilege. The targeted change is: Apply Kubernetes RBAC granting only namespace-scoped read permissions to that service account.
Question 343A service publishes one exposed public IP but its DDoS plan covers only application-layer HTTP. Which change best addresses this retired Azure security topic? Set the minimum supported TLS version on the application endpoint and test legacy-client rejection Require explicit subscription visibility and reviewed private endpoint connection approval Assess Azure DDoS Protection for network-layer risks at relevant VNet public endpoints Rotate the listener certificate using controlled Key Vault integration or approved certificate deployment ExplanationCorrect Answer C:The relevant technical principle is: Volumetric and protocol-level denial-of-service require controls beyond a web WAF. The appropriate correction is to assess Azure DDoS Protection for network-layer risks at relevant VNet public endpoints. Verify it by checking that DDoS telemetry and controlled response plans show protected public IP exposure. Incorrect Answers A:Transport-layer security configuration must enforce protocol strength at each public termination point. The operative distinction here is: Volumetric and protocol-level denial-of-service require controls beyond a web WAF. The targeted change is: Assess Azure DDoS Protection for network-layer risks at relevant VNet public endpoints. B:Private Link service connection approval governs which private endpoint consumers reach a provider. The operative distinction here is: Volumetric and protocol-level denial-of-service require controls beyond a web WAF. The targeted change is: Assess Azure DDoS Protection for network-layer risks at relevant VNet public endpoints. D:TLS listener availability depends on valid configured server certificates and renewed trust. The operative distinction here is: Volumetric and protocol-level denial-of-service require controls beyond a web WAF. The targeted change is: Assess Azure DDoS Protection for network-layer risks at relevant VNet public endpoints.
Question 344A managed identity is deleted and recreated while the engineering team assumes its old object ID still authorizes access. An engineer proposes to update target RBAC assignments for the new principal identity after recreation. Which technical principle most strongly supports that proposal? Federated and managed workload credentials avoid persistent secret exposure in deployment definitions Moving ownership boundaries requires deliberate review of scope and authorization inheritance A managed identity receives tokens for resource access but still needs explicit target authorization Identity recreation changes principal identifiers and does not preserve all prior permissions automatically ExplanationCorrect Answer D:The technical principle is: Identity recreation changes principal identifiers and does not preserve all prior permissions automatically. It supports the proposed action to update target RBAC assignments for the new principal identity after recreation. Confirmation evidence: the new identity can access only intended services after explicit assignment validation. Incorrect Answers A:Federated and managed workload credentials avoid persistent secret exposure in deployment definitions. For the current requirement, the decisive mechanism is: Identity recreation changes principal identifiers and does not preserve all prior permissions automatically. The related action is: Update target RBAC assignments for the new principal identity after recreation. B:Moving ownership boundaries requires deliberate review of scope and authorization inheritance. For the current requirement, the decisive mechanism is: Identity recreation changes principal identifiers and does not preserve all prior permissions automatically. The related action is: Update target RBAC assignments for the new principal identity after recreation. C:A managed identity receives tokens for resource access but still needs explicit target authorization. For the current requirement, the decisive mechanism is: Identity recreation changes principal identifiers and does not preserve all prior permissions automatically. The related action is: Update target RBAC assignments for the new principal identity after recreation.
Question 345A web application requests delegated Graph access but the developer confuses user-delegated and app-only permissions. After the team acts to choose delegated scopes for actions on behalf of signed-in users and validate consent boundaries, which observation best demonstrates that the repair worked? Issued tokens contain the expected delegated scope rather than unexpected app role grants Enterprise application permission review shows only required reporting grants and resource scope The Reader can see resource properties but a data query still requires database authorization Expected tenant users authenticate and unrelated tenants fail per the approved product design ExplanationCorrect Answer A:The expected result is that issued tokens contain the expected delegated scope rather than unexpected app role grants. This confirms the applicable principle: Delegated permissions act within a user's context while application permissions allow autonomous app access. Incorrect Answers B: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: Issued tokens contain the expected delegated scope rather than unexpected app role grants. C:Azure resource visibility permissions do not automatically grant access to the contents of a database. This is not the decisive validation for the stated requirement. The relevant evidence is: Issued tokens contain the expected delegated scope rather than unexpected app role grants. D:Application sign-in audience settings determine which Microsoft Entra tenants may issue tokens. This is not the decisive validation for the stated requirement. The relevant evidence is: Issued tokens contain the expected delegated scope rather than unexpected app role grants.
Question 346A web application requests delegated Graph access but the developer confuses user-delegated and app-only permissions. If this issue remains uncorrected, which outcome is the most direct avoidable risk? Unreviewed audience expansion might expose authentication entry points to unintended organizations Excess application permission could give unattended access to tenant-wide data One compromised secret could provide access to several unrelated business workloads Confusing control-plane roles with data rights could produce unsafe permission workarounds ExplanationCorrect Answer B:The principal risk is that excess application permission could give unattended access to tenant-wide data. The preventative response is to choose delegated scopes for actions on behalf of signed-in users and validate consent boundaries. This matters because delegated permissions act within a user's context while application permissions allow autonomous app access. Incorrect Answers A:Application sign-in audience settings determine which Microsoft Entra tenants may issue tokens. The immediate omission risk in this case is: Excess application permission could give unattended access to tenant-wide data. C:Separate principal identity enables granular access revocation and incident attribution. The immediate omission risk in this case is: Excess application permission could give unattended access to tenant-wide data. D:Azure resource visibility permissions do not automatically grant access to the contents of a database. The immediate omission risk in this case is: Excess application permission could give unattended access to tenant-wide data.
Question 347A Sentinel playbook closes any incident labeled malware automatically without preserving evidence. Which change best addresses this retired Azure security topic? Grant the supported assessment access and verify scans complete without broad persistent VM access Use governed workflow automation with scoped identity and a reviewed response playbook Require controlled human review or supported safe automation and documented close criteria Review alert entity context and perform authorized evidence-led triage before containment ExplanationCorrect Answer C:The relevant technical principle is: Automated incident response must respect evidence integrity and approval boundaries. The appropriate correction is to require controlled human review or supported safe automation and documented close criteria. Verify it by checking that A suspicious test incident remains available for investigation while approved benign closures are recorded. Incorrect Answers A:Agentless VM scanning relies on an authorized snapshot-based assessment workflow. The operative distinction here is: Automated incident response must respect evidence integrity and approval boundaries. The targeted change is: Require controlled human review or supported safe automation and documented close criteria. B:Cloud alert automation needs least-privilege execution and accountable response boundaries. The operative distinction here is: Automated incident response must respect evidence integrity and approval boundaries. The targeted change is: Require controlled human review or supported safe automation and documented close criteria. D:Security alerts are investigation signals and response action should reflect validated risk. The operative distinction here is: Automated incident response must respect evidence integrity and approval boundaries. The targeted change is: Require controlled human review or supported safe automation and documented close criteria.
Question 348An Azure SQL Managed Instance is placed in a delegated subnet without correct required routing dependencies. An engineer proposes to apply supported MI subnet routing and security configuration without opening broad internet access. Which technical principle most strongly supports that proposal? API Management inbound policies can enforce tokens and other access controls before backend invocation Service Endpoints extend subnet identity to service firewall rules while Private Endpoints provide a private IP interface Private endpoint connectivity depends on consistent service DNS resolution and reachable VNet links SQL Managed Instance networking requires specific delegated subnet and service-management connectivity ExplanationCorrect Answer D:The technical principle is: SQL Managed Instance networking requires specific delegated subnet and service-management connectivity. It supports the proposed action to apply supported MI subnet routing and security configuration without opening broad internet access. Confirmation evidence: instance provisioning and application private connections succeed under documented rules. Incorrect Answers A:API Management inbound policies can enforce tokens and other access controls before backend invocation. For the current requirement, the decisive mechanism is: SQL Managed Instance networking requires specific delegated subnet and service-management connectivity. The related action is: Apply supported MI subnet routing and security configuration without opening broad internet access. B:Service Endpoints extend subnet identity to service firewall rules while Private Endpoints provide a private IP interface. For the current requirement, the decisive mechanism is: SQL Managed Instance networking requires specific delegated subnet and service-management connectivity. The related action is: Apply supported MI subnet routing and security configuration without opening broad internet access. C:Private endpoint connectivity depends on consistent service DNS resolution and reachable VNet links. For the current requirement, the decisive mechanism is: SQL Managed Instance networking requires specific delegated subnet and service-management connectivity. The related action is: Apply supported MI subnet routing and security configuration without opening broad internet access.
Question 349A development VM's JIT request automatically opens broad inbound access for an entire week. Which change best addresses this retired Azure security topic? Require narrow source-port access for the shortest authorized just-in-time window Configure approved private cluster API access and restricted administration paths Enable Azure Bastion or approved JIT access and remove persistent public RDP exposure Enable Azure SQL auditing to an authorized protected destination and validate captured events ExplanationCorrect Answer A:The relevant technical principle is: Defender for Cloud JIT reduces standing management-port exposure through temporary rules. The appropriate correction is to require narrow source-port access for the shortest authorized just-in-time window. Verify it by checking that the rule expires after the approved period and later unrelated probes are blocked. Incorrect Answers B:AKS control-plane exposure should match the documented management-network threat model. The operative distinction here is: Defender for Cloud JIT reduces standing management-port exposure through temporary rules. The targeted change is: Require narrow source-port access for the shortest authorized just-in-time window. C:Private or time-bound administrative access reduces exposure to credential attacks. The operative distinction here is: Defender for Cloud JIT reduces standing management-port exposure through temporary rules. The targeted change is: Require narrow source-port access for the shortest authorized just-in-time window. D:Database auditing should preserve evidence of sensitive operations and accountable principal activity. The operative distinction here is: Defender for Cloud JIT reduces standing management-port exposure through temporary rules. The targeted change is: Require narrow source-port access for the shortest authorized just-in-time window.
Question 350A Sentinel playbook closes any incident labeled malware automatically without preserving evidence. After the team acts to require controlled human review or supported safe automation and documented close criteria, which observation best demonstrates that the repair worked? Expected test network telemetry reaches the intended workspace with current timestamps A suspicious test incident remains available for investigation while approved benign closures are recorded A new authorized test sign-in appears in the correct log table after remediation Scan records show completed current findings and minimal necessary access permissions ExplanationCorrect Answer B:The expected result is that A suspicious test incident remains available for investigation while approved benign closures are recorded. This confirms the applicable principle: Automated incident response must respect evidence integrity and approval boundaries. 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 suspicious test incident remains available for investigation while approved benign closures are recorded. 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 suspicious test incident remains available for investigation while approved benign closures are recorded. D:Agentless VM scanning relies on an authorized snapshot-based assessment workflow. This is not the decisive validation for the stated requirement. The relevant evidence is: A suspicious test incident remains available for investigation while approved benign closures are recorded.