Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Google Professional Cloud Architect (PR000213) Exam - Topic 3 Question 109 Discussion

For this question, refer to the TerramEarth case study. You are asked to design a new architecture for theingestion of the data of the 200,000 vehicles that are connected to a cellular network. You want to followGoogle-recommended practices.Considering the technical requirements, which components should you use for the ingestion of the data?
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

Google Professional Cloud Architect (PR000213) Exam - Topic 3 Question 109 Discussion

Actual exam question for Google's Professional Cloud Architect (PR000213) exam
Question #: 109
Topic #: 3
[All Professional Cloud Architect (PR000213) Questions]

For this question, refer to the TerramEarth case study. You are asked to design a new architecture for the

ingestion of the data of the 200,000 vehicles that are connected to a cellular network. You want to follow

Google-recommended practices.

Considering the technical requirements, which components should you use for the ingestion of the data?

Show Suggested Answer Hide Answer
Suggested Answer: A

https://cloud.google.com/solutions/iot-overview

https://cloud.google.com/iot/quotas


by Kristeen at Jul 10, 2025, 01:52 PM

Limited Time Offer

25%

Off

Get Premium Professional Cloud Architect (PR000213) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Kimbery
7 months ago
Totally agree, Cloud IoT Core is the best choice here!
upvoted 0 times
...
Tijuana
7 months ago
Wait, are we really considering Compute Engine for this? Seems outdated.
upvoted 0 times
...
Frederick
7 months ago
Definitely going with Cloud IoT Core for secure data ingestion.
upvoted 0 times
...
Rosenda
7 months ago
I think GKE is overkill for this.
upvoted 0 times
...
Carmen
7 months ago
Not sure if public/private keys are the way to go. What about scalability?
upvoted 0 times
...
Aretha
8 months ago
I keep getting confused between the options, but I think Cloud IoT Core aligns best with Google’s best practices for IoT data.
upvoted 0 times
...
Merlyn
8 months ago
I practiced a similar question, and I think Compute Engine options might not be the best fit for this scenario since they seem more manual.
upvoted 0 times
...
Frederica
8 months ago
I'm not entirely sure, but I feel like Google Kubernetes Engine could also work for handling large-scale data ingestion.
upvoted 0 times
...
Sheridan
8 months ago
I remember we discussed the importance of secure data ingestion, so I think Cloud IoT Core with public/private key pairs might be the right choice.
upvoted 0 times
...
Lillian
9 months ago
The SSL Ingress in option A sounds like a good security feature, but I'm not sure if that's the most appropriate solution for this specific use case.
upvoted 0 times
...
Ashley
9 months ago
I'm a bit unsure about the differences between the Kubernetes and Compute Engine options. I'll need to review those in more detail to make a confident choice.
upvoted 0 times
...
Gwen
9 months ago
I'm leaning towards option B, Cloud IoT Core with public/private key pairs, as that seems to align best with the requirements and Google's recommendations.
upvoted 0 times
...
Layla
9 months ago
Okay, let's think this through step-by-step. The key is to focus on the Google-recommended practices for ingesting data from a large number of connected vehicles.
upvoted 0 times
...
Elvis
9 months ago
This question seems straightforward, but I want to make sure I understand the requirements correctly before answering.
upvoted 0 times
...
Matilda
11 months ago
Personally, I think B) Cloud IoT Core with public/private key pairs is the way to go. It's like putting your data in a vault with a secret handshake. Genius!
upvoted 0 times
Iluminada
10 months ago
I agree, B) Cloud IoT Core with public/private key pairs provides an extra layer of security.
upvoted 0 times
...
...
Cecil
11 months ago
I don't know, you guys. I'm kind of leaning towards C) Compute Engine with project-wide SSH keys. Seems like the easiest option, and hey, what could go wrong?
upvoted 0 times
...
Michal
11 months ago
I'm leaning towards Compute Engine with specific SSH keys for better security.
upvoted 0 times
...
Craig
11 months ago
D) Compute Engine with specific SSH keys sounds like a good choice. I mean, who doesn't love a little extra security?
upvoted 0 times
Josphine
10 months ago
User 2: B) Cloud IoT Core with public/private key pairs seems like a more secure option.
upvoted 0 times
...
Johnson
10 months ago
User 1: I think A) Google Kubernetes Engine with an SSL Ingress is the way to go.
upvoted 0 times
...
...
Fatima
11 months ago
Hmm, I'm not sure. I'd probably go with A) Google Kubernetes Engine with an SSL Ingress. Seems like the most Google-y option, if you ask me.
upvoted 0 times
Casey
10 months ago
Yeah, it seems like the most Google-y option for ingesting data from 200,000 vehicles.
upvoted 0 times
...
Theron
10 months ago
I agree, it follows Google-recommended practices.
upvoted 0 times
...
Bea
11 months ago
I think A) Google Kubernetes Engine with an SSL Ingress is a good choice.
upvoted 0 times
...
...
Alva
12 months ago
I disagree, I believe Cloud IoT Core with public/private key pairs would be a better choice.
upvoted 0 times
...
Lavonda
12 months ago
I think we should use Google Kubernetes Engine with an SSL Ingress.
upvoted 0 times
...
Thurman
12 months ago
I think B) Cloud IoT Core with public/private key pairs is the way to go. Gotta keep that data secure, you know?
upvoted 0 times
Kallie
11 months ago
Using public/private key pairs is a smart choice to ensure data protection.
upvoted 0 times
...
Lorean
11 months ago
I agree, security is definitely a top priority when dealing with sensitive data.
upvoted 0 times
...
...

Save Cancel