Term 91
DevSecOps
DevSecOps is a software development practice that integrates security into every phase of the DevOps lifecycle, making security a shared responsibility from the start.
Acronym study
Terms 91–120 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 91
DevSecOps is a software development practice that integrates security into every phase of the DevOps lifecycle, making security a shared responsibility from the start.
Term 92
Distributed tracing is a method used to track and observe requests as they flow through multiple services in a distributed system, helping identify performance bottlenecks and failures.
Term 93
An environment is a dedicated set of computing resources, configurations, and services used to develop, test, or host software applications in a controlled and repeatable way.
Term 94
An Epic is a large, high-level work item in Azure DevOps that represents a significant body of work, typically broken down into smaller features and user stories for agile project management.
Term 95
An error budget is the maximum amount of acceptable downtime or failure a system can experience within a specified period while still meeting its Service Level Objective (SLO).
Term 96
Error Reporting is the automated process of capturing, logging, and notifying relevant systems or personnel about errors that occur in software, hardware, or network components to facilitate diagnosis and resolution.
Term 97
An execution role is a set of permissions assigned to a service or resource that defines what actions it can perform on other AWS or cloud resources on your behalf.
Term 98
An exit code (or return code) is a numeric value that a program or script sends back to the operating system after it finishes running, signaling whether it succeeded or failed.
Term 99
An Express workflow is a sequence of automated steps in a server-side web application, typically built with the Express.js framework, that handles requests and responses efficiently.
Term 100
A feature is a distinct unit of functionality that delivers value to the user, often managed and tracked throughout the software development lifecycle.
Term 101
A feature flag is a software development technique that allows developers to turn features on or off without deploying new code, enabling safer releases and testing.
Term 102
Feature telemetry is the automatic collection and transmission of usage data about specific software features to help organizations understand how those features are being used, identify issues, and improve performance.
Term 103
A feedback loop is a process where the output of a system is returned as input to guide and adjust future behavior, helping maintain stability or improve performance.
Term 104
The find command in Unix/Linux is a powerful utility for searching files and directories based on a wide range of criteria such as name, size, type, permissions, and modification time.
Term 105
A function is a reusable block of code that performs a specific task, taking inputs, processing them, and returning a result, helping to organize and automate IT workflows.
Term 106
Git is a version control system that tracks changes to files so multiple people can work on the same project without overwriting each other's work.
Term 107
Gitflow is a branching model for Git that defines a structured set of branch types and workflows to manage feature development, releases, and hotfixes in software projects.
Term 108
GitHub is a cloud-based platform for storing, tracking, and collaborating on code using Git version control.
Term 109
GitHub Advanced Security is a suite of security tools integrated into GitHub that helps developers find and fix vulnerabilities, secrets, and code quality issues directly in their repositories.
Term 110
grep is a command-line tool that searches through text for lines matching a pattern, used by IT professionals to quickly find information in files or command output.
Term 111
A here document is a scripting feature that allows you to embed a block of text or code directly inside a script without needing to use multiple echo or print statements, and it can include variables and special characters.
Term 112
An HTTP API is a set of rules and tools that allows computer programs to communicate with each other over the internet using the Hypertext Transfer Protocol.
Term 113
Infrastructure as Code (IaC) manages and provisions IT infrastructure through machine-readable definition files, rather than manual hardware configuration.
Term 114
An IAM role is a set of permissions that an entity can assume temporarily to access cloud resources securely.
Term 115
Idempotency means that an operation can be performed multiple times without changing the result beyond the first application.
Term 116
An incident is a security event that violates an organization's policies or threatens its data, systems, or operations, requiring a structured response.
Term 117
Infrastructure as code (IaC) is the practice of managing and provisioning IT infrastructure through machine-readable definition files, rather than through physical hardware configuration or interactive configuration tools.
Term 118
Intent-based networking is an approach to network management where you tell the network what you want it to do (the intent), and the network automatically configures itself to achieve that goal.
Term 119
JSON is a lightweight, text-based format for storing and exchanging data that is easy for humans to read and write and easy for machines to parse and generate.
Term 120
Kinesis is a managed service for real-time data streaming, processing, and analysis at scale.