Term 151
Regex
Regex (regular expression) is a sequence of characters that defines a search pattern, used to match, find, or manipulate text in strings.
Acronym study
Terms 151–180 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 151
Regex (regular expression) is a sequence of characters that defines a search pattern, used to match, find, or manipulate text in strings.
Term 152
A checkpoint in Azure DevOps that requires manual or automated validation before a release can proceed to a specific environment.
Term 153
A Release pipeline is an automated sequence of steps that takes software from code commit to production deployment, ensuring quality and consistency.
Term 154
Reliability engineering is the practice of designing, testing, and maintaining systems to ensure they operate without failure for a specified period under stated conditions.
Term 155
A repository is a central storage location where software packages, code, or configuration files are kept, managed, and distributed for use by IT systems.
Term 156
A resource policy is a set of rules that controls who can access a specific cloud resource and what actions they can perform on it.
Term 157
A REST API is a set of rules that allows different software applications to communicate with each other over the internet using standard HTTP methods.
Term 158
RESTCONF is a protocol that uses HTTP methods to manage and configure network devices, replacing older command-line methods with a modern web-based approach.
Term 159
A retry policy is a set of rules that automatically re-attempts a failed operation after a defined interval, up to a maximum number of tries.
Term 160
A rolling deployment is a software release strategy that gradually replaces old application instances with new ones across a cluster of servers, one at a time or in small batches, to ensure zero downtime and continuous service availability.
Term 161
SAM stands for Source Account Mapping, a process in CI/CD and monitoring that links source code changes to specific user accounts for tracking and security.
Term 162
Static Application Security Testing is a white-box method of analyzing source code, bytecode, or compiled binaries for security vulnerabilities without executing the program.
Term 163
An SBOM is a formal, machine-readable inventory of all software components and dependencies used in a software application or system.
Term 164
SCA (Software Composition Analysis) is a security testing method that automatically identifies open-source components, libraries, and dependencies in software to find known vulnerabilities and license compliance issues.
Term 165
Software-Defined Networking (SDN) is an approach to network management that separates the control plane (decision-making) from the data plane (traffic forwarding), allowing centralized, programmable network control.
Term 166
Secrets management is the practice of securely storing, controlling access to, and regularly rotating sensitive credentials like passwords, API keys, and certificates used by applications and services.
Term 167
AWS Secrets Manager is a fully managed service that helps you protect access to your applications, services, and IT resources by securely storing, rotating, and controlling access to secrets like database passwords, API keys, and credentials.
Term 168
A secure file is a protected file stored in Azure DevOps that holds sensitive information like certificates or signing keys, accessible only to authorized pipelines and users.
Term 169
sed is a stream editor used in Unix and Linux to perform basic text transformations on an input stream, such as finding and replacing text, deleting lines, or inserting content.
Term 170
A self-hosted agent is a software component that you install and manage on your own infrastructure to run automated tasks for a CI/CD or DevOps platform.
Term 171
A service connection in Azure DevOps is a secure, configurable link that allows your pipelines to authenticate and interact with external services like Azure, GitHub, or on-premises servers.
Term 172
A service principal is an identity created for an application or automated tool to access cloud resources securely without using a human user account.
Term 173
Shift left security is the practice of integrating security testing and controls earlier in the software development lifecycle, rather than waiting until after deployment.
Term 174
A Service Level Agreement (SLA) is a contract between a service provider and a customer that defines the level of service expected, including metrics like uptime, response time, and penalties for non-compliance.
Term 175
An SLI (Service Level Indicator) is a carefully chosen metric that measures one specific aspect of a service's performance, such as request latency or error rate, to help determine whether the service is meeting its reliability goals.
Term 176
A Service Level Objective is a measurable target for a specific aspect of a service's performance or reliability that a team commits to meeting over a defined period.
Term 177
Sort is the process of arranging data in a specified order, typically alphabetically or numerically, to make it easier to search, analyze, or display.
Term 178
A southbound API is an interface that allows a network controller or orchestrator to communicate with and manage the physical or virtual network devices beneath it, like switches, routers, and firewalls.
Term 179
A Sprint is a time-boxed iteration in Agile project management, typically 2–4 weeks long, during which a development team completes a set of planned work items.
Term 180
A stage is a discrete phase in a software development or deployment pipeline where code is built, tested, integrated, or released in a controlled environment.