Google Cloud Certified - Professional Cloud Security Engineer 온라인 연습
최종 업데이트 시간: 2025년10월03일
당신은 온라인 연습 문제를 통해 Google Professional Cloud Security Engineer 시험지식에 대해 자신이 어떻게 알고 있는지 파악한 후 시험 참가 신청 여부를 결정할 수 있다.
시험을 100% 합격하고 시험 준비 시간을 35% 절약하기를 바라며 Professional Cloud Security Engineer 덤프 (최신 실제 시험 문제)를 사용 선택하여 현재 최신 50개의 시험 문제와 답을 포함하십시오.
정답:
Explanation:
Objective: Implement an encryption at-rest strategy that balances key management complexity and control for sensitive and non-sensitive data, ensuring FIPS 140-2 L1 compliance.
Solution: Use Google default encryption for non-sensitive data and Cloud Key Management Service (KMS) for sensitive data.
Steps:
Step 1: Store non-sensitive data using Google Cloud’s default encryption, which automatically encrypts data at rest without additional configuration.
Step 2: For sensitive data, use Cloud KMS to create and manage encryption keys.
Step 3: Configure key rotation policies for the keys managed by Cloud KMS to meet compliance requirements.
Step 4: Ensure that all data encryption keys used by Cloud KMS comply with FIPS 140-2 Level 1 standards.
By using Google default encryption for non-sensitive data and Cloud KMS for sensitive data, you can manage encryption efficiently while maintaining control over key residency and rotation for sensitive data.
Reference:
Google Cloud Default Encryption
Cloud Key Management Service
FIPS 140-2 Compliance
정답:
Explanation:
Objective: Store and retrieve sensitive configuration data for an application running on Compute Engine.
Solution: Use Secret Manager to securely store and manage access to sensitive configuration data.
Steps:
Step 1: Open the Google Cloud Console.
Step 2: Navigate to the Secret Manager section.
Step 3: Create a new secret and add the sensitive configuration data.
Step 4: Set appropriate IAM policies to control access to the secret.
Step 5: Update the application to retrieve the secret from Secret Manager using the appropriate client libraries or APIs.
Secret Manager provides a secure and centralized way to manage sensitive information, with fine-grained access control and audit logging capabilities.
Reference:
Secret Manager Documentation
Storing and Accessing Secrets
정답:
Explanation:
Objective: Implement external web application protection and validate policy changes before enforcement.
Solution: Use Google Cloud Armor's preconfigured rules in preview mode.
Steps:
Step 1: Open the Google Cloud Console.
Step 2: Navigate to the Google Cloud Armor section.
Step 3: Create or select a security policy.
Step 4: Apply preconfigured rules to the policy.
Step 5: Enable preview mode to simulate the effects of the rules without enforcing them.
Step 6: Monitor the logs to validate the policy changes.
Google Cloud Armor's preview mode allows you to test and validate the impact of security policies on your application traffic before applying them, ensuring that they work as intended without disrupting the service.
Reference:
Google Cloud Armor Documentation
Using Preview Mode
정답:
Explanation:
Objective: Reduce the risk of Google Cloud user accounts being compromised.
Solution: Implement strong password policies and post-SSO 2-Step Verification using security keys.
Steps:
Step 1: In Active Directory, configure a domain password policy with strong settings (e.g., complexity, length, expiration).
Step 2: In the Google Admin console, navigate to the Security settings.
Step 3: Enable 2-Step Verification and configure it to use security keys for post-SSO verification.
Step 4: Ensure all users enroll in the 2-Step Verification with security keys.
Using strong password policies in Active Directory along with security keys for 2-Step Verification post-SSO provides enhanced security against account compromises.
Reference:
Active Directory Password Policies
Google Admin Console 2-Step Verification
정답:
Explanation:
Objective: Provide evidence of access reviews for an upcoming audit.
Solution: Use Policy Analyzer to review and report on IAM policies.
Steps:
Step 1: Open the Google Cloud Console.
Step 2: Navigate to the Policy Analyzer tool.
Step 3: Select the project for which you need to review access policies.
Step 4: Use the tool to generate reports on IAM roles and permissions.
Step 5: Export the reports as evidence for the audit.
Policy Analyzer provides detailed insights into IAM policies, helping you to review access configurations and generate necessary reports for compliance and auditing purposes.
Reference:
Policy Analyzer Documentation
정답:
Explanation:
Reference: https://cloud.google.com/resource-manager/docs/organization-policy/restricting-service-accounts
You can use the iam.disableServiceAccountCreation boolean constraint to disable the creation of new service accounts. This allows you to centralize management of service accounts while not restricting the other permissions your developers have on projects. https://cloud.google.com/resource-manager/docs/organization-policy/restricting-service-accounts#disable_service_account_creation
정답:
Explanation:
Pseudonymization is a de-identification technique that replaces sensitive data values with cryptographically generated tokens. Pseudonymization is widely used in industries like finance and healthcare to help reduce the risk of data in use, narrow compliance scope, and minimize the exposure of sensitive data to systems while preserving data utility and accuracy. https://cloud.google.com/dlp/docs/pseudonymization
정답:
Explanation:
Objective: Ensure that a Cloud Storage bucket in Project A can only be readable from Project B and prevent data access or copying to Cloud Storage buckets outside the network, even with correct credentials.
Solution: Use VPC Service Controls to create a security perimeter.
Steps:
Step 1: Open the Google Cloud Console.
Step 2: Navigate to the VPC Service Controls page.
Step 3: Create a new service perimeter.
Step 4: Add Project A and Project B to the service perimeter.
Step 5: Include Cloud Storage service in the perimeter configuration.
Step 6: Define access levels to ensure that only resources within the perimeter can access the Cloud Storage bucket.
By setting up a VPC Service Controls perimeter, you can enforce security boundaries that restrict data access and movement to within defined projects, providing an extra layer of protection beyond IAM permissions.
Reference:
VPC Service Controls Overview
Configuring VPC Service Controls
정답:
Explanation:
There is mention about simulating in Web Security Scanner. "Web Security Scanner cross-site scripting (XSS) injection testing *simulates* an injection attack by inserting a benign test string into user-editable fields and then performing various user actions." https://cloud.google.com/security-command-center/docs/how-to-remediate-web-security-scanner-findings#xss
Reference: https://cloud.google.com/security-scanner/docs/remediate-findings
정답:
Explanation:
To manage user accounts and ensure they comply with corporate policies, using Google Cloud Directory Sync (GCDS) allows synchronization between your local identity system and Cloud Identity. The Transfer Tool for Unmanaged Users (TTUU) helps identify and manage conflicting accounts by allowing users to transfer their personal accounts to managed accounts.
Steps:
Synchronize Identities: Use GCDS to sync users from your local identity management system to Cloud Identity, ensuring that all corporate user accounts are managed.
Identify Conflicting Accounts: Use TTUU to find users who have personal Google accounts using corporate email addresses.
Manage Conflicting Accounts: Request users to transfer their personal accounts to managed accounts using TTUU, ensuring all accounts are under corporate control.
Reference:
Google Cloud Directory Sync
Transfer Tool for Unmanaged Users
정답:
Explanation:
Setting up separate service perimeters for dev, staging, and prod environments allows for more granular control and monitoring. Automating the addition of new projects to the respective perimeters ensures that all projects are consistently secured without manual intervention.
Steps:
Set Up Service Perimeters: Use Access Context Manager to define and configure three separate service perimeters for dev, staging, and prod.
Deploy Monitoring Function: Create a Cloud Function that monitors the "implementation" folder for new projects using Stackdriver (Cloud Monitoring) and Cloud Pub/Sub.
Automate Perimeter Updates: Configure the Cloud Function to execute Terraform scripts that automatically add new projects to the appropriate service perimeter.
Reference:
Google Cloud: Access Context Manager
Service perimeter automation
정답:
Explanation:
Uniform bucket-level access allows you to manage permissions at the bucket level, rather than at the
object level. This simplifies permission management and ensures that access to objects is controlled consistently via IAM roles, without allowing uploaders full control over the objects.
Steps:
Enable Uniform Bucket-Level Access: In the Google Cloud Console, enable uniform bucket-level access for the Cloud Storage bucket.
Configure IAM Policies: Assign appropriate IAM roles to users and groups to control access to the bucket.
Audit Logging: Enable Cloud Audit Logs to track access and modifications to the bucket.
Reference:
Google Cloud: Uniform bucket-level access
Managing access with IAM
정답:
Explanation:
The Standard Tier network only provides regional load balancing, while the Premium Tier supports global load balancing with a single anycast IP address. To distribute requests across multiple regions, you need to use the Premium Tier and update the load balancer configuration accordingly.
Steps:
Upgrade to Premium Tier: Update the load balancer to use the Premium Tier network in the Google Cloud Console.
Add New Instance Group: Add the instance group in the new region (us-east-2) to the backend configuration of the existing load balancer.
Verify Configuration: Ensure that the frontend configuration of the load balancer uses a single
external IP address for global distribution.
Reference:
Google Cloud: Global load balancing
정답:
Explanation:
To restrict access to the MySQL instance to only the frontend application while other VMs are present in the subnets, creating an ingress firewall rule is the most appropriate approach. This rule will specifically allow traffic from subnet A (where the frontend application resides) to the MySQL instance in subnet B on port 3306, using network tags to target the specific MySQL VM.
Steps:
Create Network Tags: Apply a network tag (e.g., "data-tag") to the MySQL VM in subnet B.
Create Ingress Firewall Rule: Configure an ingress firewall rule with the following settings:
Source IP Range: Subnet A's IP range.
Target Tag: "data-tag".
Allowed Protocol/Ports: TCP:3306 (for MySQL).
This setup ensures that only instances in subnet A can communicate with the MySQL instance on port 3306.
Reference:
Google Cloud: Configuring firewall rules
정답:
Explanation:
Admin activity logs are always created to log entries for API calls or other actions that modify the configuration or metadata of resources. For example, these logs record when users create VM instances or change Identity and Access Management permissions.
Reference: https://cloud.google.com/iam/docs/audit-logging/examples-service-accounts