Prepare and test your skills

Prepare and test your skills

Free sample question, answered and explained below. The Professional Data Engineer practice bank has 1,353 more like it. Try 10 free: instant score, no account.
A connected vehicle platform ingests real-time telemetry from over 500,000 vehicles streaming diagnostic metrics at 1-second intervals. The data engineering team needs to design a high-throughput storage tier in Cloud Bigtable that satisfies the following requirements:
Which row key pattern and cluster target should you implement?
timestamp#vehicle_id and configure cluster autoscaling to maintain a maximum CPU utilization target of 90%.This design prefixes the row key with a monotonically increasing timestamp value followed by the vehicle_id, while operating the cluster at a 90% CPU utilization target.
This row key pattern would only be suitable if the primary access pattern was scanning across all vehicles at a single instant in time in a batch processing pipeline where latency is not a priority.
vehicle_id#timestamp and configure cluster autoscaling to maintain a maximum CPU utilization target of 60%.This architecture uses a composite row key design (vehicle_id#timestamp) paired with latency-optimized cluster capacity targets to handle high-velocity time-series ingestion and range reads in Cloud Bigtable.
vehicle_id ensures all chronological events for an individual vehicle are stored sequentially in contiguous rows. Client applications can perform high-speed row-range scans using a specific vehicle_id prefix and start/end timestamps.Placing vehicle_id as the primary prefix avoids monotonically increasing key hot spots, while appending the timestamp enables fast sequential row-range retrieval. Sizing the cluster for 60% CPU utilization guarantees predictable sub-10ms response times for real-time diagnostic queries.
md5(vehicle_id#timestamp) and configure cluster autoscaling to maintain a maximum storage utilization target of 85%.This pattern calculates a complete MD5 cryptographic hash of the concatenated vehicle ID and timestamp to serve as the row key, while running the cluster at 85% storage utilization per node.
vehicle_id and timestamp produces a completely randomized key distribution. Because lexicographical ordering is lost, sequential time-series records for a single vehicle are scattered across different tablets, making row-range scans impossible.This approach would be appropriate for a pure key-value point lookup workload where range scans are never performed and storage cost minimization is prioritized over query latency.
vehicle_id with each metric stored in separate timestamped cells within a single row, and maintain a maximum CPU utilization target of 90%.This approach uses a single static row per vehicle (vehicle_id as the row key) and appends incoming periodic metric updates as new timestamped versions (cells) within the same row, targeting 90% CPU utilization.
This pattern would be acceptable if each vehicle reported only a small, bounded number of historical updates (e.g., maintaining only the single most recent status update with garbage collection configured to retain 1 version).
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