Question 480
A BigQuery cost review must choose between scanning less data and changing compute infrastructure. How should the team proceed?
- Analyze storage-class retrieval and operations costs before changing its class
- Estimate query bytes processed and apply partitioning or clustering where suitable
- Review Cloud KMS key-version disablement effects before changing it
- Include applicable network egress and retrieval charges in the estimate
- Review Cloud Storage operations pricing and request patterns
Explanation
Correct Answer
B:BigQuery query billing and performance are influenced by the workload and pricing model. Better query pruning can reduce scanned data without provisioning VMs.
Incorrect Answers
A:Using this action would assess retrieval cost in cold storage, not lower BigQuery query consumption. Its function is different from the specific change described in the scenario.
C:The choice is aimed at a different purpose: to control access through key lifecycle; Even if it can manage CMEK key version availability, that would not accomplish the stated requirement to lower BigQuery query consumption.
D:It can estimate object transfer and retrieval cost; however, it does not provide the specific operation to lower BigQuery query consumption. The two controls serve different purposes.
E:This choice is useful to analyze object request cost. The stated task is to lower BigQuery query consumption, which requires a different mechanism or permission scope.
Question 481
A storage team needs to use an organization-controlled key for an eligible Cloud Storage bucket. Which configuration best meets the requirement?
- Review Cloud KMS key-version disablement effects before changing it
- Configure a Cloud KMS customer-managed encryption key for the bucket
- Configure a compatible Cloud KMS key and required permissions when provisioning the database
- Restore the correct KMS key usage permissions to the service identity
Explanation
Correct Answer
B:CMEK lets the organization control a supported encryption key's lifecycle through Cloud KMS. The storage service identity needs the requisite key access.
Incorrect Answers
A:Administrators use it to manage CMEK key version availability, rather than to apply KMS-based Cloud Storage encryption. Applying it would change the wrong component of this deployment.
C:Its purpose is to use CMEK for an eligible managed database. That distinction matters: the scenario calls for an action to apply KMS-based Cloud Storage encryption, not this separate configuration task.
D:This approach can authorize a service to use its KMS key. The requirement is to apply KMS-based Cloud Storage encryption, so it controls a different part of the workflow and leaves that result unaddressed.
Question 482
A Cloud SQL instance requires supported customer-managed encryption key integration at creation. What should be configured?
- Configure a compatible Cloud KMS key and required permissions when provisioning the database
- Restore the correct KMS key usage permissions to the service identity
- Review Cloud Storage operations pricing and request patterns
- Configure a Cloud KMS customer-managed encryption key for the bucket
- Review Cloud KMS key-version disablement effects before changing it
Explanation
Correct Answer
A:CMEK for databases has product-specific timing and location requirements. Enabling the key after creating an incompatible instance does not automatically retrofit every setting.
Incorrect Answers
B:It can authorize a service to use its KMS key; however, it does not provide the specific operation to control relational storage encryption keys. The two controls serve different purposes.
C:In a workflow for storage cost analysis, it can analyze object request cost; This question instead asks how to control relational storage encryption keys; substituting the former action would leave that distinct technical requirement unmet.
D:The tool can encrypt objects with a customer-managed key, but it cannot be substituted for the capability needed to control relational storage encryption keys. Its operational effect is not equivalent.
E:This mechanism is intended to manage CMEK key version availability. It does not implement the required action to control relational storage encryption keys, even though both are relevant to the same general service.
Question 483
A service cannot decrypt its CMEK-protected data after a key permission was removed. Which action is most appropriate?
- Configure a Cloud KMS customer-managed encryption key for the bucket
- Review Cloud KMS key-version disablement effects before changing it
- Configure a compatible Cloud KMS key and required permissions when provisioning the database
- Grant a suitable Storage Object Viewer role on the specific bucket
- Restore the correct KMS key usage permissions to the service identity
Explanation
Correct Answer
E:Services using CMEK must be authorized to invoke the necessary cryptographic operations. Ordinary data reader IAM alone cannot replace missing key access.
Incorrect Answers
A:Its purpose is to encrypt objects with a customer-managed key. That distinction matters: the scenario calls for an action to repair denied CMEK decryption, not this separate configuration task.
B:This setting would manage CMEK key version availability. That behavior does not establish the requested ability to repair denied CMEK decryption; it addresses an adjacent concern instead.
C:While this can use CMEK for an eligible managed database, the present task requires an action to repair denied CMEK decryption. This operation does not supply the behavior described in the requirements.
D:Using this action would grant read access to objects in one bucket, not repair denied CMEK decryption. Its function is different from the specific change described in the scenario.
Question 484
A compliance officer needs to disable use of a customer-managed key and understand the risk. Which solution should be used?
- Review Cloud KMS key-version disablement effects before changing it
- Configure a Cloud KMS customer-managed encryption key for the bucket
- Use Database Center for supported database inventory and management insights
- Configure a compatible Cloud KMS key and required permissions when provisioning the database
- Restore the correct KMS key usage permissions to the service identity
Explanation
Correct Answer
A:Disabling a key version can make dependent encrypted data temporarily unavailable. It is a security-sensitive operation separate from object deletion.
Incorrect Answers
B:Select this when the goal is to encrypt objects with a customer-managed key. Here the decisive requirement is to control access through key lifecycle, and that outcome is not achieved by this action.
C:This alternative addresses bigtable and database administration by allowing a team to monitor a managed database fleet centrally; The incident, however, requires the different action to control access through key lifecycle, so its central configuration remains unchanged.
D:The result of this choice would be to use CMEK for an eligible managed database. The requested outcome, to control access through key lifecycle, is handled at a different layer or through another operation.
E:Administrators use it to authorize a service to use its KMS key, rather than to control access through key lifecycle. Applying it would change the wrong component of this deployment.
Question 485
A bucket has noncurrent object generations that accumulate storage costs. What is the best next step?
- Enable and review appropriate Cloud Audit Logs for Cloud Storage access
- Apply a version-aware lifecycle cleanup rule after assessing retention needs
- Enable public access prevention for the relevant bucket or inherited scope
- Honor the retention lock and wait until the permitted expiration
Explanation
Correct Answer
B:Object Versioning preserves prior generations until deleted by policy or action. Lifecycle rules can limit growth while keeping required versions.
Incorrect Answers
A:This choice is useful to capture object access audit records. The stated task is to control version storage growth, which requires a different mechanism or permission scope.
C:It can block anonymous Cloud Storage access; however, it does not provide the specific operation to control version storage growth. The two controls serve different purposes.
D:This setting would enforce immutable retention timing. That behavior does not establish the requested ability to control version storage growth; it addresses an adjacent concern instead.
Question 486
A regulated bucket has a retention policy and someone requests deleting a protected object early. Which configuration best meets the requirement?
- Enable public access prevention for the relevant bucket or inherited scope
- Honor the retention lock and wait until the permitted expiration
- Enable and review appropriate Cloud Audit Logs for Cloud Storage access
- Apply a version-aware lifecycle cleanup rule after assessing retention needs
- Configure an appropriate retention policy or object retention setting
Explanation
Correct Answer
B:Retention policies prevent deletion while protection applies. Broad IAM permissions do not automatically bypass a locked compliance retention condition.
Incorrect Answers
A:Administrators use it to block anonymous Cloud Storage access, rather than to reject prohibited early object deletion. Applying it would change the wrong component of this deployment.
C:The result of this choice would be to capture object access audit records. The requested outcome, to reject prohibited early object deletion, is handled at a different layer or through another operation.
D:Its purpose is to manage obsolete bucket generations. That distinction matters: the scenario calls for an action to reject prohibited early object deletion, not this separate configuration task.
E:The choice is aimed at a different purpose: to block premature deletion of records; Even if it can enforce object retention for compliance, that would not accomplish the stated requirement to reject prohibited early object deletion.
Question 487
A Cloud Storage object was accidentally deleted yesterday. The bucket's soft delete policy retained it, and the object is still inside the retention window. How can the team recover the object without requiring a previous versioning snapshot?
- Disable the soft delete policy before attempting recovery
- Create a new empty bucket with the same name and assume the object is recreated
- Enable public access prevention and assume the deleted object's bytes reappear automatically
- List the soft-deleted object generation and use the supported Cloud Storage soft-delete restore operation
Explanation
Correct Answer
D:Soft delete preserves eligible deleted objects for a configured period and permits restoration into a new live object. The engineer must identify the correct object generation and ensure the retention window has not expired.
Incorrect Answers
A:Disabling the protection policy is unnecessary for recovery and can remove safeguards against future deletions. Restoration uses the existing retained object.
B:A bucket name is not a backup of its contents. Creating an empty bucket cannot reproduce an object without a recovery source.
C:Public access prevention blocks public exposure but does not restore a deleted object. It is a distinct access control.
Question 488
A shared object bucket needs to avoid anonymous access even when a user adds a public principal. Which action is most appropriate?
- Review Cloud KMS key-version disablement effects before changing it
- Enable and review appropriate Cloud Audit Logs for Cloud Storage access
- Enable public access prevention for the relevant bucket or inherited scope
- Honor the retention lock and wait until the permitted expiration
- Apply a version-aware lifecycle cleanup rule after assessing retention needs
Explanation
Correct Answer
C:Public access prevention blocks relevant public exposure mechanisms. Uniform bucket-level access alone does not forbid public IAM bindings.
Incorrect Answers
A:The technical effect is to manage CMEK key version availability, not to enforce nonpublic bucket posture; That distinction matters here because the first operation serves control access through key lifecycle, rather than the scenario's required result.
B:While this can capture object access audit records, the present task requires an action to enforce nonpublic bucket posture. This operation does not supply the behavior described in the requirements.
D:This setting would enforce immutable retention timing. That behavior does not establish the requested ability to enforce nonpublic bucket posture; it addresses an adjacent concern instead.
E:This approach can manage obsolete bucket generations. The requirement is to enforce nonpublic bucket posture, so it controls a different part of the workflow and leaves that result unaddressed.
Question 489
A regional subnet is running out of usable internal IPv4 addresses and its existing services must remain online. Which method addresses the task?
- Choose a nonoverlapping expanded range or revise the network address plan
- Expand the appropriate secondary IP range where supported
- Plan a replacement subnet or supported migration rather than relying on CIDR shrink
- Expand the subnet primary IPv4 range to a supported larger CIDR
Explanation
Correct Answer
D:Subnets can have their primary range expanded under documented constraints. Shrinking to a narrower CIDR is not a normal supported reverse operation.
Incorrect Answers
A:This mechanism is intended to avoid CIDR overlap during subnet expansion. It does not implement the required action to add room for VM internal addresses, even though both are relevant to the same general service.
B:The result of this choice would be to expand a Pod secondary IP range. The requested outcome, to add room for VM internal addresses, is handled at a different layer or through another operation.
C:Select this when the goal is to handle a requested subnet shrink safely. Here the decisive requirement is to add room for VM internal addresses, and that outcome is not achieved by this action.
Question 490
A GKE VPC-native cluster needs more Pod address space but its node subnet range is sufficient. What is the best next step?
- Choose a nonoverlapping expanded range or revise the network address plan
- Check whether the address resource is regional or global before reassignment
- Plan a replacement subnet or supported migration rather than relying on CIDR shrink
- Expand the appropriate secondary IP range where supported
- Expand the subnet primary IPv4 range to a supported larger CIDR
Explanation
Correct Answer
D:Pod alias IP ranges are separate from the primary range used by nodes. Capacity troubleshooting must identify which address pool is exhausted.
Incorrect Answers
A:This setting would avoid CIDR overlap during subnet expansion. That behavior does not establish the requested ability to fix alias-IP Pod address exhaustion; it addresses an adjacent concern instead.
B:This alternative addresses static addresses and frontend identities by allowing a team to match IP scope to target resource; The incident, however, requires the different action to fix alias-IP Pod address exhaustion, so its central configuration remains unchanged.
C:This choice is useful to handle a requested subnet shrink safely. The stated task is to fix alias-IP Pod address exhaustion, which requires a different mechanism or permission scope.
E:Using this action would expand a subnet's primary IPv4 capacity, not fix alias-IP Pod address exhaustion. Its function is different from the specific change described in the scenario.