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.
Question 631
To limit who may use a cloud-held data-encryption key, which control achieves the target outcome?
- Azure Network Security Group
- Microsoft Entra Conditional Access
- AWS KMS key policy
- Azure Key Vault
Explanation
Correct Answer
C:KMS authorization combines key policy and applicable identity permissions with cryptographic operation controls; it supplies the specific control needed to limit who may use a cloud-held data-encryption key.
Incorrect Answers
A:NSG rules evaluate priorities, service tags and port ranges for network-level access control; it could help someone trying to filter inbound and outbound traffic on Azure network interfaces or subnets, but the problem is instead to limit who may use a cloud-held data-encryption key.
B: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 limit who may use a cloud-held data-encryption key.
D:Access controls and auditing protect secret retrieval independent of source-code repositories; its operational purpose is to securely store and govern application cryptographic keys and secrets, not to achieve the specific requirement to limit who may use a cloud-held data-encryption key.
Question 632
To prevent accidental public exposure through bucket or object permissions, which solution should be adopted?
- Google Cloud VPC firewall rules
- Azure Network Security Group
- AWS S3 Block Public Access
- AWS IAM Access Analyzer
Explanation
Correct Answer
C:Account or bucket-level guardrails reject public-access configurations within their defined coverage; that is why it addresses the operational task to prevent accidental public exposure through bucket or object permissions.
Incorrect Answers
A:Cloud firewall rules evaluate direction, targets and priorities within the applicable network policy; although relevant to restrict VM networking by target and traffic attributes in GCP, it does not by itself achieve the required task to prevent accidental public exposure through bucket or object permissions.
B:NSG rules evaluate priorities, service tags and port ranges for network-level access control; it could help someone trying to filter inbound and outbound traffic on Azure network interfaces or subnets, but the problem is instead to prevent accidental public exposure through bucket or object permissions.
D:Policy analysis evaluates cross-account trust and public sharing paths for supported resources; a team would select it to find resource policies granting unexpected external principal access, which does not provide the particular result to prevent accidental public exposure through bucket or object permissions.
Question 633
To restrict SaaS and Azure sign-ins using identity and device signals, which of the available controls is suitable?
- Microsoft Entra Conditional Access
- Google Cloud VPC firewall rules
- AWS S3 Block Public Access
- AWS IAM Access Analyzer
Explanation
Correct Answer
A:Entra policies evaluate sign-in context for supported applications before issuing access decisions; its relevant protective or investigative effect is to restrict SaaS and Azure sign-ins using identity and device signals.
Incorrect Answers
B:Cloud firewall rules evaluate direction, targets and priorities within the applicable network policy; although relevant to restrict VM networking by target and traffic attributes in GCP, it does not by itself achieve the required task to restrict SaaS and Azure sign-ins using identity and device signals.
C:Account or bucket-level guardrails reject public-access configurations within their defined coverage; it could help someone trying to prevent accidental public exposure through bucket or object permissions, but the problem is instead to restrict SaaS and Azure sign-ins using identity and device signals.
D:Policy analysis evaluates cross-account trust and public sharing paths for supported resources; that is useful when the task is to find resource policies granting unexpected external principal access, not the stated requirement to restrict SaaS and Azure sign-ins using identity and device signals.
Question 634
To filter inbound and outbound traffic on Azure network interfaces or subnets, which option is the direct technical match?
- AWS S3 Block Public Access
- Azure Network Security Group
- Azure Activity Log
- Google Cloud Audit Logs
Explanation
Correct Answer
B:NSG rules evaluate priorities, service tags and port ranges for network-level access control; the requested outcome is precisely to filter inbound and outbound traffic on Azure network interfaces or subnets.
Incorrect Answers
A:Account or bucket-level guardrails reject public-access configurations within their defined coverage; its mechanism supports prevent accidental public exposure through bucket or object permissions, while the requested control must be able to filter inbound and outbound traffic on Azure network interfaces or subnets.
C:Control-plane audit records reveal Azure resource actions rather than full packet-level payloads; although relevant to review subscription management operations such as resource deletion, it does not by itself achieve the required task to filter inbound and outbound traffic on Azure network interfaces or subnets.
D:Audit streams support investigation of configuration changes and data access where enabled and available; it could help someone trying to trace administrator and service API activity in GCP projects, but the problem is instead to filter inbound and outbound traffic on Azure network interfaces or subnets.
Question 635
To securely store and govern application cryptographic keys and secrets, which approach should a cloud security architect choose?
- Azure Key Vault
- Azure Network Security Group
- AWS S3 Block Public Access
- Azure Activity Log
- Google Cloud VPC firewall rules
Explanation
Correct Answer
A:Access controls and auditing protect secret retrieval independent of source-code repositories; this choice fits the scenario because the team must securely store and govern application cryptographic keys and secrets.
Incorrect Answers
B:NSG rules evaluate priorities, service tags and port ranges for network-level access control; its mechanism supports filter inbound and outbound traffic on Azure network interfaces or subnets, while the requested control must be able to securely store and govern application cryptographic keys and secrets.
C:Account or bucket-level guardrails reject public-access configurations within their defined coverage; the outcome it supports is to prevent accidental public exposure through bucket or object permissions, whereas this scenario asks defenders to securely store and govern application cryptographic keys and secrets.
D:Control-plane audit records reveal Azure resource actions rather than full packet-level payloads; although relevant to review subscription management operations such as resource deletion, it does not by itself achieve the required task to securely store and govern application cryptographic keys and secrets.
E:Cloud firewall rules evaluate direction, targets and priorities within the applicable network policy; it could help someone trying to restrict VM networking by target and traffic attributes in GCP, but the problem is instead to securely store and govern application cryptographic keys and secrets.
Question 636
To review subscription management operations such as resource deletion, which method is designed for the task?
- Azure Network Security Group
- Microsoft Entra Conditional Access
- Azure Activity Log
- Google Cloud Audit Logs
Explanation
Correct Answer
C:Control-plane audit records reveal Azure resource actions rather than full packet-level payloads; this mechanism directly supports the requirement to review subscription management operations such as resource deletion.
Incorrect Answers
A: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 review subscription management operations such as resource deletion unresolved.
B:Entra policies evaluate sign-in context for supported applications before issuing access decisions; the technique works for situations involving restrict SaaS and Azure sign-ins using identity and device signals, rather than this need to review subscription management operations such as resource deletion.
D:Audit streams support investigation of configuration changes and data access where enabled and available; the outcome it supports is to trace administrator and service API activity in GCP projects, whereas this scenario asks defenders to review subscription management operations such as resource deletion.
Question 637
To restrict VM networking by target and traffic attributes in GCP and to trace administrator and service API activity in GCP projects, which TWO measures should the defender select? Choose TWO.
- Google Cloud Audit Logs
- Google Cloud VPC firewall rules
- Azure Activity Log
- Azure Key Vault
- AWS S3 Block Public Access
Explanation
Correct Answers
A:Audit streams support investigation of configuration changes and data access where enabled and available; its contribution to the combined design is specifically to trace administrator and service API activity in GCP projects.
B:Cloud firewall rules evaluate direction, targets and priorities within the applicable network policy; its contribution to the combined design is specifically to restrict VM networking by target and traffic attributes in GCP.
Incorrect Answers
C:Control-plane audit records reveal Azure resource actions rather than full packet-level payloads; the technique works for situations involving review subscription management operations such as resource deletion, rather than this need to restrict VM networking by target and traffic attributes in GCP and to trace administrator and service API activity in GCP projects.
D:Access controls and auditing protect secret retrieval independent of source-code repositories; its mechanism supports securely store and govern application cryptographic keys and secrets, while the requested control must be able to restrict VM networking by target and traffic attributes in GCP and to trace administrator and service API activity in GCP projects.
E:Account or bucket-level guardrails reject public-access configurations within their defined coverage; the outcome it supports is to prevent accidental public exposure through bucket or object permissions, whereas this scenario asks defenders to restrict VM networking by target and traffic attributes in GCP and to trace administrator and service API activity in GCP projects.
Question 638
To trace administrator and service API activity in GCP projects, what technique should the team use?
- Azure Activity Log
- Google Cloud Audit Logs
- Google Cloud VPC firewall rules
- Azure Key Vault
Explanation
Correct Answer
B:Audit streams support investigation of configuration changes and data access where enabled and available; that is why it addresses the operational task to trace administrator and service API activity in GCP projects.
Incorrect Answers
A:Control-plane audit records reveal Azure resource actions rather than full packet-level payloads; its operational purpose is to review subscription management operations such as resource deletion, not to achieve the specific requirement to trace administrator and service API activity in GCP projects.
C:Cloud firewall rules evaluate direction, targets and priorities within the applicable network policy; it addresses the different need to restrict VM networking by target and traffic attributes in GCP, leaving the requested ability to trace administrator and service API activity in GCP projects unresolved.
D:Access controls and auditing protect secret retrieval independent of source-code repositories; the technique works for situations involving securely store and govern application cryptographic keys and secrets, rather than this need to trace administrator and service API activity in GCP projects.
Question 639
To detect misconfigured public storage and permissive IAM across subscriptions, which protective or investigative measure applies?
- Cloud security posture management
- Cloud workload protection
- Cloud storage object immutability
- Cloud infrastructure as code review
Explanation
Correct Answer
A:CSPM evaluates cloud resource state against secure configuration and compliance rules; its relevant protective or investigative effect is to detect misconfigured public storage and permissive IAM across subscriptions.
Incorrect Answers
B:CWPP sensors focus on execution and vulnerability exposure rather than only control-plane settings; its operational purpose is to monitor host and container runtime behavior inside virtual compute workloads, not to achieve the specific requirement to detect misconfigured public storage and permissive IAM across subscriptions.
C:Retention locks protect copies against destructive changes under approved governance modes; applying it would serve prevent backup objects being deleted before a defined recovery window without directly satisfying the goal to detect misconfigured public storage and permissive IAM across subscriptions.
D:Static policy checks and pull-request controls catch risky definitions before provisioning; it addresses the different need to stop a permissive firewall rule from entering production via a template, leaving the requested ability to detect misconfigured public storage and permissive IAM across subscriptions unresolved.
Question 640
To monitor host and container runtime behavior inside virtual compute workloads, what is the most direct option?
- Cloud secret rotation
- Cloud security posture management
- Cloud database encryption at rest
- Cloud storage object immutability
- Cloud workload protection
Explanation
Correct Answer
E:CWPP sensors focus on execution and vulnerability exposure rather than only control-plane settings; the requested outcome is precisely to monitor host and container runtime behavior inside virtual compute workloads.
Incorrect Answers
A:Replacing the credential and all consumers closes continued use of the leaked value; that is useful when the task is to limit exposure after a workload password appears in build logs, not the stated requirement to monitor host and container runtime behavior inside virtual compute workloads.
B:CSPM evaluates cloud resource state against secure configuration and compliance rules; a team would select it to detect misconfigured public storage and permissive IAM across subscriptions, which does not provide the particular result to monitor host and container runtime behavior inside virtual compute workloads.
C:Provider or customer-managed keys support storage confidentiality while query access remains separately authorized; its operational purpose is to protect managed database storage against offline media disclosure, not to achieve the specific requirement to monitor host and container runtime behavior inside virtual compute workloads.
D:Retention locks protect copies against destructive changes under approved governance modes; applying it would serve prevent backup objects being deleted before a defined recovery window without directly satisfying the goal to monitor host and container runtime behavior inside virtual compute workloads.