Glossary · IT & Cloud

AZ-204 Glossary: Key Azure Developer Terms

advanced

A free AZ-204 glossary defining the key Azure developer terms - Functions, App Service, Cosmos DB, Key Vault, Managed Identities and more - in plain English.

By The Exam Atlas Editorial Team · Verified 2026-06-05

Key AZ-204 terms in plain English. Knowing what each service is for - and when to choose it over a similar one - is exactly what the exam tests.

TermDefinition
Azure FunctionsA serverless, event-driven compute service that runs small pieces of code (triggered by HTTP, timers, queues and more) without managing servers.
TriggerThe event that starts an Azure Function, such as an HTTP request, a timer, or a new message on a queue.
BindingA declarative connection between a Function and a service, used to pass data in or out without writing connection code.
App ServiceA managed platform for hosting web apps and APIs, with features like deployment slots for staged releases.
Deployment slotA live staging environment in App Service that lets you deploy and test, then swap into production with no downtime.
Container AppsA serverless container service for running microservices and containerised apps without managing the underlying cluster.
Azure Container InstancesA service for running a single container quickly without orchestration; useful for simple or short-lived workloads.
Cosmos DBA globally distributed, multi-model NoSQL database with tunable consistency and low-latency access.
Consistency levelA Cosmos DB setting that trades off data freshness against latency and availability, from strong to eventual.
Partition keyThe property Cosmos DB uses to distribute data across partitions; choosing it well is key to performance and scale.
Blob storageAzure object storage for unstructured data such as files, images and backups, organised into containers.
Access tierA Blob storage setting (hot, cool, archive) that trades storage cost against access cost and retrieval time.
SAS tokenA Shared Access Signature: a time-limited, scoped token granting access to a storage resource without sharing the account key.
Microsoft EntraAzure’s identity service (formerly Azure Active Directory) used to authenticate users and applications.
Access tokenA credential issued after authentication that an app presents to access a protected API or resource.
Key VaultAn Azure service for securely storing and accessing secrets, keys and certificates.
Managed IdentityAn identity managed by Azure that lets a resource authenticate to other services without storing credentials in code.
API ManagementA service to publish, secure, throttle and monitor APIs behind a single gateway.
Event GridA service for routing discrete events (such as a file uploaded) to handlers in an event-driven architecture.
Event HubsA high-throughput service for ingesting large streams of telemetry or event data.
Service BusAn enterprise messaging service with queues and topics for reliably decoupling components.
Queue StorageA simple, durable message queue for decoupling parts of an application.
Application InsightsAn Azure Monitor feature that collects telemetry to monitor app performance and diagnose problems.
Azure Cache for RedisAn in-memory cache used to speed up applications by storing frequently accessed data.
CDNA Content Delivery Network that caches content at edge locations to reduce latency for users.

FAQ

What is a Managed Identity in Azure?
A Managed Identity lets an Azure resource authenticate to other services without storing credentials in code. Azure handles the identity, so apps can reach Key Vault or storage securely.

Sources