Study guide
1.5 Evolving Cloud Technologies: AI/ML Services, IoT & Edge Computing
CompTIA Cloud+ Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Cloud Architecture Fundamentals
1.1 Cloud Service Models & Shared Responsibility 1.2 Cloud Deployment Models & Multi-Cloud Strategies 1.3 High Availability, Resiliency & Redundancy 1.4 Disaster Recovery & Business Continuity 1.5 Evolving Cloud Technologies: AI/ML Services, IoT & Edge Computing
2 Chapter 2: Cloud Compute & Storage Architecture
2.1 Virtualization & Hypervisor Architectures 2.2 Containerization & Microservices Architecture 2.3 Container Orchestration & Kubernetes Architecture 2.4 Cloud Storage Architectures & Performance
3 Chapter 3: Cloud Networking Architecture
3.1 Virtual Private Clouds & Subnetting Architecture 3.2 Hybrid & Multi-Cloud Connectivity 3.3 DNS, Load Balancing & Traffic Routing 3.4 Cloud Network Security Architecture
4 Chapter 4: Workload Assessment & Migration Planning
4.1 Cloud Migration Strategies (The 6/7 Rs) 4.2 Pre-Migration Workload Assessment & Sizing 4.3 Data & Database Migration Methods 4.4 Migration Execution, Cutover & Post-Migration Validation
5 Chapter 5: Infrastructure as Code & Provisioning
5.1 Infrastructure as Code Fundamentals & State Management 5.2 IaC Tooling & Template Authoring 5.3 Provisioning Automation & Image Management 5.4 Deployment Strategies & Release Patterns
6 Chapter 6: Cloud Operations & Lifecycle Management
6.1 Resource Lifecycle & Patch Management 6.2 Cloud Scaling Strategies & Elasticity 6.3 Cloud Cost Management & Optimization (FinOps) 6.4 Capacity Planning & Service Quotas
7 Chapter 7: Cloud Backup, Recovery & Business Continuity Operations
7.1 Backup Strategies, Storage Media & Retention Policies 7.2 Immutable Backups, Vault Locking & Ransomware Defense 7.3 Point-in-Time Recovery & Data Integrity Validation 7.4 High Availability Failover Drills & Chaos Engineering
8 Chapter 8: Cloud Security Controls & Identity and Access Management
8.1 Identity & Access Management, RBAC & ABAC 8.2 Identity Federation, SSO & Directory Integration 8.3 Multi-Factor Authentication, PAM & Machine Identities 8.4 Secrets Management & Cryptographic Credential Hygiene
9 Chapter 9: Data Protection, Vulnerability & Compliance
9.1 Data Encryption, Key Management & Confidential Computing 9.2 Vulnerability Management, Posture Assessment & CWPP 9.3 Container, Workload & Runtime Security 9.4 Cloud Compliance Frameworks & Governance Auditing
10 Chapter 10: DevOps Fundamentals & CI/CD Pipelines
10.1 Version Control Systems & Branching Strategies 10.2 Continuous Integration & Automated Testing Pipelines 10.3 Continuous Delivery, Deployment Automation & GitOps 10.4 Configuration Management & Systems Integration
11 Chapter 11: Cloud Observability & Monitoring
11.1 The Three Pillars of Observability: Metrics, Logs & Traces 11.2 Cloud Monitoring Architecture, Alerting & SLOs 11.3 Centralized Log Aggregation, SIEM & Log Analytics
12 Chapter 12: Troubleshooting Cloud Architecture & Deployments
12.1 Structured Cloud Troubleshooting Methodology 12.2 Troubleshooting Compute, Container & Storage Failures 12.3 Troubleshooting Provisioning, IaC & Automation Failures
13 Chapter 13: Troubleshooting Cloud Networking & Security
13.1 Troubleshooting Cloud Network Connectivity & Routing 13.2 Troubleshooting IAM, Permissions & Encryption 13.3 Troubleshooting Disaster Recovery & Performance Degradation
1.5 Evolving Cloud Technologies: AI/ML Services, IoT & Edge Computing
Key Takeaways Explain This Topic AI
Major cloud providers expose artificial intelligence as fully managed API services — OCR text recognition, language translation, visual recognition, sentiment analysis, speech-to-text, text-to-speech, and generative AI — so applications gain machine-learning capability without training custom models.
The core AWS AI services map one-to-one to common exam tasks: Textract (OCR), Translate (translation), Rekognition (visual recognition), Comprehend (sentiment analysis), Transcribe (speech-to-text), Polly (text-to-speech), and Bedrock (generative AI).
An IoT solution chains sensors and actuators through edge gateways into cloud ingestion platforms such as AWS IoT Core or Azure IoT Hub, using lightweight transmission protocols such as MQTT (publish/subscribe over TLS) and CoAP.
MQTT is the default IoT telemetry protocol for constrained devices on unreliable networks: a broker mediates publish/subscribe traffic, and edge gateways provide certificate management plus store-and-forward buffering during connectivity outages.
Edge computing executes workloads physically close to the data source — carrier-embedded zones (AWS Wavelength), metro Local Zones, or on-premises edge hardware (Outposts, Azure Stack) — cutting round-trip latency and backhaul bandwidth while remaining centrally managed from the cloud.
Last updated: August 2026
Evolving Cloud Technologies: AI/ML Services, IoT & Edge Computing
Objective 1.11 of the Cloud+ (CV0-004) blueprint requires candidates to identify evolving technologies built on cloud platforms — not to operate them. The exam tests whether you can match a business requirement (transcribe a support call, read a scanned invoice, stream factory telemetry) to the correct managed service category or architecture. Edge computing also appears under Objective 1.2 (service availability), because edge locations push cloud services physically closer to end users and devices.
1. Cloud-Managed AI & Machine Learning Services
Every hyperscaler delivers machine learning as consumption-based APIs. Instead of collecting and labeling training data and operating GPU clusters, an application simply calls a pre-trained inference endpoint and pays per request.
Business Task AWS Service Microsoft Azure Service Google Cloud Service
Text recognition (OCR) — extract printed/handwritten characters from scans Amazon Textract Azure AI Document Intelligence Document AI / Vision AI
Text translation — convert documents between languages Amazon Translate Azure AI Translator Cloud Translation
Visual recognition — detect objects, faces, and unsafe content in images/video Amazon Rekognition Azure AI Vision Vision AI / Video AI
Sentiment analysis — classify text tone (positive/negative/neutral) Amazon Comprehend Azure AI Language Natural Language AI
- Voice-to-text (speech recognition / transcription) Amazon Transcribe Azure AI Speech to Text Speech-to-Text
- Text-to-voice (speech synthesis) Amazon Polly Azure AI Text to Speech Text-to-Speech
Generative AI — large language model chat, summarization, code Amazon Bedrock Azure OpenAI Service Vertex AI (Gemini)
Key Concepts Behind the Services
Inference vs. training: The services above perform inference — applying a model the provider already trained. Building a custom model on proprietary data belongs to the training platforms ( Amazon SageMaker, Azure Machine Learning, Vertex AI ), which require labeled datasets and GPU capacity provisioning.
Generative AI: Foundation-model platforms (Bedrock, Azure OpenAI, Vertex AI) bill per token and raise distinct governance questions: prompts may contain PII, outputs require grounding techniques such as Retrieval-Augmented Generation (RAG) against enterprise data, and many organizations route access through a private API gateway with content filters.
Exam association table: read text from scanned receipts → OCR (Textract); decide whether product reviews are angry → sentiment analysis (Comprehend); a contact-center IVR speaks the account balance → text-to-speech (Polly); transcribe recorded support calls → speech-to-text (Transcribe); a chatbot that drafts answers → generative AI (Bedrock).
Important
Exam Trap: "Extract printed tracking numbers from two million scanned shipping labels" is an OCR / text-recognition requirement. Do not choose visual object detection (which identifies things in a picture, not characters) or generative AI (which composes new text rather than reading it).
2. Internet of Things (IoT) Cloud Architecture
An IoT estate moves telemetry through four layers, each of which the exam expects you to identify: +---------------------------------------------------------------------------------------------+
- | FOUR-LAYER IOT CLOUD ARCHITECTURE |
- | |
- | [ 1. SENSORS + ACTUATORS ] [ 2. EDGE GATEWAY ] [ 3. INGESTION BROKER ] |
- | - Measure temperature, GPS, - Protocol translation - Authenticates fleets of |
- | vibration, flow; actuators - X.509 device certs - devices |
- | drive valves, relays, locks - Store-and-forward - AWS IoT Core (device |
- | - Battery-powered, constrained buffering during WAN - shadows + rules engine) |
- | compute/memory outages; local filter - Azure IoT Hub (device |
- | and pre-aggregation twins) |
- | | | | |
- | +---- MQTT / CoAP / LPWAN --->+---- MQTT over TLS (8883) ----+ |
- | |
- | [ 4. CLOUD PROCESSING ] |
- | - Streaming analytics, dashboards, ML inference, |
- | long-term data-lake storage |
- +---------------------------------------------------------------------------------------------+
- Communication & Transmission Protocols
MQTT (Message Queuing Telemetry Transport): The default IoT protocol. A lightweight publish/subscribe design over TCP with TLS (port 8883 ) in which devices publish to topics on a central broker; Quality-of-Service levels offer QoS 0 (fire-and-forget), QoS 1 (at-least-once delivery), and QoS 2 (exactly-once). Ideal for low-power devices on unreliable links.
CoAP (Constrained Application Protocol): A UDP-based, REST-like protocol for severely constrained devices that cannot afford TCP overhead.
HTTP(S): Acceptable for mains-powered devices with generous bandwidth, but its per-request overhead is heavy for battery telemetry.
Edge radio links: LPWAN options ( LoRaWAN, NB-IoT ) carry long-range, low-bitrate sensor traffic; BLE and Zigbee serve short-range personal-area networks that hand off to a gateway.
Note
Exam associations: unreliable backhaul + minimal power draw → MQTT ; the cloud component that authenticates devices and brokers their messages is the IoT platform (AWS IoT Core / Azure IoT Hub); when connectivity drops, the edge gateway buffers telemetry (store-and-forward) and synchronizes on reconnection.
3. Edge Computing Architecture
Edge computing executes workloads physically close to the data source rather than in a distant cloud region:
Why edge: round-trip latency (carrier-embedded compute can reach single-digit milliseconds versus 50–150 ms to a remote region), backhaul bandwidth (process factory video locally and ship only anomalies), intermittent connectivity, and data-sovereignty constraints that keep raw data on premises.
The edge spectrum:
CDN points of presence (PoPs): CloudFront, Azure Front Door, and Cloudflare cache static assets and run lightweight edge functions near users.
Provider edge compute: AWS Wavelength embeds compute inside carrier 5G networks; AWS Local Zones and Azure Extended Zones place compute in metro areas.
On-premises edge hardware: AWS Outposts racks, Azure Stack Hub/Edge , and Google Distributed Cloud run provider-native services inside the customer's facility.
Availability relationship (Objective 1.2): Edge PoPs raise service availability for regional users, and local edge processing lets sites keep operating — running control loops and buffering data store-and-forward — while the WAN link is down.
Management model: Edge nodes are centrally orchestrated from the cloud but tolerate disconnection. Over-the-air software updates roll out in deployment rings with automatic rollback on health-check failure.
Caution
Exam Trap: "Users in one metro area need sub-10 ms latency for an augmented-reality application" points to Local Zones or carrier-edge (Wavelength) compute — not simply choosing a different full cloud region. "The plant must keep running when disconnected from the internet" points to an IoT edge gateway with local compute and store-and-forward buffering .
4. Exam-Ready Distinctions
- Scenario Requirement Correct Technology Family
- Read printed text from scanned invoices Managed OCR / text recognition (Textract, Document AI)
- Translate documentation into 12 languages Managed translation API
- Detect defective parts in assembly-line photos Visual recognition
- Flag enraged customer emails for escalation Sentiment analysis
Thousands of battery sensors on flaky rural links MQTT into an IoT ingestion platform through a buffering edge gateway
- Sub-10 ms latency for a stadium app Carrier-edge / Local Zone compute
- Continue plant control during WAN outage On-premises edge hardware with local processing