Question 170A production automation script shares the same service principal credential with several independent applications. After the team acts to create distinct scoped workload identities and rotate the shared secret out of circulation, which observation best demonstrates that the repair worked? The function retrieves the intended secret while a different identity remains denied Revoking one compromised credential leaves other applications operational with independent identities Enterprise application permission review shows only required reporting grants and resource scope Role activation records show approvals expiration and timely deactivation of vendor privileges ExplanationCorrect Answer B:The expected result is that revoking one compromised credential leaves other applications operational with independent identities. This confirms the applicable principle: Separate principal identity enables granular access revocation and incident attribution. Incorrect Answers A: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: Revoking one compromised credential leaves other applications operational with independent identities. C: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: Revoking one compromised credential leaves other applications operational with independent identities. D:Just-in-time privileged access reduces standing exposure while retaining auditable emergency elevation. This is not the decisive validation for the stated requirement. The relevant evidence is: Revoking one compromised credential leaves other applications operational with independent identities.
Question 171An Application Gateway backend probe uses the wrong host name and reports healthy servers as offline. If this issue remains uncorrected, which outcome is the most direct avoidable risk? Compromised servers could communicate with attacker-controlled endpoints unhindered Attackers could evade gateway inspection and WAF protections Incorrect health probes could cause unnecessary regional failover Policy drift could leave a regional network with weaker protections ExplanationCorrect Answer C:The principal risk is that incorrect health probes could cause unnecessary regional failover. The preventative response is to set the appropriate probe host and path and verify backend health behavior. This matters because layer-7 health probes depend on the host header and URL expected by the service. Incorrect Answers A:Outbound NSG filtering can restrict workloads from communicating with unapproved networks. The immediate omission risk in this case is: Incorrect health probes could cause unnecessary regional failover. B:Layer-7 gateway security is ineffective when the original service stays directly accessible. The immediate omission risk in this case is: Incorrect health probes could cause unnecessary regional failover. D:Central firewall policies can provide consistent baseline rules across multiple protected hubs. The immediate omission risk in this case is: Incorrect health probes could cause unnecessary regional failover.
Question 172A multinational extends Defender for Cloud to AWS but assigns no permission for discovering protected compute inventory. An engineer proposes to configure the supported multicloud connector permissions and confirm expected resource discovery. Which technical principle most strongly supports that proposal? Threat-intelligence indicators are contextual signals and can become stale or incorrectly attributed Hybrid posture assessment depends on correctly connected and reporting assets Regulatory dashboards aggregate control assessments but human governance must resolve deviations Multicloud posture coverage depends on connector authorization and service integration ExplanationCorrect Answer D:The technical principle is: Multicloud posture coverage depends on connector authorization and service integration. It supports the proposed action to configure the supported multicloud connector permissions and confirm expected resource discovery. Confirmation evidence: the expected AWS accounts and resources appear with recent assessment data. Incorrect Answers A:Threat-intelligence indicators are contextual signals and can become stale or incorrectly attributed. For the current requirement, the decisive mechanism is: Multicloud posture coverage depends on connector authorization and service integration. The related action is: Configure the supported multicloud connector permissions and confirm expected resource discovery. B:Hybrid posture assessment depends on correctly connected and reporting assets. For the current requirement, the decisive mechanism is: Multicloud posture coverage depends on connector authorization and service integration. The related action is: Configure the supported multicloud connector permissions and confirm expected resource discovery. C:Regulatory dashboards aggregate control assessments but human governance must resolve deviations. For the current requirement, the decisive mechanism is: Multicloud posture coverage depends on connector authorization and service integration. The related action is: Configure the supported multicloud connector permissions and confirm expected resource discovery.
Question 173An Azure Arc server remains listed as onboarded but has not uploaded assessment data since a network change. An engineer proposes to investigate connector health and telemetry freshness before trusting the inventory status. Which technical principle most strongly supports that proposal? Asset presence is not equivalent to current posture visibility Hybrid posture assessment depends on correctly connected and reporting assets Regulatory dashboards aggregate control assessments but human governance must resolve deviations Version-specific references do not automatically track new Key Vault secret versions ExplanationCorrect Answer A:The technical principle is: Asset presence is not equivalent to current posture visibility. It supports the proposed action to investigate connector health and telemetry freshness before trusting the inventory status. Confirmation evidence: the server reports recent data and an intentionally triggered safe finding appears in assessment. Incorrect Answers B:Hybrid posture assessment depends on correctly connected and reporting assets. For the current requirement, the decisive mechanism is: Asset presence is not equivalent to current posture visibility. The related action is: Investigate connector health and telemetry freshness before trusting the inventory status. C:Regulatory dashboards aggregate control assessments but human governance must resolve deviations. For the current requirement, the decisive mechanism is: Asset presence is not equivalent to current posture visibility. The related action is: Investigate connector health and telemetry freshness before trusting the inventory status. D:Version-specific references do not automatically track new Key Vault secret versions. For the current requirement, the decisive mechanism is: Asset presence is not equivalent to current posture visibility. The related action is: Investigate connector health and telemetry freshness before trusting the inventory status.
Question 174A regulated database exports audit logs to a shared workspace where ordinary developers can delete them. After the team acts to move audit evidence to a retention-controlled destination with separate access grants, which observation best demonstrates that the repair worked? Unprivileged queries show masked identifiers while approved authorized roles can perform required checks Developers can inspect permitted activity but cannot modify the retained audit records Database settings report encryption enabled and restoration tests preserve encrypted backups An inventory read succeeds but an attempted deployment deletion is denied ExplanationCorrect Answer B:The expected result is that developers can inspect permitted activity but cannot modify the retained audit records. This confirms the applicable principle: Security audit evidence requires protected custody and restricted deletion rights. Incorrect Answers A: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: Developers can inspect permitted activity but cannot modify the retained audit records. C:Transparent Data Encryption protects SQL database files and backups at rest. This is not the decisive validation for the stated requirement. The relevant evidence is: Developers can inspect permitted activity but cannot modify the retained audit records. D: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: Developers can inspect permitted activity but cannot modify the retained audit records.
Question 175A contractor's Microsoft Entra guest account remains active after the vendor engagement ended. After the team acts to disable or remove the guest and revoke relevant sessions while validating access-review closure, which observation best demonstrates that the repair worked? A supervised emergency test succeeds while sign-in alerts and credential custody remain enforced Role activation records show approvals expiration and timely deactivation of vendor privileges The user fails a new sign-in and the sponsor review records removal of the stale guest Issued tokens contain the expected delegated scope rather than unexpected app role grants ExplanationCorrect Answer C:The expected result is that the user fails a new sign-in and the sponsor review records removal of the stale guest. This confirms the applicable principle: External identity lifecycle controls must revoke access when the legitimate sponsorship ends. Incorrect Answers A: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: The user fails a new sign-in and the sponsor review records removal of the stale guest. B:Just-in-time privileged access reduces standing exposure while retaining auditable emergency elevation. This is not the decisive validation for the stated requirement. The relevant evidence is: The user fails a new sign-in and the sponsor review records removal of the stale guest. D:Delegated permissions act within a user's context while application permissions allow autonomous app access. This is not the decisive validation for the stated requirement. The relevant evidence is: The user fails a new sign-in and the sponsor review records removal of the stale guest.
Question 176A platform team enables infrastructure encryption but assumes it replaces required customer-managed key controls. Which change best addresses this retired Azure security topic? Apply workload admission restrictions to prohibit unjustified privileged container settings Disable anonymous blob access and require approved token-based authorization Replace account-wide shared keys with an appropriate short-lived delegated access mechanism Validate independent infrastructure encryption and customer-managed key requirements ExplanationCorrect Answer D:The relevant technical principle is: Infrastructure-level double encryption and customer-managed keys address different encryption controls. The appropriate correction is to validate independent infrastructure encryption and customer-managed key requirements. Verify it by checking that both encryption settings show expected values and recoverability is tested. Incorrect Answers A:Privileged pods and host mounts can cross the isolation boundary between containers and nodes. The operative distinction here is: Infrastructure-level double encryption and customer-managed keys address different encryption controls. The targeted change is: Validate independent infrastructure encryption and customer-managed key requirements. B:Blob public-access configuration can expose data independently of a user's Azure management role. The operative distinction here is: Infrastructure-level double encryption and customer-managed keys address different encryption controls. The targeted change is: Validate independent infrastructure encryption and customer-managed key requirements. C:Storage account keys grant broad service authority and must never be embedded in untrusted clients. The operative distinction here is: Infrastructure-level double encryption and customer-managed keys address different encryption controls. The targeted change is: Validate independent infrastructure encryption and customer-managed key requirements.
Question 177A high-severity recommendation in Defender for Cloud is dismissed because one VM was decommissioned even though other assets remain affected. After the team acts to verify all affected resources and close only findings with corroborated remediation, which observation best demonstrates that the repair worked? The recommendation shows correct remaining affected assets and supporting remediation evidence Notification arrives ahead of expiry and the renewed certificate is deployed to the intended listener Each failed control has a reviewed affected-resource list an owner and closure evidence Control mapping identifies assessed evidence and separately tracked manual requirements ExplanationCorrect Answer A:The expected result is that the recommendation shows correct remaining affected assets and supporting remediation evidence. This confirms the applicable principle: A posture recommendation may apply to multiple resources and needs per-resource validation. Incorrect Answers B:Certificate management needs proactive renewal and validation of dependent services. This is not the decisive validation for the stated requirement. The relevant evidence is: The recommendation shows correct remaining affected assets and supporting remediation evidence. C: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 recommendation shows correct remaining affected assets and supporting remediation evidence. D: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 recommendation shows correct remaining affected assets and supporting remediation evidence.
Question 178A cloud security design uses a service tag as though it identifies one fixed vendor IP address across all Azure regions. Which change best addresses this retired Azure security topic? Implement destination-specific outbound rules and validate required service exceptions Review service tag semantics and use approved scoped service definitions where possible Validate the supported ASE network dependencies and narrowly permit required service traffic Apply scoped NSG inbound rules permitting only the documented required application ports ExplanationCorrect Answer B:The relevant technical principle is: Service tags represent provider-maintained address groups rather than immutable individual endpoints. The appropriate correction is to review service tag semantics and use approved scoped service definitions where possible. Verify it by checking that effective rules allow the intended Azure service traffic without admitting arbitrary external destinations. Incorrect Answers A:Outbound NSG filtering can restrict workloads from communicating with unapproved networks. The operative distinction here is: Service tags represent provider-maintained address groups rather than immutable individual endpoints. The targeted change is: Review service tag semantics and use approved scoped service definitions where possible. C:Isolated App Service environments still require documented platform management and health dependencies. The operative distinction here is: Service tags represent provider-maintained address groups rather than immutable individual endpoints. The targeted change is: Review service tag semantics and use approved scoped service definitions where possible. D:Network Security Groups filter traffic by rule priority direction protocol source destination and port. The operative distinction here is: Service tags represent provider-maintained address groups rather than immutable individual endpoints. The targeted change is: Review service tag semantics and use approved scoped service definitions where possible.
Question 179A branch virtual network sends internet-bound traffic directly despite an approved central inspection appliance. After the team acts to associate the correct route table and next hop for the routed subnet, which observation best demonstrates that the repair worked? A new instance inherits authorized traffic outcomes without creating a new IP-specific allow rule DNS resolves the intended private address from the workload and public attempts are rejected Effective routes show the approved appliance next hop and packet traces confirm traversal Traffic uses the intended inspection path and blocked destinations fail firewall enforcement ExplanationCorrect Answer C:The expected result is that effective routes show the approved appliance next hop and packet traces confirm traversal. This confirms the applicable principle: Subnet route tables can steer flows through an Azure virtual appliance for centralized inspection. Incorrect Answers A:Application Security Groups let rules refer to virtual machine groupings instead of brittle IP lists. This is not the decisive validation for the stated requirement. The relevant evidence is: Effective routes show the approved appliance next hop and packet traces confirm traversal. B:Private Endpoints expose supported platform services through private IPs but public endpoints require separate restriction. This is not the decisive validation for the stated requirement. The relevant evidence is: Effective routes show the approved appliance next hop and packet traces confirm traversal. D:User-defined routes choose next hops but are not equivalent to security-filter rules. This is not the decisive validation for the stated requirement. The relevant evidence is: Effective routes show the approved appliance next hop and packet traces confirm traversal.
Question 180A production automation script shares the same service principal credential with several independent applications. An engineer proposes to create distinct scoped workload identities and rotate the shared secret out of circulation. Which technical principle most strongly supports that proposal? Just-in-time privileged access reduces standing exposure while retaining auditable emergency elevation 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 Separate principal identity enables granular access revocation and incident attribution ExplanationCorrect Answer D:The technical principle is: Separate principal identity enables granular access revocation and incident attribution. It supports the proposed action to create distinct scoped workload identities and rotate the shared secret out of circulation. Confirmation evidence: revoking one compromised credential leaves other applications operational with independent identities. Incorrect Answers A:Just-in-time privileged access reduces standing exposure while retaining auditable emergency elevation. For the current requirement, the decisive mechanism is: Separate principal identity enables granular access revocation and incident attribution. The related action is: Create distinct scoped workload identities and rotate the shared secret out of circulation. B:A managed identity receives tokens for resource access but still needs explicit target authorization. For the current requirement, the decisive mechanism is: Separate principal identity enables granular access revocation and incident attribution. The related action is: Create distinct scoped workload identities and rotate the shared secret out of circulation. C:Federated and managed workload credentials avoid persistent secret exposure in deployment definitions. For the current requirement, the decisive mechanism is: Separate principal identity enables granular access revocation and incident attribution. The related action is: Create distinct scoped workload identities and rotate the shared secret out of circulation.