Term 181
Standard workflow
A standard workflow is a repeatable, predefined sequence of steps for completing a common IT task, ensuring consistency and efficiency.
Acronym study
Terms 181–206 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 181
A standard workflow is a repeatable, predefined sequence of steps for completing a common IT task, ensuring consistency and efficiency.
Term 182
A state machine is a computational model that defines a finite number of states, transitions between those states based on inputs, and actions that occur as a result.
Term 183
AWS Step Functions is a serverless orchestration service that lets you coordinate multiple AWS services into a visual, state-machine-based workflow.
Term 184
Structured logging is the practice of recording log data in a consistent, machine-readable format, such as JSON, so that it can be easily searched, filtered, and analyzed by automated tools.
Term 185
A unified cloud-based service that lets IT administrators centrally manage the configuration, patching, and health of a fleet of servers and virtual machines.
Term 186
A Task in Azure DevOps is a predefined, reusable step that performs a specific action during a build or release pipeline, like compiling code or running tests.
Term 187
Task state refers to the current condition of a process or thread within an operating system, indicating whether it is running, ready to run, waiting, or terminated.
Term 188
Telemetry is the automatic collection, transmission, and measurement of data from remote sources to a central system for analysis and monitoring.
Term 189
Terraform is an infrastructure-as-code tool that lets you define and manage your IT infrastructure using configuration files instead of manual processes.
Term 190
Threat modelling is a structured approach to identifying, evaluating, and documenting potential security threats to a system so that defenses can be built proactively.
Term 191
A trace is a record of the path and timing of a request or operation as it moves through components in a system, used to monitor performance and troubleshoot issues.
Term 192
Trunk-based development is a version control practice where developers integrate small changes frequently into a single main branch, called the trunk, to avoid merge conflicts and enable continuous delivery.
Term 193
A Trusted Advisor is an IT professional who earns deep client trust through expert guidance, ethical behavior, and a focus on the client’s long-term success rather than just selling products.
Term 194
uniq is a Unix/Linux command that filters out adjacent duplicate lines from a sorted or unsorted text file or input stream, reporting only unique occurrences.
Term 195
A usage plan is a set of throttling and quota rules that govern how clients can access an API, controlling request rates and access limits per user or application.
Term 196
A user story is a short, simple description of a feature told from the perspective of the end user, used in agile software development to guide work.
Term 197
A variable group is a reusable collection of key-value pairs in Azure DevOps that can store configuration settings and secrets, shared across multiple pipelines.
Term 198
A variable is a named storage location in a computer program that holds a value which can change during execution.
Term 199
A WebSocket API is a programming interface that enables real-time, two-way communication between a client (like a web browser) and a server over a single, persistent TCP connection.
Term 200
A work item is a digital record in Azure DevOps that tracks a single unit of work, such as a task, bug, or user story, helping teams manage and monitor their progress.
Term 201
X-Ray is a data analysis and visualization tool used in cloud and distributed systems to trace and debug requests as they travel through an application's components.
Term 202
X-Ray tracing is a monitoring technique used in cloud applications to trace requests as they travel through different services, helping identify performance bottlenecks and errors.
Term 203
xargs is a command-line utility that reads input from standard input and converts it into arguments for another command.
Term 204
XML is a flexible text format used to store and transport data in a way that both humans and computers can read, using custom tags to describe the data's structure.
Term 205
A YAML pipeline is a text-based file written in YAML format that defines an automated series of steps for building, testing, and deploying software in a continuous integration and continuous delivery (CI/CD) system.
Term 206
YANG is a data modeling language used to define the structure and constraints of data exchanged between network devices and management applications.