Question 260An AKS cluster exposes its Kubernetes API server publicly despite a mandatory private management baseline. After the team acts to configure approved private cluster API access and restricted administration paths, which observation best demonstrates that the repair worked? An inventory read succeeds but an attempted deployment deletion is denied The deployment pipeline accepts a known approved image and rejects an unsigned test image A controlled schema change appears in the retained audit log with actor and timestamp Authorized administrators reach the private API while public endpoint probes fail ExplanationCorrect Answer D:The expected result is that authorized administrators reach the private API while public endpoint probes fail. This confirms the applicable principle: AKS control-plane exposure should match the documented management-network threat model. 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: Authorized administrators reach the private API while public endpoint probes fail. B:Container supply-chain integrity depends on trusted build and registry provenance. This is not the decisive validation for the stated requirement. The relevant evidence is: Authorized administrators reach the private API while public endpoint probes fail. C:Database auditing should preserve evidence of sensitive operations and accountable principal activity. This is not the decisive validation for the stated requirement. The relevant evidence is: Authorized administrators reach the private API while public endpoint probes fail.
Question 261An application publisher rotates certificates but leaves an expired credential configured as the only active signing material. Which change best addresses this retired Azure security topic? Roll the credential using supported overlap and validate service principal authentication before expiry Remove role-assignment write capability and test the effective permissions independently Choose delegated scopes for actions on behalf of signed-in users and validate consent boundaries Replace the embedded secret with workload federation or managed identity where supported ExplanationCorrect Answer A:The relevant technical principle is: Application credential rotation needs a controlled overlap and effective authentication test. The appropriate correction is to roll the credential using supported overlap and validate service principal authentication before expiry. Verify it by checking that the new certificate authenticates and the expired credential is removed without service disruption. Incorrect Answers B:Permission to grant authorization can create privilege escalation even without direct resource writes. The operative distinction here is: Application credential rotation needs a controlled overlap and effective authentication test. The targeted change is: Roll the credential using supported overlap and validate service principal authentication before expiry. C:Delegated permissions act within a user's context while application permissions allow autonomous app access. The operative distinction here is: Application credential rotation needs a controlled overlap and effective authentication test. The targeted change is: Roll the credential using supported overlap and validate service principal authentication before expiry. D:Federated and managed workload credentials avoid persistent secret exposure in deployment definitions. The operative distinction here is: Application credential rotation needs a controlled overlap and effective authentication test. The targeted change is: Roll the credential using supported overlap and validate service principal authentication before expiry.
Question 262A storage account permits access from all public networks despite being assigned to a regulated workload subnet. If this issue remains uncorrected, which outcome is the most direct avoidable risk? Teams may broadly disclose storage keys to compensate for misunderstood authentication A stolen data-plane credential could be used from untrusted networks One mistaken deletion may irreversibly remove production data Public RDP access may enable password attacks or exploitation of management services ExplanationCorrect Answer B:The principal risk is that A stolen data-plane credential could be used from untrusted networks. The preventative response is to restrict its network access and verify required service endpoints or private endpoints. This matters because storage firewall settings are independent from Azure resource management role assignments. Incorrect Answers A:Azure Files supports distinct SMB and REST access patterns with different identity requirements. The immediate omission risk in this case is: A stolen data-plane credential could be used from untrusted networks. C:Object recovery mechanisms must be configured in advance of accidental deletion events. The immediate omission risk in this case is: A stolen data-plane credential could be used from untrusted networks. D:Private or time-bound administrative access reduces exposure to credential attacks. The immediate omission risk in this case is: A stolen data-plane credential could be used from untrusted networks.
Question 263An NSG exception permanently allows a vendor's entire geographic IP range for a one-day migration. Which change best addresses this retired Azure security topic? Rotate the listener certificate using controlled Key Vault integration or approved certificate deployment Implement destination-specific outbound rules and validate required service exceptions Replace it with a narrow source-and-port rule and expire the exception after approval window Apply scoped NSG inbound rules permitting only the documented required application ports ExplanationCorrect Answer C:The relevant technical principle is: Time-bound network exceptions should be scoped to demonstrated source and service need. The appropriate correction is to replace it with a narrow source-and-port rule and expire the exception after approval window. Verify it by checking that A post-window test confirms the vendor flow is blocked and exception closure is recorded. Incorrect Answers A:TLS listener availability depends on valid configured server certificates and renewed trust. The operative distinction here is: Time-bound network exceptions should be scoped to demonstrated source and service need. The targeted change is: Replace it with a narrow source-and-port rule and expire the exception after approval window. B:Outbound NSG filtering can restrict workloads from communicating with unapproved networks. The operative distinction here is: Time-bound network exceptions should be scoped to demonstrated source and service need. The targeted change is: Replace it with a narrow source-and-port rule and expire the exception after approval window. D:Network Security Groups filter traffic by rule priority direction protocol source destination and port. The operative distinction here is: Time-bound network exceptions should be scoped to demonstrated source and service need. The targeted change is: Replace it with a narrow source-and-port rule and expire the exception after approval window.
Question 264A security engineer enables Key Vault RBAC authorization but expects old access policies to continue granting data permissions. An engineer proposes to assign the intended Key Vault data-plane Azure RBAC roles after choosing the permission model. Which technical principle most strongly supports that proposal? Azure Policy effects apply through their assignment scope and inherited governance hierarchy Azure Policy audit detects conditions whereas deny and modify can enforce or change deployments Hybrid posture assessment depends on correctly connected and reporting assets Vault access-policy and Azure RBAC authorization modes are distinct ExplanationCorrect Answer D:The technical principle is: Vault access-policy and Azure RBAC authorization modes are distinct. It supports the proposed action to assign the intended Key Vault data-plane Azure RBAC roles after choosing the permission model. Confirmation evidence: the intended principal accesses the required secret under RBAC and old unneeded grants no longer apply. Incorrect Answers A:Azure Policy effects apply through their assignment scope and inherited governance hierarchy. For the current requirement, the decisive mechanism is: Vault access-policy and Azure RBAC authorization modes are distinct. The related action is: Assign the intended Key Vault data-plane Azure RBAC roles after choosing the permission model. B:Azure Policy audit detects conditions whereas deny and modify can enforce or change deployments. For the current requirement, the decisive mechanism is: Vault access-policy and Azure RBAC authorization modes are distinct. The related action is: Assign the intended Key Vault data-plane Azure RBAC roles after choosing the permission model. C:Hybrid posture assessment depends on correctly connected and reporting assets. For the current requirement, the decisive mechanism is: Vault access-policy and Azure RBAC authorization modes are distinct. The related action is: Assign the intended Key Vault data-plane Azure RBAC roles after choosing the permission model.
Question 265A VM triggers repeated suspicious PowerShell alerts but analysts suppress the entire alert type across subscriptions. After the team acts to triage a bounded sample and tune narrow supported exclusions only with evidence, which observation best demonstrates that the repair worked? Documented benign commands are handled without hiding a controlled malicious test The target account displays the intended protection status and safe test telemetry routes correctly The remediation task updates only target tags and reports success against sampled resources A protected SQL instance reports plan status and relevant security alerts reach the queue ExplanationCorrect Answer A:The expected result is that documented benign commands are handled without hiding a controlled malicious test. This confirms the applicable principle: Broad threat-alert suppression can conceal genuine attacks that resemble benign administration. Incorrect Answers B: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: Documented benign commands are handled without hiding a controlled malicious test. C:Policy modification and remediation require authorization for the policy assignment identity. This is not the decisive validation for the stated requirement. The relevant evidence is: Documented benign commands are handled without hiding a controlled malicious test. D: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: Documented benign commands are handled without hiding a controlled malicious test.
Question 266A developer applies built-in Contributor at subscription level because a pipeline must update one storage account. Which change best addresses this retired Azure security topic? Replace subscription-wide Owner with the narrow VM operator role at the resource group Assign a narrow custom deployment role scoped to the intended resource rather than the subscription Edit the custom role to permit only validated cost-reading operations and inspect assignable scopes Restrict consent to necessary API scopes and examine the application's enterprise permissions ExplanationCorrect Answer B:The relevant technical principle is: Scoped deployment identities can manage their target resource without all subscription-write permissions. The appropriate correction is to assign a narrow custom deployment role scoped to the intended resource rather than the subscription. Verify it by checking that pipeline execution succeeds for the storage update but cannot deploy an unrelated public VM. Incorrect Answers A:Azure role-based access control should grant the fewest management actions at the smallest workable scope. The operative distinction here is: Scoped deployment identities can manage their target resource without all subscription-write permissions. The targeted change is: Assign a narrow custom deployment role scoped to the intended resource rather than the subscription. C:Custom role action lists determine permissible management-plane operations and must not include unrelated privileges. The operative distinction here is: Scoped deployment identities can manage their target resource without all subscription-write permissions. The targeted change is: Assign a narrow custom deployment role scoped to the intended resource rather than the subscription. D:Admin consent may authorize high-impact access far beyond a user's immediate reporting need. The operative distinction here is: Scoped deployment identities can manage their target resource without all subscription-write permissions. The targeted change is: Assign a narrow custom deployment role scoped to the intended resource rather than the subscription.
Question 267A VM security team relies entirely on manual patch lists and has no integrated vulnerability findings. After the team acts to enable supported Defender Vulnerability Management assessment and assign remediation owners, which observation best demonstrates that the repair worked? The report identifies the controlling definition assignment scope and noncompliant VM property The target account displays the intended protection status and safe test telemetry routes correctly The VM assessment identifies known vulnerable components and closes after validated remediation A protected SQL instance reports plan status and relevant security alerts reach the queue ExplanationCorrect Answer C:The expected result is that the VM assessment identifies known vulnerable components and closes after validated remediation. This confirms the applicable principle: Vulnerability management requires current scan findings and actionable asset prioritization. Incorrect Answers A:An initiative aggregates policy definitions while compliance results can be traced to specific assignments. This is not the decisive validation for the stated requirement. The relevant evidence is: The VM assessment identifies known vulnerable components and closes after validated remediation. B: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 VM assessment identifies known vulnerable components and closes after validated remediation. D: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 VM assessment identifies known vulnerable components and closes after validated remediation.
Question 268A staging account's access keys are never rotated because applications reference their values directly. If this issue remains uncorrected, which outcome is the most direct avoidable risk? DBAs or service components could read sensitive plaintext beyond business need Teams may broadly disclose storage keys to compensate for misunderstood authentication A stolen data-plane credential could be used from untrusted networks Leaked old keys could remain usable indefinitely ExplanationCorrect Answer D:The principal risk is that leaked old keys could remain usable indefinitely. The preventative response is to introduce a controlled key rotation plan using alternating keys and application validation. This matters because storage access key rotation requires preserving service continuity while invalidating old credentials. Incorrect Answers A:Always Encrypted can keep protected values encrypted in the database engine and at rest. The immediate omission risk in this case is: Leaked old keys could remain usable indefinitely. B:Azure Files supports distinct SMB and REST access patterns with different identity requirements. The immediate omission risk in this case is: Leaked old keys could remain usable indefinitely. C:Storage firewall settings are independent from Azure resource management role assignments. The immediate omission risk in this case is: Leaked old keys could remain usable indefinitely.
Question 269An NSG exception permanently allows a vendor's entire geographic IP range for a one-day migration. An engineer proposes to replace it with a narrow source-and-port rule and expire the exception after approval window. Which technical principle most strongly supports that proposal? Time-bound network exceptions should be scoped to demonstrated source and service need TLS listener availability depends on valid configured server certificates and renewed trust Outbound NSG filtering can restrict workloads from communicating with unapproved networks Application Security Groups let rules refer to virtual machine groupings instead of brittle IP lists ExplanationCorrect Answer A:The technical principle is: Time-bound network exceptions should be scoped to demonstrated source and service need. It supports the proposed action to replace it with a narrow source-and-port rule and expire the exception after approval window. Confirmation evidence: A post-window test confirms the vendor flow is blocked and exception closure is recorded. Incorrect Answers B:TLS listener availability depends on valid configured server certificates and renewed trust. For the current requirement, the decisive mechanism is: Time-bound network exceptions should be scoped to demonstrated source and service need. The related action is: Replace it with a narrow source-and-port rule and expire the exception after approval window. C:Outbound NSG filtering can restrict workloads from communicating with unapproved networks. For the current requirement, the decisive mechanism is: Time-bound network exceptions should be scoped to demonstrated source and service need. The related action is: Replace it with a narrow source-and-port rule and expire the exception after approval window. D:Application Security Groups let rules refer to virtual machine groupings instead of brittle IP lists. For the current requirement, the decisive mechanism is: Time-bound network exceptions should be scoped to demonstrated source and service need. The related action is: Replace it with a narrow source-and-port rule and expire the exception after approval window.
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.