Term 121
KMS encryption
KMS encryption is a managed service that creates, stores, and controls cryptographic keys used to encrypt data in the cloud.
Acronym study
Terms 121–150 of 206 AZ-400 acronyms and key terms. Each entry includes a plain-English definition and a link to the full 800-word glossary page with exam context and practice questions.
Term 121
KMS encryption is a managed service that creates, stores, and controls cryptographic keys used to encrypt data in the cloud.
Term 122
Kusto Query Language is a powerful read-only query language used to explore, analyze, and visualize large datasets, most notably in Azure Data Explorer and Microsoft Sentinel.
Term 123
Key-value pairs that AWS Lambda makes available to your function code at runtime, used to pass configuration settings like database URLs or feature flags without hardcoding them.
Term 124
A Lambda function is a piece of code that runs in the cloud without you having to manage any servers, and it only runs when you tell it to, saving you money and effort.
Term 125
A Lambda handler is the specific function in your code that AWS Lambda invokes to start processing an event, acting as the main entry point for your serverless application.
Term 126
A Lambda layer is a ZIP archive that contains libraries, custom runtimes, or other dependencies that you can use with your AWS Lambda functions.
Term 127
Lambda memory is the amount of RAM allocated to an AWS Lambda function, which also determines its CPU power and network throughput.
Term 128
Lambda timeout is the maximum amount of time a serverless function is allowed to run before it is forcibly terminated by the cloud provider.
Term 129
Least privilege is a security principle that means giving users, systems, or programs only the minimum permissions they need to do their job and nothing more.
Term 130
In Azure DevOps, a Library is a central repository for managing reusable content like variable groups and secure files that can be shared across multiple pipelines.
Term 131
Log Analytics is a cloud-based service that collects, analyzes, and visualizes machine-generated log data from various sources to help IT teams monitor systems and troubleshoot issues.
Term 132
A loop is a programming construct that repeats a block of code multiple times until a certain condition is met or until all items in a collection have been processed.
Term 133
A managed identity is an automatically managed service principal in Azure that allows your code to authenticate to any service that supports Azure AD authentication without storing credentials.
Term 134
A mapping template is a reusable blueprint that defines how data fields from one system or format are transformed and transferred to another, ensuring consistency in data integration tasks.
Term 135
A merge conflict is a situation that occurs when version control software cannot automatically reconcile conflicting changes made to the same part of a file by different contributors.
Term 136
A metric is a quantifiable measurement used to assess the performance, health, or status of IT systems, networks, or applications.
Term 137
A Microsoft-hosted agent is a virtual machine provided by Microsoft Azure DevOps that runs your build or release jobs without you having to manage or maintain the underlying infrastructure.
Term 138
NETCONF is a network management protocol that allows administrators to configure, retrieve, and delete settings on network devices using a structured, machine-readable data format.
Term 139
A northbound API is an interface that allows higher-level software components, such as network management or orchestration platforms, to communicate with and control lower-level network devices like switches and routers.
Term 140
OIDC federation is a method that lets users log into multiple applications or services using a single identity from a trusted provider, based on the OpenID Connect protocol.
Term 141
Parameter Store is a secure, centralized service for storing and managing configuration data, secrets, and environment variables used by applications and IT infrastructure.
Term 142
A pipeline is an automated series of steps that takes code from development to production, ensuring quality and speed.
Term 143
A pipeline artifact is a file or collection of files produced during a CI/CD pipeline stage that is stored and used by subsequent stages or for deployment.
Term 144
A pipe is a mechanism that connects the output of one command directly to the input of another command, allowing data to flow between processes in a chain.
Term 145
Policy as code is the practice of representing and managing security, compliance, and governance rules as executable code, enabling automated validation and enforcement across infrastructure and software development workflows.
Term 146
A postmortem is a structured review of an incident to identify what went wrong, what went well, and how to prevent future issues.
Term 147
Provisioned concurrency is a feature in serverless computing that keeps a specified number of function instances initialized and ready to respond immediately, eliminating cold start delays.
Term 148
A pull request is a way for a developer to propose changes to a codebase and ask other team members to review and merge them into the main project.
Term 149
A query is a request for information from a database, asking a specific question to retrieve, update, or manipulate data.
Term 150
Redirection is a mechanism that sends output or input from a command or program to a different destination, such as a file, another command, or a device, instead of the default screen or keyboard.