Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Developer practice bank has an additional 608 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
You are designing the Cloud Storage data organization for a multi-workload enterprise application with the following requirements:
staging and processed directories via folder renames while preserving object creation timestamps so age-based Object Lifecycle Management (OLM) rules execute on schedule.Which bucket and naming architecture should you implement?
restricted/cust-id/...) for lifecycle filtering and discoverability, and simulate analytics folder renames by copying and deleting objects between staging/ and processed/ prefixes.This design relies exclusively on flat namespace buckets, encodes sensitive classification and customer identifiers directly into object name prefixes, and emulates directory renames by copying objects to a new prefix and deleting the originals.
staging/ and processed/ are merely strings in the object name. Renaming a simulated folder requires copying every object to the destination prefix and deleting the source object. This creates brand-new objects with reset creation timestamps, preventing age-based Object Lifecycle Management (OLM) rules at processed/ from executing on the original schedule.restricted or cust-id directly in object names violates security best practices. Object names are visible in bucket listings, access URLs, and error probing responses, risking exposure of personally identifiable information (PII) or internal governance tiers.x-goog-meta custom metadata rather than object or bucket names.Analytics pipelines did not rely on preserving original creation timestamps for age-based OLM rules, rename operations involved very few objects, and the encoded prefixes contained no sensitive or identifying information.
<timestamp>/<hash> to align with chronological lifecycle rules.This option proposes migrating an existing flat namespace bucket to hierarchical namespace (HNS) through a metadata update, applying per-object Object Retention Lock, and structuring telemetry object keys with a leading timestamp followed by a hash.
<timestamp>/<hash>): Placing a hash after a sequential timestamp (<timestamp>/<hash>) fails to prevent hotspotting. Because Cloud Storage indexes object keys in lexicographical order, every burst of writes with the current timestamp hits the same narrow range of the index, throttling throughput.<hash>-<timestamp>) to spread writes evenly across backend servers.Hierarchical namespace were configured at bucket creation in a separate analytics bucket, Bucket Lock were used on a flat compliance bucket, and the hash were placed before the timestamp rather than after it.
x-goog-meta custom headers; store analytics datasets in a hierarchical namespace bucket; and name telemetry objects with a hash before the timestamp under a common prefix (logs/<hash>-<timestamp>).This design separates workloads across flat namespace and hierarchical namespace (HNS) Cloud Storage buckets based on feature compatibility, while pairing custom object metadata and hash-prefixed naming to satisfy security, lifecycle, and throughput requirements.
x-goog-meta custom headers keeps confidential metadata out of object names, preventing exposure in object URLs, bucket listings, and unauthorized existence probing.RenameFolder operates atomically at the folder level without copying or recreating objects, which preserves original creation times so age-based Object Lifecycle Management (OLM) rules apply immediately when objects qualify.logs/<hash>-<timestamp>) distributes object keys evenly across Cloud Storage's lexicographical index while still allowing OLM rules to match the logs/ prefix.429 or 5xx throttling during high-volume telemetry ingestion.Attempting to combine Bucket Lock with HNS in a single bucket fails due to platform incompatibilities, and using flat namespaces for frequent folder renames resets object ages. Isolating workloads by namespace and applying hash-before-timestamp naming under a fixed prefix delivers full compliance, accurate lifecycle timing, and predictable auto-scaling.
logs/YYYY-MM-DD-HH/<uuid>).This approach attempts to consolidate all workloads into a single hierarchical namespace (HNS) bucket using Bucket Lock for retention, managed folders for IAM isolation, and sequential time-bucketed prefixes followed by UUIDs for telemetry ingestion.
logs/YYYY-MM-DD-HH/<uuid>) restricts auto-scaling benefits to the current hour's prefix. Each time the hour rolls over, write traffic shifts to a brand-new sequential index range, forcing Cloud Storage to re-partition servers repeatedly and causing elevated latency or errors above 1,000 writes per second.The compliance workload did not require Bucket Lock or retention immutability, sensitive classification did not need to be hidden from object paths, and telemetry writes stayed well below 1,000 writes per second or gradually ramped up on each new hourly prefix.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated