Question 610
To reduce exposure of the highest-privilege cloud tenant identity, which solution should be adopted?
- Short-lived cloud credentials
- Cloud account separation
- Cloud root-account protection
- Cloud organization policy
- Cloud service account lifecycle
Explanation
Correct Answer
C:Strong MFA, no routine root use and protected recovery channels limit catastrophic account takeover; the requested outcome is precisely to reduce exposure of the highest-privilege cloud tenant identity.
Incorrect Answers
A:Workload identity or assumed roles produce temporary tokens with bounded authority and lifetime; that is useful when the task is to replace static access keys embedded in container images, not the stated requirement to reduce exposure of the highest-privilege cloud tenant identity.
B:Separate projects or accounts provide billing, access and policy boundaries when governance is correctly configured; a team would select it to keep test workloads from sharing production administrative trust, which does not provide the particular result to reduce exposure of the highest-privilege cloud tenant identity.
D:Hierarchical guardrails restrict configurations beyond individual developer IAM grants; applying it would serve prevent member accounts deploying resources outside approved regions without directly satisfying the goal to reduce exposure of the highest-privilege cloud tenant identity.
E:Inventory and deprovisioning prevent abandoned credentials from retaining API access; it addresses the different need to remove unused nonhuman principals after application retirement, leaving the requested ability to reduce exposure of the highest-privilege cloud tenant identity unresolved.
Question 611
A supported cloud application currently accepts an access session long after a high-impact identity event such as account disablement. The team wants the application to re-evaluate active access promptly instead of relying only on the original sign-in check. What capability applies?
- Continuous access evaluation for supported sessions
- Conditional access policy evaluated at sign-in
- A quarterly privileged-role access review
- Cloud organization account separation
- Initial MFA registration
Explanation
Correct Answer
A:Continuous access evaluation allows supported applications to respond to important identity or policy changes and challenge or terminate an active session without always waiting for ordinary token expiry.
Incorrect Answers
B:A sign-in-time conditional access decision evaluates context before granting initial access. By itself it may not promptly respond to account or policy changes during an ongoing session.
C:An access review is a periodic governance check on assignments. It cannot promptly end an already-authorized application session when an account is disabled.
D:Separating cloud accounts reduces administrative and resource blast radius. It does not provide real-time evaluation of a user's established application session.
E:MFA registration improves the available authentication factors for future sign-ins. It is not the session reevaluation mechanism requested after a critical identity event.
Question 612
To prevent member accounts deploying resources outside approved regions, which option is the direct technical match?
- Cloud organization policy
- Cloud identity federation
- Cloud IAM least privilege
- Cloud privilege escalation review
Explanation
Correct Answer
A:Hierarchical guardrails restrict configurations beyond individual developer IAM grants; this mechanism directly supports the requirement to prevent member accounts deploying resources outside approved regions.
Incorrect Answers
B:Federation uses trusted identity assertions and centralized lifecycle controls across providers; it could help someone trying to let enterprise users sign into cloud consoles without storing separate cloud passwords, but the problem is instead to prevent member accounts deploying resources outside approved regions.
C:Identity policies restrict actions and resources instead of handing broad account administrator roles to applications; that is useful when the task is to grant an automation identity only needed object-read permissions, not the stated requirement to prevent member accounts deploying resources outside approved regions.
D:Effective-permission analysis exposes indirect routes to elevated control even when direct grants look narrow; a team would select it to detect a role that can modify its own access policies or impersonate admins, which does not provide the particular result to prevent member accounts deploying resources outside approved regions.
Question 613
To remove unused nonhuman principals after application retirement and to replace static access keys embedded in container images, which TWO measures should the defender select? Choose TWO.
- Cloud service account lifecycle
- Short-lived cloud credentials
- Multi-cloud asset inventory
- Cloud organization policy
- Cloud conditional access
Explanation
Correct Answers
A:Inventory and deprovisioning prevent abandoned credentials from retaining API access; its contribution to the combined design is specifically to remove unused nonhuman principals after application retirement.
B:Workload identity or assumed roles produce temporary tokens with bounded authority and lifetime; its contribution to the combined design is specifically to replace static access keys embedded in container images.
Incorrect Answers
C:Centralized posture visibility links network exposure to accounts, owners and required corrections; it could help someone trying to discover publicly reachable resources across several cloud tenants, but the problem is instead to remove unused nonhuman principals after application retirement and to replace static access keys embedded in container images.
D:Hierarchical guardrails restrict configurations beyond individual developer IAM grants; that is useful when the task is to prevent member accounts deploying resources outside approved regions, not the stated requirement to remove unused nonhuman principals after application retirement and to replace static access keys embedded in container images.
E:Context-aware access policy combines identity with device, location and risk signals where supported; a team would select it to deny privileged access from untrusted device or sign-in conditions, which does not provide the particular result to remove unused nonhuman principals after application retirement and to replace static access keys embedded in container images.
Question 614
To replace static access keys embedded in container images, which method is designed for the task?
- Short-lived cloud credentials
- Multi-cloud asset inventory
- Cloud identity federation
- Cloud conditional access
Explanation
Correct Answer
A:Workload identity or assumed roles produce temporary tokens with bounded authority and lifetime; that is why it addresses the operational task to replace static access keys embedded in container images.
Incorrect Answers
B:Centralized posture visibility links network exposure to accounts, owners and required corrections; the outcome it supports is to discover publicly reachable resources across several cloud tenants, whereas this scenario asks defenders to replace static access keys embedded in container images.
C:Federation uses trusted identity assertions and centralized lifecycle controls across providers; although relevant to let enterprise users sign into cloud consoles without storing separate cloud passwords, it does not by itself achieve the required task to replace static access keys embedded in container images.
D:Context-aware access policy combines identity with device, location and risk signals where supported; it could help someone trying to deny privileged access from untrusted device or sign-in conditions, but the problem is instead to replace static access keys embedded in container images.
Question 615
To detect a role that can modify its own access policies or impersonate admins, what technique should the team use?
- Multi-cloud asset inventory
- Cloud privilege escalation review
- Cloud organization policy
- Short-lived cloud credentials
- Cloud service account lifecycle
Explanation
Correct Answer
B:Effective-permission analysis exposes indirect routes to elevated control even when direct grants look narrow; its relevant protective or investigative effect is to detect a role that can modify its own access policies or impersonate admins.
Incorrect Answers
A:Centralized posture visibility links network exposure to accounts, owners and required corrections; the technique works for situations involving discover publicly reachable resources across several cloud tenants, rather than this need to detect a role that can modify its own access policies or impersonate admins.
C:Hierarchical guardrails restrict configurations beyond individual developer IAM grants; the outcome it supports is to prevent member accounts deploying resources outside approved regions, whereas this scenario asks defenders to detect a role that can modify its own access policies or impersonate admins.
D:Workload identity or assumed roles produce temporary tokens with bounded authority and lifetime; although relevant to replace static access keys embedded in container images, it does not by itself achieve the required task to detect a role that can modify its own access policies or impersonate admins.
E:Inventory and deprovisioning prevent abandoned credentials from retaining API access; it could help someone trying to remove unused nonhuman principals after application retirement, but the problem is instead to detect a role that can modify its own access policies or impersonate admins.
Question 616
To discover publicly reachable resources across several cloud tenants, what technique should the team use?
- Cloud privilege escalation review
- Cloud organization policy
- Cloud conditional access
- Multi-cloud asset inventory
Explanation
Correct Answer
D:Centralized posture visibility links network exposure to accounts, owners and required corrections; the requested outcome is precisely to discover publicly reachable resources across several cloud tenants.
Incorrect Answers
A:Effective-permission analysis exposes indirect routes to elevated control even when direct grants look narrow; it addresses the different need to detect a role that can modify its own access policies or impersonate admins, leaving the requested ability to discover publicly reachable resources across several cloud tenants unresolved.
B:Hierarchical guardrails restrict configurations beyond individual developer IAM grants; the technique works for situations involving prevent member accounts deploying resources outside approved regions, rather than this need to discover publicly reachable resources across several cloud tenants.
C:Context-aware access policy combines identity with device, location and risk signals where supported; its mechanism supports deny privileged access from untrusted device or sign-in conditions, while the requested control must be able to discover publicly reachable resources across several cloud tenants.
Question 617
To restrict inbound server traffic to approved source ranges and ports, which protective or investigative measure applies?
- Private endpoint connectivity
- Cloud network ACL
- Cloud security group
- Public IP exposure review
Explanation
Correct Answer
C:Stateful virtual network filtering controls instance flows, with exact attachment and precedence defined by provider; this choice fits the scenario because the team must restrict inbound server traffic to approved source ranges and ports.
Incorrect Answers
A:Private network attachment limits exposure but still requires identity authentication and DNS correctness; applying it would serve reach a managed database without using its public internet address without directly satisfying the goal to restrict inbound server traffic to approved source ranges and ports.
B:Stateless or ordered subnet policies require explicit direction and ephemeral-port considerations depending on provider; it addresses the different need to apply subnet-bound packet filtering separate from instance-level rules, leaving the requested ability to restrict inbound server traffic to approved source ranges and ports unresolved.
D:Inventory of addresses, routes and firewall rules identifies the actual reachable path; its mechanism supports find an internet-accessible cloud VM unintentionally created by a project team, while the requested control must be able to restrict inbound server traffic to approved source ranges and ports.
Question 618
To apply subnet-bound packet filtering separate from instance-level rules, what is the most direct option?
- Cloud network ACL
- Public IP exposure review
- Cloud route table assessment
- Private endpoint connectivity
Explanation
Correct Answer
A:Stateless or ordered subnet policies require explicit direction and ephemeral-port considerations depending on provider; this mechanism directly supports the requirement to apply subnet-bound packet filtering separate from instance-level rules.
Incorrect Answers
B:Inventory of addresses, routes and firewall rules identifies the actual reachable path; applying it would serve find an internet-accessible cloud VM unintentionally created by a project team without directly satisfying the goal to apply subnet-bound packet filtering separate from instance-level rules.
C:Route evaluation exposes unintended egress or connectivity paths despite security-group intentions; it addresses the different need to explain why a supposedly private subnet sends default traffic through an internet gateway, leaving the requested ability to apply subnet-bound packet filtering separate from instance-level rules unresolved.
D:Private network attachment limits exposure but still requires identity authentication and DNS correctness; the technique works for situations involving reach a managed database without using its public internet address, rather than this need to apply subnet-bound packet filtering separate from instance-level rules.
Question 619
To reach a managed database without using its public internet address, what should defenders select?
- Cloud route table assessment
- Private endpoint connectivity
- Cloud security group
- Public IP exposure review
Explanation
Correct Answer
B:Private network attachment limits exposure but still requires identity authentication and DNS correctness; it supplies the specific control needed to reach a managed database without using its public internet address.
Incorrect Answers
A:Route evaluation exposes unintended egress or connectivity paths despite security-group intentions; a team would select it to explain why a supposedly private subnet sends default traffic through an internet gateway, which does not provide the particular result to reach a managed database without using its public internet address.
C:Stateful virtual network filtering controls instance flows, with exact attachment and precedence defined by provider; applying it would serve restrict inbound server traffic to approved source ranges and ports without directly satisfying the goal to reach a managed database without using its public internet address.
D:Inventory of addresses, routes and firewall rules identifies the actual reachable path; it addresses the different need to find an internet-accessible cloud VM unintentionally created by a project team, leaving the requested ability to reach a managed database without using its public internet address unresolved.
Question 620
To find an internet-accessible cloud VM unintentionally created by a project team, which mechanism best fits?
- Public IP exposure review
- Cloud security group
- Private endpoint connectivity
- NAT gateway egress
- Cloud network ACL
Explanation
Correct Answer
A:Inventory of addresses, routes and firewall rules identifies the actual reachable path; that is why it addresses the operational task to find an internet-accessible cloud VM unintentionally created by a project team.
Incorrect Answers
B:Stateful virtual network filtering controls instance flows, with exact attachment and precedence defined by provider; a team would select it to restrict inbound server traffic to approved source ranges and ports, which does not provide the particular result to find an internet-accessible cloud VM unintentionally created by a project team.
C:Private network attachment limits exposure but still requires identity authentication and DNS correctness; its operational purpose is to reach a managed database without using its public internet address, not to achieve the specific requirement to find an internet-accessible cloud VM unintentionally created by a project team.
D:Managed translation supports outbound sessions but is not equivalent to content inspection; applying it would serve allow private subnet workloads to initiate outbound internet connections without direct inbound addresses without directly satisfying the goal to find an internet-accessible cloud VM unintentionally created by a project team.
E:Stateless or ordered subnet policies require explicit direction and ephemeral-port considerations depending on provider; it addresses the different need to apply subnet-bound packet filtering separate from instance-level rules, leaving the requested ability to find an internet-accessible cloud VM unintentionally created by a project team unresolved.