問題一覧
1
Use customer-managed encryption keys to delete specific encryption keys.
2
Create an aggregate org sink at the parent folder of the production projects, and set the destination to a logs bucket.
3
1. Create or use an existing key with a unique uniform resource identifier (URI) in a supported external key management partner system. 2. In the external key management partner system, grant access for this key to use your Google Cloud project.
4
Cloud NAT
5
Configure uniform bucket-level access, and enforce domain restricted sharing in an organization policy.
6
Install Google Cloud Directory Sync and connect it to Active Directory and Cloud Identity., Create Identity and Access Management (IAM) roles with permissions corresponding to each Active Directory group.
7
Use a physical token to secure the super admin credentials with multi-factor authentication (MFA)., Provide non-privileged identities to the super admin users for their day-to-day activities.
8
Create a Cloud Storage bucket to store your logs in the EUROPE-WEST1 region. Modify your application code to ship logs directly to your bucket for increased efficiency.
9
Cloud Key Management Service, Cloud Data Loss Prevention with deterministic encryption using AES-SIV
10
Customer-supplied encryption keys. , Cloud External Key Manager
11
Customer-managed encryption keys
12
IAP-Secured Web App User
13
All VM instances are missing the respective network tags. , VPC firewall rule is allowing traffic between source/targets based on the same service account with priority 999.
14
Enable the constraints/compute.skipDefaultNetworkCreation organization policy constraint at the organization level.
15
Use SSO/SAML integration with Cloud Identity for user authentication and user lifecycle management., Provide granular access with predefined roles.
16
Use Packet Mirroring to mirror traffic to and from particular VM instances. Perform inspection using security software that analyzes the mirrored traffic.
17
All load balancer types are denied in accordance with the global node's policy.
18
Enable VPC Service Controls, create a perimeter around Projects A and B, and include the Cloud Storage API in the Service Perimeter configuration.
19
Set up a Shared VPC where the security team manages the firewall rules, and share the network with developers via service projects.
20
Use the transfer tool for unmanaged user accounts.
21
Grant users the compute.imageUser role in the OS image project. , Set up an image access organization policy constraint, and list the security team managed project in the project's allow list.
22
Create a custom IAM role with limited list/view permissions, and assign it to the DevOps team.
23
Customer-managed encryption keys with Cloud HSM
24
Packet Mirroring
25
Confidential Computing and Istio, Client-side encryption
26
Enable the constraints/storage.publicAccessPrevention constraint at the organization level.
27
Configure packet mirroring policies.
28
Format-preserving encryption
29
Use restricted googleapis.com to access Google APIs using a set of IP addresses only routable from within Google Cloud, which are advertised as routes over the Cloud Interconnect connection.
30
1. Generate Supply Chain Levels for Software Artifacts (SLSA) level 3 assurance by using Cloud Build. 2. View the build provenance in the Security insights side panel within the Google Cloud console.
31
Ensure that VM Manager is installed and running on the VMs. In the OS patch management service, configure the patch jobs to update with critical patches dally.
32
Ensure the OS Config agent is installed on all VMs and extract the patch status dashboard every six months.
33
Use date shifting with the context set to the unique ID of the test subject.
34
Use service perimeter and create an access level based on the authorized source IP address as the condition.
35
Implement an organization policy to enforce that boot disks can only be created from images that come from the trusted image project.
36
1. Update the perimeter. 2. Configure the egressTo field to include the external Google Cloud project number as an allowed resource and the serviceName to compute.googleapis.com. 3. Configure the egressFrom field to set identityType to ANY_IDENTITY.
37
Delete the compromised service account.
38
1. Enable vulnerability scanning in the Artifact Registry settings. 2. Use Cloud Build to build the images. 3. Push the images to the Artifact Registry for automatic scanning. 4. View the reports in the Artifact Registry.
39
Configure a throttle action by using Google Cloud Armor to limit the number of requests per client over a specified time interval.
40
1. Create a new SAML profile. 2. Populate the sign-in and sign-out page URLs. 3. Upload the X.509 certificate. 4. Configure Entity ID and ACS URL in your IdP.
41
Implement an Access Policy in BeyondCorp Enterprise to verify the device certificate. Create an access binding with the access policy just created.
42
1. Create two service accounts, one for the infrastructure and one for the application deployment. 2. Use workload identities to let the pods run the two pipelines and authenticate with the service accounts. 3. Run the infrastructure and application pipelines in separate namespaces.
43
Create a Cloud Data loss Prevention (DLP) inspection job that de-identifies PII in files created more than 12 months ago and archives them to another Cloud Storage bucket. Delete the original files.
44
Reconcile accounts that exist in Cloud Identity but not in the third-party IdP. , Use the transfer tool to invite those corporate employees to transfer their unmanaged consumer accounts to the corporate domain.
45
Use Policy Analyzer to query the permissions compute.firewalls.create or compute.firewalls.update or compute.firewalls.delete.
46
Change the encryption type on the bucket to CMEK, and rewrite the objects.
47
Enable Binary Authorization on the existing Cloud Run service., Set the organization policy constraint constraints/run.allowedBinaryAuthorizationPolicies to the list or allowed Binary Authorization policy names.
48
Route all on-premises traffic to Google Cloud through an IPsec VPN tunnel to a VPC with Private Google Access enabled.
49
Data Access audit logs
50
• organization policy: con-straints/gcp.restrictNonCmekServices • binding at: org1 • policy type: deny • policy value: storage.googleapis.com
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 201-244
PCSE 201-244
Mark Joseph Tinawin · 44問 · 1年前PCSE 201-244
PCSE 201-244
44問 • 1年前問題一覧
1
Use customer-managed encryption keys to delete specific encryption keys.
2
Create an aggregate org sink at the parent folder of the production projects, and set the destination to a logs bucket.
3
1. Create or use an existing key with a unique uniform resource identifier (URI) in a supported external key management partner system. 2. In the external key management partner system, grant access for this key to use your Google Cloud project.
4
Cloud NAT
5
Configure uniform bucket-level access, and enforce domain restricted sharing in an organization policy.
6
Install Google Cloud Directory Sync and connect it to Active Directory and Cloud Identity., Create Identity and Access Management (IAM) roles with permissions corresponding to each Active Directory group.
7
Use a physical token to secure the super admin credentials with multi-factor authentication (MFA)., Provide non-privileged identities to the super admin users for their day-to-day activities.
8
Create a Cloud Storage bucket to store your logs in the EUROPE-WEST1 region. Modify your application code to ship logs directly to your bucket for increased efficiency.
9
Cloud Key Management Service, Cloud Data Loss Prevention with deterministic encryption using AES-SIV
10
Customer-supplied encryption keys. , Cloud External Key Manager
11
Customer-managed encryption keys
12
IAP-Secured Web App User
13
All VM instances are missing the respective network tags. , VPC firewall rule is allowing traffic between source/targets based on the same service account with priority 999.
14
Enable the constraints/compute.skipDefaultNetworkCreation organization policy constraint at the organization level.
15
Use SSO/SAML integration with Cloud Identity for user authentication and user lifecycle management., Provide granular access with predefined roles.
16
Use Packet Mirroring to mirror traffic to and from particular VM instances. Perform inspection using security software that analyzes the mirrored traffic.
17
All load balancer types are denied in accordance with the global node's policy.
18
Enable VPC Service Controls, create a perimeter around Projects A and B, and include the Cloud Storage API in the Service Perimeter configuration.
19
Set up a Shared VPC where the security team manages the firewall rules, and share the network with developers via service projects.
20
Use the transfer tool for unmanaged user accounts.
21
Grant users the compute.imageUser role in the OS image project. , Set up an image access organization policy constraint, and list the security team managed project in the project's allow list.
22
Create a custom IAM role with limited list/view permissions, and assign it to the DevOps team.
23
Customer-managed encryption keys with Cloud HSM
24
Packet Mirroring
25
Confidential Computing and Istio, Client-side encryption
26
Enable the constraints/storage.publicAccessPrevention constraint at the organization level.
27
Configure packet mirroring policies.
28
Format-preserving encryption
29
Use restricted googleapis.com to access Google APIs using a set of IP addresses only routable from within Google Cloud, which are advertised as routes over the Cloud Interconnect connection.
30
1. Generate Supply Chain Levels for Software Artifacts (SLSA) level 3 assurance by using Cloud Build. 2. View the build provenance in the Security insights side panel within the Google Cloud console.
31
Ensure that VM Manager is installed and running on the VMs. In the OS patch management service, configure the patch jobs to update with critical patches dally.
32
Ensure the OS Config agent is installed on all VMs and extract the patch status dashboard every six months.
33
Use date shifting with the context set to the unique ID of the test subject.
34
Use service perimeter and create an access level based on the authorized source IP address as the condition.
35
Implement an organization policy to enforce that boot disks can only be created from images that come from the trusted image project.
36
1. Update the perimeter. 2. Configure the egressTo field to include the external Google Cloud project number as an allowed resource and the serviceName to compute.googleapis.com. 3. Configure the egressFrom field to set identityType to ANY_IDENTITY.
37
Delete the compromised service account.
38
1. Enable vulnerability scanning in the Artifact Registry settings. 2. Use Cloud Build to build the images. 3. Push the images to the Artifact Registry for automatic scanning. 4. View the reports in the Artifact Registry.
39
Configure a throttle action by using Google Cloud Armor to limit the number of requests per client over a specified time interval.
40
1. Create a new SAML profile. 2. Populate the sign-in and sign-out page URLs. 3. Upload the X.509 certificate. 4. Configure Entity ID and ACS URL in your IdP.
41
Implement an Access Policy in BeyondCorp Enterprise to verify the device certificate. Create an access binding with the access policy just created.
42
1. Create two service accounts, one for the infrastructure and one for the application deployment. 2. Use workload identities to let the pods run the two pipelines and authenticate with the service accounts. 3. Run the infrastructure and application pipelines in separate namespaces.
43
Create a Cloud Data loss Prevention (DLP) inspection job that de-identifies PII in files created more than 12 months ago and archives them to another Cloud Storage bucket. Delete the original files.
44
Reconcile accounts that exist in Cloud Identity but not in the third-party IdP. , Use the transfer tool to invite those corporate employees to transfer their unmanaged consumer accounts to the corporate domain.
45
Use Policy Analyzer to query the permissions compute.firewalls.create or compute.firewalls.update or compute.firewalls.delete.
46
Change the encryption type on the bucket to CMEK, and rewrite the objects.
47
Enable Binary Authorization on the existing Cloud Run service., Set the organization policy constraint constraints/run.allowedBinaryAuthorizationPolicies to the list or allowed Binary Authorization policy names.
48
Route all on-premises traffic to Google Cloud through an IPsec VPN tunnel to a VPC with Private Google Access enabled.
49
Data Access audit logs
50
• organization policy: con-straints/gcp.restrictNonCmekServices • binding at: org1 • policy type: deny • policy value: storage.googleapis.com