Google Associate Cloud Engineer Practice Test 54
Question 530
A BigQuery external table reads Cloud Storage objects but an auditor expects BigQuery table ACLs to grant every user direct object-storage access. What boundary must be checked?
- Define approved row access policies and test query behavior for each authorized principal.
- Set a shorter result-cache lifetime as the only correction for the described query behavior.
- Review the external connection identity or caller's required Cloud Storage read permissions separately from BigQuery dataset authorization.
- Increase BigQuery query concurrency while leaving the table design and filters unchanged.
Explanation
Correct Answer
C:External data sources have independent storage permissions; BigQuery access does not automatically grant Google Cloud Storage object read rights.
Incorrect Answers
A:The alternative does not address the query or storage behavior driving the workload. It leaves the requested BigQuery operation unaddressed. The appropriate action here is: Review the external connection identity or caller's required Cloud Storage read permissions separately from BigQuery dataset authorization.
B:The alternative does not address the query or storage behavior driving the workload. The specific requirement concerns the requested BigQuery operation. The appropriate action here is: Review the external connection identity or caller's required Cloud Storage read permissions separately from BigQuery dataset authorization.
D:The alternative does not address the query or storage behavior driving the workload. The necessary distinction is the requested BigQuery operation. The appropriate action here is: Review the external connection identity or caller's required Cloud Storage read permissions separately from BigQuery dataset authorization.
Question 531
A BigQuery workload repeatedly writes a daily table with changing schema, making downstream queries fail on missing fields. What controls should be used?
- Apply BigQuery policy tags/data masking or column-level security and verify authorized role permissions.
- Version the ingest schema contract and run schema compatibility checks before loading or replacing production partitions.
- Grant every analyst BigQuery Admin without modifying the requested dataset behavior.
- Add a dataset label instead of changing the query or table feature involved.
Explanation
Correct Answer
B:BigQuery supports schema evolution but downstream consumers still require a governed contract for field additions or removals.
Incorrect Answers
A:The alternative does not address the query or storage behavior driving the workload. The specific requirement concerns the requested BigQuery operation. The appropriate action here is: Version the ingest schema contract and run schema compatibility checks before loading or replacing production partitions.
C:The alternative does not address the query or storage behavior driving the workload. The necessary distinction is the requested BigQuery operation. The appropriate action here is: Version the ingest schema contract and run schema compatibility checks before loading or replacing production partitions.
D:The alternative does not address the query or storage behavior driving the workload. The case instead depends on the requested BigQuery operation. The appropriate action here is: Version the ingest schema contract and run schema compatibility checks before loading or replacing production partitions.
Question 532
A BigQuery query uses SELECT * over a wide table when consumers need only two fields, inflating billed bytes. What change reduces scanning?
- Apply BigQuery policy tags/data masking or column-level security and verify authorized role permissions.
- Add a dataset label instead of changing the query or table feature involved.
- Copy the data to a Compute Engine disk and run the same analytics workload without query changes.
- Project only required columns and apply selective predicates, then confirm bytes processed in the job plan.
Explanation
Correct Answer
D:Columnar BigQuery storage can avoid reading unneeded fields; selecting all columns discards that efficiency.
Incorrect Answers
A:The alternative does not address the query or storage behavior driving the workload. The necessary distinction is the requested BigQuery operation. The appropriate action here is: Project only required columns and apply selective predicates, then confirm bytes processed in the job plan.
B:The alternative does not address the query or storage behavior driving the workload. The case instead depends on the requested BigQuery operation. The appropriate action here is: Project only required columns and apply selective predicates, then confirm bytes processed in the job plan.
C:The alternative does not address the query or storage behavior driving the workload. It leaves the requested BigQuery operation unaddressed. The appropriate action here is: Project only required columns and apply selective predicates, then confirm bytes processed in the job plan.
Question 533
A Bigtable autoscaling configuration caps nodes too low and the cluster experiences sustained CPU pressure at peak time. What should be adjusted?
- Change to a suitable multi-cluster routing app profile with consistency and latency trade-offs understood.
- Write every new value under a sequential leading key even when write hotspots remain.
- Change the Bigtable cluster display name as a substitute for the required data operation.
- Increase the allowed autoscaling max nodes within budget and quotas and assess CPU/storage goals using cluster metrics.
Explanation
Correct Answer
D:Bigtable autoscaling needs headroom; a hard node cap can prevent scaling even when demand rises.
Incorrect Answers
A:It does not correct the Bigtable row-key, cluster or data-access requirement. The case instead depends on the intended autoscaling control.
B:It does not correct the Bigtable row-key, cluster or data-access requirement. It leaves the intended autoscaling control unaddressed.
C:Display names and labels identify resources; they do not enforce their runtime behavior. The specific requirement concerns the intended autoscaling control.
Question 534
A Bigtable table is retaining old cell versions indefinitely and storage grows faster than business data volume. What should be configured?
- Increase the allowed autoscaling max nodes within budget and quotas and assess CPU/storage goals using cluster metrics.
- Set column-family garbage-collection rules appropriate to maximum age or retained version count.
- Rebuild only the client VM image while leaving the Bigtable table configuration unchanged.
- Write every new value under a sequential leading key even when write hotspots remain.
Explanation
Correct Answer
B:Bigtable garbage collection manages obsolete cell versions within families, not by replacing an entire database instance.
Incorrect Answers
A:It does not correct the Bigtable row-key, cluster or data-access requirement. It leaves the required key-oriented data access unaddressed.
C:It does not correct the Bigtable row-key, cluster or data-access requirement. The specific requirement concerns the required key-oriented data access. The appropriate action here is: Set column-family garbage-collection rules appropriate to maximum age or retained version count.
D:It does not correct the Bigtable row-key, cluster or data-access requirement. The necessary distinction is the required key-oriented data access.
Question 535
A Bigtable multi-cluster application sends all requests to one failed cluster because routing policy uses a single-cluster app profile. What should be evaluated?
- Change to a suitable multi-cluster routing app profile with consistency and latency trade-offs understood.
- Verify app-profile routing, replication health, backups and available capacity before decommissioning a cluster.
- Use a relational SQL join instead of the row-key-oriented access needed here.
- Increase the Bigtable node count without examining the row-key distribution or required data model.
Explanation
Correct Answer
A:Bigtable app profiles control cluster routing; replication does not automatically guarantee a client routes away from a failed pinned cluster.
Incorrect Answers
B:It does not correct the Bigtable row-key, cluster or data-access requirement. The specific requirement concerns the requested latency measurement.
C:It does not correct the Bigtable row-key, cluster or data-access requirement. The necessary distinction is the requested latency measurement.
D:It does not correct the Bigtable row-key, cluster or data-access requirement. The case instead depends on the requested latency measurement.
Question 536
An application changes a Bigtable row-key schema and suddenly has high hot-node CPU because new records share a common prefix. What should be checked?
- Increase the allowed autoscaling max nodes within budget and quotas and assess CPU/storage goals using cluster metrics.
- Write every new value under a sequential leading key even when write hotspots remain.
- Rebuild only the client VM image while leaving the Bigtable table configuration unchanged.
- Review key distribution and adjust schema or salting strategy to spread writes across tablets without losing range-query requirements.
Explanation
Correct Answer
D:Bigtable sorted row keys affect load distribution; concentrated prefix patterns can overload specific tablets.
Incorrect Answers
A:It does not correct the Bigtable row-key, cluster or data-access requirement. The necessary distinction is Bigtable row-key distribution. The appropriate action here is: Review key distribution and adjust schema or salting strategy to spread writes across tablets without losing range-query requirements.
B:It does not correct the Bigtable row-key, cluster or data-access requirement. The case instead depends on Bigtable row-key distribution. The appropriate action here is: Review key distribution and adjust schema or salting strategy to spread writes across tablets without losing range-query requirements.
C:It does not correct the Bigtable row-key, cluster or data-access requirement. It leaves Bigtable row-key distribution unaddressed.
Question 537
An operator deletes a Bigtable cluster believing its replicated sibling will immediately replace its contribution without impact. Which risk should be assessed?
- Change to a suitable multi-cluster routing app profile with consistency and latency trade-offs understood.
- Turn on a backup schedule and assume it also repairs live key or access patterns.
- Verify app-profile routing, replication health, backups and available capacity before decommissioning a cluster.
- Increase the Bigtable node count without examining the row-key distribution or required data model.
Explanation
Correct Answer
C:Replication topology and per-cluster load must support continued operations after a cluster is removed.
Incorrect Answers
A:It does not correct the Bigtable row-key, cluster or data-access requirement. The case instead depends on the required key-oriented data access. The appropriate action here is: Verify app-profile routing, replication health, backups and available capacity before decommissioning a cluster.
B:Backups protect recovery points but do not automatically change live database behavior. It leaves the required key-oriented data access unaddressed.
D:It does not correct the Bigtable row-key, cluster or data-access requirement. The specific requirement concerns the required key-oriented data access. The appropriate action here is: Verify app-profile routing, replication health, backups and available capacity before decommissioning a cluster.
Question 538
A Cloud Storage bucket allows object overwrites, but a user must recover the prior generation of one accidentally replaced file. What action should be taken?
- Apply generation-match preconditions or an agreed conditional-write protocol to prevent conflicting overwrites.
- Locate the retained noncurrent object generation under versioning and restore it to a new live generation with audit evidence.
- Turn off Object Versioning and rely on the current live object to reconstruct a prior generation.
- Make the Cloud Storage bucket publicly readable instead of configuring a scoped access mechanism.
Explanation
Correct Answer
B:Object versioning preserves previous generations if configured before the overwrite; it does not require restoring an entire bucket.
Incorrect Answers
A:The option does not enforce the required object location, access or lifecycle behavior. It leaves preservation of object generations unaddressed.
C:Removing version history cannot reconstruct a deleted or overwritten historical object generation.
D:Public access expands exposure without meeting the requested scoped-control requirement. The necessary distinction is preservation of object generations.
Question 539
A Cloud Storage bucket has a retention lock but an operator tries to shorten the locked period for cost savings. What outcome should they anticipate?
- Keep the locked retention policy and create an approved future-data strategy rather than attempting to weaken existing retention.
- Verify the effective retention policy and legal hold status and follow authorized compliance release procedures before deletion.
- Change only the storage class and assume it adds recovery, locking or IAM rights.
- Grant organization-wide Storage Admin as a substitute for the required targeted operation.
Explanation
Correct Answer
A:A locked bucket retention policy is designed to prevent reducing or removing the retention protection.
Incorrect Answers
B:The option does not enforce the required object location, access or lifecycle behavior. The specific requirement concerns retention or recoverability controls.
C:Storage class changes cost and access behavior, not the required policy by itself. The necessary distinction is retention or recoverability controls.
D:Broad Storage Admin access introduces privileges beyond the stated task. The case instead depends on retention or recoverability controls. The appropriate action here is: Keep the locked retention policy and create an approved future-data strategy rather than attempting to weaken existing retention.
Question 540
A bucket receives thousands of user uploads but no change notifications reach the consuming service because the event filter uses the wrong bucket name. What should be corrected?
- Locate the retained noncurrent object generation under versioning and restore it to a new live generation with audit evidence.
- Update Eventarc or Pub/Sub notification filters to the actual bucket and validated object-finalize event type.
- Grant organization-wide Storage Admin as a substitute for the required targeted operation.
- Increase the caller VM memory without modifying any bucket or object behavior.
Explanation
Correct Answer
B:Cloud Storage event notifications need exact source and event filters; changing a consumer's CPU cannot restore missed routing.
Incorrect Answers
A:Object versioning and the requested retention or deletion safeguards are separate mechanisms. The necessary distinction is the object's required data or access behavior. The appropriate action here is: Update Eventarc or Pub/Sub notification filters to the actual bucket and validated object-finalize event type.
C:Broad Storage Admin access introduces privileges beyond the stated task. The case instead depends on the object's required data or access behavior. The appropriate action here is: Update Eventarc or Pub/Sub notification filters to the actual bucket and validated object-finalize event type.
D:Memory sizing may change capacity but cannot replace the specified platform feature. It leaves the object's required data or access behavior unaddressed.