Cloud Digital Leader Practice Question: Google Cloud products, services, and solutions
A company is building a new application that needs to send transactional emails (order confirmations, password resets, account notifications) to customers. Google Cloud does not provide a native SMTP email service. Which approach is standard for sending transactional emails from Google Cloud applications?
⚠ Common exam trap
Many candidates assume Google Cloud provides a native SMTP service (like AWS SES) or that Gmail SMTP can be repurposed for application use, but Google Cloud explicitly lacks this service, and Gmail's SMTP is restricted to personal use and low-volume sending.
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
✓
Integrating a third-party transactional email service (such as SendGrid, Mailgun, or Postmark) via API from the Cloud Run or Cloud Functions application
Google Cloud does not offer a native SMTP service for sending transactional emails. The standard approach is to integrate a third-party transactional email service (e.g., SendGrid, Mailgun, Postmark) via API from serverless compute services like Cloud Run or Cloud Functions. These services handle deliverability, reputation, and compliance with email standards (SPF, DKIM, DMARC) that are critical for transactional email.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Using Cloud Storage to store email templates and delivering them directly to customers' inboxes
Why it's wrong here
Cloud Storage is an object storage service for storing immutable files such as images, archives, or email templates; it has no built-in email delivery mechanism and cannot connect to recipient mail servers. To send an email, you need an SMTP server or a third-party email API that performs DNS lookups, handles MX records, manages bounces, and maintains delivery reputation. Placing templates in a bucket merely stores them as bytes; there is no agent within Cloud Storage that can interpret those templates and transmit them over SMTP to a recipient's inbox.
- ✓
Integrating a third-party transactional email service (such as SendGrid, Mailgun, or Postmark) via API from the Cloud Run or Cloud Functions application
Why this is correct
This is the standard pattern. Applications hosted on Cloud Run or Cloud Functions call third-party email service APIs to send transactional emails. These services provide the SMTP infrastructure, deliverability management, and analytics that transactional email requires.
- ✗
Running a self-managed SMTP server on a Compute Engine VM and configuring MX records to deliver email
Why it's wrong here
Running a self-managed SMTP server on a cloud VM is technically possible but problematic: cloud provider IPs are frequently blocklisted by spam filters, deliverability management is complex, and it doesn't scale easily. Third-party email services exist precisely to solve these problems.
- ✗
Using Gmail directly by authenticating the application with a corporate Gmail account and sending through Gmail SMTP
Why it's wrong here
Gmail's SMTP gateway is designed for individual user email, enforcing a strict sending limit of roughly 500 messages per day per account. This quota is far below the volume required for production transactional email, and exceeding it triggers temporary lockouts or permanent account suspension. Additionally, Gmail servers send from shared IP address pools that are often blocklisted by receiving servers when used for application-generated mail, leading to poor deliverability. Authenticating your application with a corporate Gmail account also violates Google's Terms of Service when used for bulk or automated sending, making this approach both unreliable and non-compliant.
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
Google Cloud
Google Cloud is a suite of cloud computing services offered by Google that provides infrastructure, platform, and software solutions over the internet.
About these practice questions
One of 829 original GCDL practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.