問題一覧
1
1. Create one log sink at the organization level that includes all the child resources. 2. Use as destination a Pub/Sub topic to ingest the logs into the security information and event. management (SIEM) on-premises, and ensure that the right team can access the SIEM. 3. Grant the Viewer role at organization level to the security operations team.
2
Create a hierarchical firewall policy configured at the organization to allow connections only from internal IP ranges.
3
Create a new log bucket in europe-west4, and redirect the _Default bucket to the new bucket.
4
Virtual Machine Threat Detection
5
Use a dedicated project to manage workload identity pools and providers., Use immutable attributes in attribute mappings.
6
Create row-level access policies to restrict the result data when you run queries with the filter expression set to FALSE., Create column-level policy tags to control access to columns at query runtime.
7
Provision a Cloud NAT instance in the same VPC and region as the Compute Engine VM., Enable Private Google Access on the subnet that the Compute Engine VM is deployed within.
8
1. Change the bucket permissions to limit access. 2. Query the bucket's usage logs to report on unauthorized access to the data. 3. Enforce the organization policy storage.publicAccessPrevention to avoid regressions.
9
Configure the trusted image organization policy constraint for the project. , Configure the Binary Authorization policy with respective attestations for the project.
10
Identify all external assets by using Cloud Asset Inventory, and then run a network security scanner against them.
11
Limit the physical location of a new resource with the Organization Policy Service "resource locations constraint.", Limit Google personnel access based on predefined attributes such as their citizenship or geographic location by using Key Access Justifications.
12
Use the transfer tool to migrate unmanaged users.
13
Configure workload identity federation to use GitHub as an identity pool provider.
14
Implement an organization policy that ensures all VM resources created across your organization are Confidential VM instances.
15
Change the configuration of the relevant groups in the Google Workspace Admin console to prevent external users from being added to the group.
16
Activate Security Command Center (SCC) Premium. Create a rule to mute the security findings in SCC so they are not evaluated.
17
Configure Cloud Interconnect and route traffic through an on-premises firewall.
18
Set the session length timeout for Google Cloud services to a shorter duration.
19
Key Access Justifications, Cloud External Key Manager
20
Configure an ingress policy for the perimeter in Project A, and allow access for the service account in Project B to collect messages.
21
A project level, the organizational policy control has been overwritten with an "allow" value.
22
Set up a workload identity pool with your corporate Active Directory Federation Service (ADFS). Configure a rule to let principals in the pool impersonate the Google Cloud service account.
23
Set the reauthentication frequency for the Google Cloud Session Control to one hour.
24
Create a firewall rule to allow access from the Identity-Aware Proxy (IAP) IP range. Grant the role of an IAP-secured Tunnel User to the administrators.
25
1. Identify buckets with record data. 2. Apply a retention policy and set it to retain for seven years. 3. Enable bucket lock.
26
1. Use Google Shielded VM including secure boot, Virtual Trusted Platform Module (vTPM), and integrity monitoring. 2. Activate Confidential Computing. 3. Enforce these actions by using organization policies.
27
Configure Google session control to a shorter duration. , Set a reauthentication policy for Google Cloud services to a shorter duration.
28
Configure Cloud External Key Manager to encrypt the sensitive data before it is uploaded to Cloud Storage, and decrypt the sensitive data after it is downloaded into your VMs. , Create Confidential VMs to access the sensitive data.
29
Use the org policy constraint 'Google Cloud Platform – Resource Location Restriction' on your Google Cloud organization node.
30
Create your secret with a user managed replication policy, and choose only compliant locations.
31
Generate a key in your on-premises environment and store it in a Hardware Security Module (HSM) that is managed on-premises. Use this key as an external key in the Cloud Key Management Service (KMS). Activate Key Access Justifications (KAJ) and set the external key system to reject unauthorized accesses.
32
1. Grant logging.viewer role to the security team at the organization resource level. 2. Grant logging.viewer role to the developer team at the folder resource level that contains all the dev projects.
33
View patch management data in a Security Command Center dashboard. , Deploy patches with VM Manager by using OS patch management.
34
Create curated tables in a separate dataset and assign the role roles/bigquery.dataViewer.
35
The CMEK is in a different region than the Cloud Storage bucket.
36
Deploy Assured Workloads
37
Use Cloud External Key Management (EKM) that integrates with an external Hardware Security Module (HSM) system from supported vendors.
38
Security key
39
1. Leave the network configuration of the VMs in scope unchanged. 2. Enable Cloud NAT for “dev-vpc” and restrict the target range in Cloud NAT to 10.58.5.0/24.
40
Use a subordinate CA in the Google Certificate Authority Service from the on-premises PKI system to issue certificates for the load balancers.
41
1. Create a general service account “g-sa” to orchestrate the batch jobs. 2. Create one service account per batch job “b-sa-[1-5]”, and grant only the permissions required to run the individual batch jobs to the service accounts. 3. Grant the Service Account Token Creator role to g-sa. Use g-sa to obtain short-lived access tokens for b-sa-[1-5] and to execute the batch jobs with the permissions of b-sa-[1-5].
42
The action fails because a constraints/iam.allowedPolicyMemberDomains organization policy is in place and only members from the flowlogistic.com organization are allowed.
43
Configure an HTTP Load Balancing instance that points to the managed group with Identity-Aware Proxy (IAP) protection with Google credentials. Modify the VPC firewall to allow access from IAP network range.
44
Assign a BigQuery Data Viewer role along with an IAM condition that limits the access to specified working hours.
PCSE 1-50
PCSE 1-50
Mark Joseph Tinawin · 50問 · 1年前PCSE 1-50
PCSE 1-50
50問 • 1年前PCSE 51-100
PCSE 51-100
Mark Joseph Tinawin · 50問 · 1年前PCSE 51-100
PCSE 51-100
50問 • 1年前PCSE 101-150
PCSE 101-150
Mark Joseph Tinawin · 50問 · 1年前PCSE 101-150
PCSE 101-150
50問 • 1年前PCSE 151-200
PCSE 151-200
Mark Joseph Tinawin · 50問 · 1年前PCSE 151-200
PCSE 151-200
50問 • 1年前問題一覧
1
1. Create one log sink at the organization level that includes all the child resources. 2. Use as destination a Pub/Sub topic to ingest the logs into the security information and event. management (SIEM) on-premises, and ensure that the right team can access the SIEM. 3. Grant the Viewer role at organization level to the security operations team.
2
Create a hierarchical firewall policy configured at the organization to allow connections only from internal IP ranges.
3
Create a new log bucket in europe-west4, and redirect the _Default bucket to the new bucket.
4
Virtual Machine Threat Detection
5
Use a dedicated project to manage workload identity pools and providers., Use immutable attributes in attribute mappings.
6
Create row-level access policies to restrict the result data when you run queries with the filter expression set to FALSE., Create column-level policy tags to control access to columns at query runtime.
7
Provision a Cloud NAT instance in the same VPC and region as the Compute Engine VM., Enable Private Google Access on the subnet that the Compute Engine VM is deployed within.
8
1. Change the bucket permissions to limit access. 2. Query the bucket's usage logs to report on unauthorized access to the data. 3. Enforce the organization policy storage.publicAccessPrevention to avoid regressions.
9
Configure the trusted image organization policy constraint for the project. , Configure the Binary Authorization policy with respective attestations for the project.
10
Identify all external assets by using Cloud Asset Inventory, and then run a network security scanner against them.
11
Limit the physical location of a new resource with the Organization Policy Service "resource locations constraint.", Limit Google personnel access based on predefined attributes such as their citizenship or geographic location by using Key Access Justifications.
12
Use the transfer tool to migrate unmanaged users.
13
Configure workload identity federation to use GitHub as an identity pool provider.
14
Implement an organization policy that ensures all VM resources created across your organization are Confidential VM instances.
15
Change the configuration of the relevant groups in the Google Workspace Admin console to prevent external users from being added to the group.
16
Activate Security Command Center (SCC) Premium. Create a rule to mute the security findings in SCC so they are not evaluated.
17
Configure Cloud Interconnect and route traffic through an on-premises firewall.
18
Set the session length timeout for Google Cloud services to a shorter duration.
19
Key Access Justifications, Cloud External Key Manager
20
Configure an ingress policy for the perimeter in Project A, and allow access for the service account in Project B to collect messages.
21
A project level, the organizational policy control has been overwritten with an "allow" value.
22
Set up a workload identity pool with your corporate Active Directory Federation Service (ADFS). Configure a rule to let principals in the pool impersonate the Google Cloud service account.
23
Set the reauthentication frequency for the Google Cloud Session Control to one hour.
24
Create a firewall rule to allow access from the Identity-Aware Proxy (IAP) IP range. Grant the role of an IAP-secured Tunnel User to the administrators.
25
1. Identify buckets with record data. 2. Apply a retention policy and set it to retain for seven years. 3. Enable bucket lock.
26
1. Use Google Shielded VM including secure boot, Virtual Trusted Platform Module (vTPM), and integrity monitoring. 2. Activate Confidential Computing. 3. Enforce these actions by using organization policies.
27
Configure Google session control to a shorter duration. , Set a reauthentication policy for Google Cloud services to a shorter duration.
28
Configure Cloud External Key Manager to encrypt the sensitive data before it is uploaded to Cloud Storage, and decrypt the sensitive data after it is downloaded into your VMs. , Create Confidential VMs to access the sensitive data.
29
Use the org policy constraint 'Google Cloud Platform – Resource Location Restriction' on your Google Cloud organization node.
30
Create your secret with a user managed replication policy, and choose only compliant locations.
31
Generate a key in your on-premises environment and store it in a Hardware Security Module (HSM) that is managed on-premises. Use this key as an external key in the Cloud Key Management Service (KMS). Activate Key Access Justifications (KAJ) and set the external key system to reject unauthorized accesses.
32
1. Grant logging.viewer role to the security team at the organization resource level. 2. Grant logging.viewer role to the developer team at the folder resource level that contains all the dev projects.
33
View patch management data in a Security Command Center dashboard. , Deploy patches with VM Manager by using OS patch management.
34
Create curated tables in a separate dataset and assign the role roles/bigquery.dataViewer.
35
The CMEK is in a different region than the Cloud Storage bucket.
36
Deploy Assured Workloads
37
Use Cloud External Key Management (EKM) that integrates with an external Hardware Security Module (HSM) system from supported vendors.
38
Security key
39
1. Leave the network configuration of the VMs in scope unchanged. 2. Enable Cloud NAT for “dev-vpc” and restrict the target range in Cloud NAT to 10.58.5.0/24.
40
Use a subordinate CA in the Google Certificate Authority Service from the on-premises PKI system to issue certificates for the load balancers.
41
1. Create a general service account “g-sa” to orchestrate the batch jobs. 2. Create one service account per batch job “b-sa-[1-5]”, and grant only the permissions required to run the individual batch jobs to the service accounts. 3. Grant the Service Account Token Creator role to g-sa. Use g-sa to obtain short-lived access tokens for b-sa-[1-5] and to execute the batch jobs with the permissions of b-sa-[1-5].
42
The action fails because a constraints/iam.allowedPolicyMemberDomains organization policy is in place and only members from the flowlogistic.com organization are allowed.
43
Configure an HTTP Load Balancing instance that points to the managed group with Identity-Aware Proxy (IAP) protection with Google credentials. Modify the VPC firewall to allow access from IAP network range.
44
Assign a BigQuery Data Viewer role along with an IAM condition that limits the access to specified working hours.