Cloud Digital Leader Practice Question: Google Cloud products, services, and solutions
A company wants to send transactional emails (receipts, password resets) and marketing emails at scale from their application. Which approach is recommended when using Google Cloud?
⚠ Common exam trap
The GCDL exam often tests the misconception that GCP provides a built-in email sending service (like AWS SES) or that a self-managed SMTP server on Compute Engine is a viable solution, ignoring the critical importance of IP reputation and deliverability at scale.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Integrate a third-party email delivery service (e.g., SendGrid, Mailgun) with the GCP application.
Google Cloud does not provide a native transactional email service, so integrating a dedicated third-party email delivery service like SendGrid or Mailgun is the recommended approach. These services handle deliverability, reputation management, and compliance with email standards (e.g., SPF, DKIM, DMARC), which are critical for high-volume transactional and marketing emails. Using GCP's native services like Cloud Functions or App Engine to send emails directly would rely on SMTP relays that often have strict sending limits and poor deliverability.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use Gmail to manually send all transactional emails.
Why it's wrong here
Gmail is designed for interactive human communication via its web interface or a single-user IMAP/POP access, not for automated, application-generated transactional messages. It imposes strict per-day sending limits (e.g., 500 for free accounts and 2,000 for Google Workspace) and lacks the API features needed for managing bounces, templates, or bulk personalization. Manually sending each email via Gmail is also inherently unscalable and error-prone, making it unsuitable for any application at production scale.
- ✓
Integrate a third-party email delivery service (e.g., SendGrid, Mailgun) with the GCP application.
Why this is correct
Google Cloud does not provide a native outbound email-sending service, so to send transactional email programmatically you must integrate a dedicated email delivery provider like SendGrid or Mailgun. These third-party services offer mature HTTP APIs and SMTP endpoints designed for bulk and automated messaging, along with crucial features such as bounce handling, open/click tracking, and IP reputation management. They maintain pre-warmed IP pools and strict deliverability practices, which directly address the email reliability challenges that applications face.
- ✗
Use BigQuery to store and send emails directly to customers.
Why it's wrong here
BigQuery is a serverless, highly scalable data warehouse optimized for running analytical SQL queries over petabyte-scale datasets, not for sending communications. It has no outbound email capability—its only outputs are query results, exports to storage, or transfers to other data systems. The idea of using BigQuery to send emails conflates data storage and analysis with message delivery; sending email requires a separate delivery infrastructure built for that purpose.
- ✗
Deploy an SMTP server on Compute Engine and send emails directly from GCP IP addresses.
Why it's wrong here
While you can run your own SMTP server on Compute Engine, Google Cloud blocks outbound traffic on port 25 by default to prevent spam, so you would need to use a non-standard port or request a special exception, which is rarely granted. Even if you work around that, GCP's shared IP ranges are frequently blocklisted by major email providers, causing poor deliverability and requiring complex IP warming and feedback-loop management. Building and maintaining SMTP infrastructure this way is operationally heavy and technically inferior to using a managed email delivery service.
Quick reference
Cloud Service Model Comparison
| Model | You Manage | Provider Manages | Examples |
|---|---|---|---|
| IaaS | OS, runtime, apps, data | Hardware, hypervisor, networking | EC2, Azure VMs, GCP Compute Engine |
| PaaS | Apps and data | OS, runtime, middleware, hardware | Elastic Beanstalk, Azure App Service |
| SaaS | Data and settings only | Everything else | Microsoft 365, Salesforce, Workday |
| FaaS / Serverless | Function code only | Infra, scaling, runtime | Lambda, Azure Functions, Cloud Run |
| CaaS | Containers and apps | Kubernetes, OS, hardware | EKS, AKS, GKE |
Go deeper
Related to this question
Learn chapter
Cloud Digital Transformation
Key term
Service
A service is a software component or system that performs a specific function and is available to be used by other programs or users over a network.
Key term
DomainKeys Identified Mail
DomainKeys Identified Mail is an email authentication method that allows a domain to cryptographically sign its outgoing messages so receiving servers can verify the sender's domain is legitimate and the message was not tampered with.
About these practice questions
Courseiva writes every GCDL question from scratch — 829 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This GCDL practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the GCDL exam.