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.
Question 621
To explain why a supposedly private subnet sends default traffic through an internet gateway, which measure best meets the requirement?
- Cloud web application firewall
- Public IP exposure review
- Private endpoint connectivity
- Cloud route table assessment
Explanation
Correct Answer
D:Route evaluation exposes unintended egress or connectivity paths despite security-group intentions; its relevant protective or investigative effect is to explain why a supposedly private subnet sends default traffic through an internet gateway.
Incorrect Answers
A:Managed web-layer rules can filter recognized attacks before they reach application servers; it could help someone trying to inspect HTTP requests sent to exposed cloud front ends, but the problem is instead to explain why a supposedly private subnet sends default traffic through an internet gateway.
B:Inventory of addresses, routes and firewall rules identifies the actual reachable path; that is useful when the task is to find an internet-accessible cloud VM unintentionally created by a project team, not the stated requirement to explain why a supposedly private subnet sends default traffic through an internet gateway.
C:Private network attachment limits exposure but still requires identity authentication and DNS correctness; a team would select it to reach a managed database without using its public internet address, which does not provide the particular result to explain why a supposedly private subnet sends default traffic through an internet gateway.
Question 622
To allow private subnet workloads to initiate outbound internet connections without direct inbound addresses, what control should be selected?
- Cloud load-balancer TLS
- Cloud web application firewall
- Private endpoint connectivity
- NAT gateway egress
Explanation
Correct Answer
D:Managed translation supports outbound sessions but is not equivalent to content inspection; the requested outcome is precisely to allow private subnet workloads to initiate outbound internet connections without direct inbound addresses.
Incorrect Answers
A:The listener protects the external connection while upstream encryption must be configured separately if required; although relevant to terminate client HTTPS on a managed entry point with trusted certificates, it does not by itself achieve the required task to allow private subnet workloads to initiate outbound internet connections without direct inbound addresses.
B:Managed web-layer rules can filter recognized attacks before they reach application servers; it could help someone trying to inspect HTTP requests sent to exposed cloud front ends, but the problem is instead to allow private subnet workloads to initiate outbound internet connections without direct inbound addresses.
C:Private network attachment limits exposure but still requires identity authentication and DNS correctness; that is useful when the task is to reach a managed database without using its public internet address, not the stated requirement to allow private subnet workloads to initiate outbound internet connections without direct inbound addresses.
Question 623
To terminate client HTTPS on a managed entry point with trusted certificates, which security control is most appropriate?
- Cloud route table assessment
- Cloud network ACL
- Cloud DNS split-horizon
- Cloud load-balancer TLS
Explanation
Correct Answer
D:The listener protects the external connection while upstream encryption must be configured separately if required; this choice fits the scenario because the team must terminate client HTTPS on a managed entry point with trusted certificates.
Incorrect Answers
A:Route evaluation exposes unintended egress or connectivity paths despite security-group intentions; the outcome it supports is to explain why a supposedly private subnet sends default traffic through an internet gateway, whereas this scenario asks defenders to terminate client HTTPS on a managed entry point with trusted certificates.
B:Stateless or ordered subnet policies require explicit direction and ephemeral-port considerations depending on provider; although relevant to apply subnet-bound packet filtering separate from instance-level rules, it does not by itself achieve the required task to terminate client HTTPS on a managed entry point with trusted certificates.
C:Separate DNS views align name resolution with distinct trust and routing contexts; it could help someone trying to return private service addresses for internal workloads and public records externally, but the problem is instead to terminate client HTTPS on a managed entry point with trusted certificates.
Question 624
A cloud website routes users through a security edge that inspects requests, but an attacker has discovered the publicly reachable origin load balancer and can bypass the edge. Which control most directly closes that inspection bypass?
- Enable HTTPS between users and the origin
- Require authenticated edge-to-origin access and deny direct origin traffic
- Update cloud web application firewall signatures
- Enable public DNS resolution for the origin host
Explanation
Correct Answer
B:Enforcing edge-to-origin authentication and restricting origin ingress ensures that requests cannot normally reach the backend without traversing the approved security edge. This closes the direct-origin bypass path.
Incorrect Answers
A:HTTPS encrypts the transport to the origin, which is important for confidentiality in transit. Encryption does not force requests through the inspection edge when the public origin still accepts arbitrary client connections.
C:WAF signatures help recognize malicious request patterns at the inspection point. They cannot inspect attacks that go directly to an origin address and never pass through that inspection point.
D:Advertising the origin through public DNS can make direct bypass easier to discover and use. DNS publication does not add an authentication or ingress enforcement boundary protecting backend traffic.
Question 625
To protect internet-facing cloud endpoints from high-volume denial-of-service traffic and to return private service addresses for internal workloads and public records externally, which TWO measures should the defender select? Choose TWO.
- Cloud route table assessment
- Cloud DNS split-horizon
- Cloud web application firewall
- Hybrid VPN connection
- Cloud DDoS protection
Explanation
Correct Answers
B:Separate DNS views align name resolution with distinct trust and routing contexts; its contribution to the combined design is specifically to return private service addresses for internal workloads and public records externally.
E:Provider-scale absorption mitigates floods at network and application layers according to service coverage; its contribution to the combined design is specifically to protect internet-facing cloud endpoints from high-volume denial-of-service traffic.
Incorrect Answers
A:Route evaluation exposes unintended egress or connectivity paths despite security-group intentions; the technique works for situations involving explain why a supposedly private subnet sends default traffic through an internet gateway, rather than this need to protect internet-facing cloud endpoints from high-volume denial-of-service traffic and to return private service addresses for internal workloads and public records externally.
C:Managed web-layer rules can filter recognized attacks before they reach application servers; the outcome it supports is to inspect HTTP requests sent to exposed cloud front ends, whereas this scenario asks defenders to protect internet-facing cloud endpoints from high-volume denial-of-service traffic and to return private service addresses for internal workloads and public records externally.
D:IPsec tunnels provide protected transport over shared networks while route policy limits reachable segments; although relevant to encrypt routing between an office gateway and a cloud virtual network, it does not by itself achieve the required task to protect internet-facing cloud endpoints from high-volume denial-of-service traffic and to return private service addresses for internal workloads and public records externally.
Question 626
To return private service addresses for internal workloads and public records externally, which tool, policy, or technique is appropriate?
- Cloud DNS split-horizon
- Cloud web application firewall
- Cloud DDoS protection
- Hybrid VPN connection
Explanation
Correct Answer
A:Separate DNS views align name resolution with distinct trust and routing contexts; that is why it addresses the operational task to return private service addresses for internal workloads and public records externally.
Incorrect Answers
B:Managed web-layer rules can filter recognized attacks before they reach application servers; the technique works for situations involving inspect HTTP requests sent to exposed cloud front ends, rather than this need to return private service addresses for internal workloads and public records externally.
C:Provider-scale absorption mitigates floods at network and application layers according to service coverage; its mechanism supports protect internet-facing cloud endpoints from high-volume denial-of-service traffic, while the requested control must be able to return private service addresses for internal workloads and public records externally.
D:IPsec tunnels provide protected transport over shared networks while route policy limits reachable segments; the outcome it supports is to encrypt routing between an office gateway and a cloud virtual network, whereas this scenario asks defenders to return private service addresses for internal workloads and public records externally.
Question 627
To encrypt routing between an office gateway and a cloud virtual network, which tool, policy, or technique is appropriate?
- Hybrid VPN connection
- Cloud web application firewall
- Cloud load-balancer TLS
- Cloud DDoS protection
- Cloud DNS split-horizon
- NAT gateway egress
Explanation
Correct Answer
A:IPsec tunnels provide protected transport over shared networks while route policy limits reachable segments; its relevant protective or investigative effect is to encrypt routing between an office gateway and a cloud virtual network.
Incorrect Answers
B:Managed web-layer rules can filter recognized attacks before they reach application servers; it addresses the different need to inspect HTTP requests sent to exposed cloud front ends, leaving the requested ability to encrypt routing between an office gateway and a cloud virtual network unresolved.
C:The listener protects the external connection while upstream encryption must be configured separately if required; the technique works for situations involving terminate client HTTPS on a managed entry point with trusted certificates, rather than this need to encrypt routing between an office gateway and a cloud virtual network.
D:Provider-scale absorption mitigates floods at network and application layers according to service coverage; its mechanism supports protect internet-facing cloud endpoints from high-volume denial-of-service traffic, while the requested control must be able to encrypt routing between an office gateway and a cloud virtual network.
E:Separate DNS views align name resolution with distinct trust and routing contexts; the outcome it supports is to return private service addresses for internal workloads and public records externally, whereas this scenario asks defenders to encrypt routing between an office gateway and a cloud virtual network.
F:Managed translation supports outbound sessions but is not equivalent to content inspection; although relevant to allow private subnet workloads to initiate outbound internet connections without direct inbound addresses, it does not by itself achieve the required task to encrypt routing between an office gateway and a cloud virtual network.
Question 628
To audit changes made through AWS control-plane API calls, what safeguard would be most applicable?
- AWS CloudTrail
- AWS IAM Access Analyzer
- AWS VPC Flow Logs
- AWS S3 Block Public Access
Explanation
Correct Answer
A:CloudTrail records management events and can capture supported data events when enabled and retained; the requested outcome is precisely to audit changes made through AWS control-plane API calls.
Incorrect Answers
B:Policy analysis evaluates cross-account trust and public sharing paths for supported resources; applying it would serve find resource policies granting unexpected external principal access without directly satisfying the goal to audit changes made through AWS control-plane API calls.
C:Flow logs summarize traffic metadata rather than storing full application payloads; it addresses the different need to identify IP flows accepted or rejected at cloud network interfaces, leaving the requested ability to audit changes made through AWS control-plane API calls unresolved.
D:Account or bucket-level guardrails reject public-access configurations within their defined coverage; the technique works for situations involving prevent accidental public exposure through bucket or object permissions, rather than this need to audit changes made through AWS control-plane API calls.
Question 629
To identify IP flows accepted or rejected at cloud network interfaces, what is the relevant defensive action?
- Microsoft Entra Conditional Access
- AWS CloudTrail
- AWS S3 Block Public Access
- AWS VPC Flow Logs
Explanation
Correct Answer
D:Flow logs summarize traffic metadata rather than storing full application payloads; this choice fits the scenario because the team must identify IP flows accepted or rejected at cloud network interfaces.
Incorrect Answers
A:Entra policies evaluate sign-in context for supported applications before issuing access decisions; a team would select it to restrict SaaS and Azure sign-ins using identity and device signals, which does not provide the particular result to identify IP flows accepted or rejected at cloud network interfaces.
B:CloudTrail records management events and can capture supported data events when enabled and retained; its operational purpose is to audit changes made through AWS control-plane API calls, not to achieve the specific requirement to identify IP flows accepted or rejected at cloud network interfaces.
C:Account or bucket-level guardrails reject public-access configurations within their defined coverage; applying it would serve prevent accidental public exposure through bucket or object permissions without directly satisfying the goal to identify IP flows accepted or rejected at cloud network interfaces.
Question 630
To find resource policies granting unexpected external principal access, which option most directly provides the capability?
- Microsoft Entra Conditional Access
- AWS VPC Flow Logs
- AWS S3 Block Public Access
- AWS IAM Access Analyzer
- Azure Network Security Group
Explanation
Correct Answer
D:Policy analysis evaluates cross-account trust and public sharing paths for supported resources; this mechanism directly supports the requirement to find resource policies granting unexpected external principal access.
Incorrect Answers
A:Entra policies evaluate sign-in context for supported applications before issuing access decisions; that is useful when the task is to restrict SaaS and Azure sign-ins using identity and device signals, not the stated requirement to find resource policies granting unexpected external principal access.
B:Flow logs summarize traffic metadata rather than storing full application payloads; a team would select it to identify IP flows accepted or rejected at cloud network interfaces, which does not provide the particular result to find resource policies granting unexpected external principal access.
C:Account or bucket-level guardrails reject public-access configurations within their defined coverage; its operational purpose is to prevent accidental public exposure through bucket or object permissions, not to achieve the specific requirement to find resource policies granting unexpected external principal access.
E:NSG rules evaluate priorities, service tags and port ranges for network-level access control; it addresses the different need to filter inbound and outbound traffic on Azure network interfaces or subnets, leaving the requested ability to find resource policies granting unexpected external principal access unresolved.