Answer-first summary for fast verification
Answer: Cloud IoT Core with public/private key pairs
The question asks for the optimal Google Cloud component for ingesting data from 200,000 vehicles connected via cellular network, following Google-recommended practices. Option B (Cloud IoT Core with public/private key pairs) is the correct choice because: 1) Cloud IoT Core is specifically designed for IoT device connectivity at scale, supporting millions of devices with secure authentication using public/private key pairs over TLS 1.2; 2) It provides managed MQTT and HTTP endpoints ideal for cellular-connected devices; 3) The community discussion shows overwhelming consensus (100% of answers and high upvotes) supporting B, with references to Google's IoT documentation and connected vehicle use cases. While Cloud IoT Core is being retired, the question context and community responses reflect its appropriateness at the time. Options A, C, and D are less suitable: A (GKE with SSL Ingress) is over-engineered for simple data ingestion and not IoT-optimized; C and D (Compute Engine with SSH keys) are inappropriate as SSH keys are for VM access, not device data ingestion.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
Based on the TerramEarth case study, you need to design a new data ingestion architecture for 200,000 vehicles connected via a cellular network, adhering to Google-recommended practices. Which specific Google Cloud components should be used for this data ingestion pipeline?
A
Google Kubernetes Engine with an SSL Ingress
B
Cloud IoT Core with public/private key pairs
C
Compute Engine with project-wide SSH keys
D
Compute Engine with specific SSH keys