Hard1 markMultiple Choice
GCP PCA · Question 16 · Technical Requirements
CASE STUDY: ManuIoT
Overview:
Industry: Manufacturing
Size: 100 factories globally
Environment:
- 100,000 sensors
- Local SCADA
- Fragmented SQL Server DBs
- No central analytics
Requirements:
- Predictive maintenance
- Real-time global dashboards
- Edge computing
Exec Statements:
- CEO: Monetize telemetry.
- CFO: Costs must scale linearly.
- VP Ops: Factory lines need local control if internet drops.
Tech Reqs:
- Ingest 1M msgs/sec
- Stream processing
- Offline factory capabilities
- Train ML centrally, deploy to edge
Constraints:
- Low bandwidth/high latency at factories
- Legacy MQTT protocol
- Zero IT staff at factories
QUESTION: How should you architect the ingestion layer to handle 1 million MQTT messages per second from the legacy sensors?
CASE STUDY: ManuIoT
Overview:
Industry: Manufacturing
Size: 100 factories globally
Environment:
- 100,000 sensors
- Local SCADA
- Fragmented SQL Server DBs
- No central analytics
Requirements:
- Predictive maintenance
- Real-time global dashboards
- Edge computing
Exec Statements:
- CEO: Monetize telemetry.
- CFO: Costs must scale linearly.
- VP Ops: Factory lines need local control if internet drops.
Tech Reqs:
- Ingest 1M msgs/sec
- Stream processing
- Offline factory capabilities
- Train ML centrally, deploy to edge
Constraints:
- Low bandwidth/high latency at factories
- Legacy MQTT protocol
- Zero IT staff at factories
QUESTION: How should you architect the ingestion layer to handle 1 million MQTT messages per second from the legacy sensors?
Answer options:
A.
Send messages directly from sensors to Cloud Pub/Sub using the REST API.
B.
Deploy an MQTT broker on Compute Engine or GKE that bridges messages to Cloud Pub/Sub.
C.
Use Cloud IoT Core to ingest the MQTT messages directly.
D.
Write the MQTT messages directly to a global Cloud Spanner database.
How to approach this question
Recognize that Cloud IoT Core is deprecated and identify the modern pattern for MQTT ingestion into GCP.
Full Answer
B.Deploy an MQTT broker on Compute Engine or GKE that bridges messages to Cloud Pub/Sub.✓ Correct
With the deprecation of Cloud IoT Core, the recommended architecture for IoT ingestion is to use a partner solution or host an MQTT broker (like HiveMQ or Mosquitto) on GKE/Compute Engine. This broker accepts the legacy MQTT connections and publishes the payloads to Cloud Pub/Sub, which easily scales to 1M messages/sec.
Common mistakes
Selecting Cloud IoT Core (C) based on outdated documentation.
Practice the full GCP Professional Cloud Architect Practice Exam 6
50 questions · hints · full answers · grading
More questions from this exam
Q01CASE STUDY: TechStream Gaming
Overview:
Industry: Gaming
Size: 500 employees, $100M revenue
Env...MediumQ02CASE STUDY: TechStream Gaming
Overview:
Industry: Gaming
Size: 500 employees, $100M revenue
Env...MediumQ03CASE STUDY: TechStream Gaming
Overview:
Industry: Gaming
Size: 500 employees, $100M revenue
Env...HardQ04CASE STUDY: TechStream Gaming
Overview:
Industry: Gaming
Size: 500 employees, $100M revenue
Env...MediumQ05CASE STUDY: TechStream Gaming
Overview:
Industry: Gaming
Size: 500 employees, $100M revenue
Env...Easy
Expert