Azure AZ-400 flashcards
Azure AZ-400 · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Area path
- An Azure Boards field that groups work items by team, product, or component; it determines which team owns the item and supports filtering and reporting.
- Iteration path
- An Azure Boards field that assigns work items to a sprint or time box; it drives sprint backlogs, capacity planning, and burndown charts.
- Service hook
- An Azure DevOps feature that sends event notifications to external services such as Teams, Slack, or webhooks when work items, builds, or pull requests change.
- Delivery Plans
- An Azure DevOps view that shows work items from multiple teams across iterations, helping stakeholders spot dependencies, gaps, and schedule conflicts.
- Inherited process
- An Azure DevOps customization model that lets a project collection derive a process from Agile, Scrum, Basic, or CMMI and then add fields, rules, and states.
- Work item linking
- Connecting Azure Boards items to commits, pull requests, and builds using AB# identifiers or mention syntax so traceability appears on the work item.
- Team capacity
- The per-sprint availability configured in Azure Boards for each team member, used to compare planned work against available hours or story points.
- Branch policy
- A rule on an Azure Repos branch that enforces requirements such as minimum reviewers, linked work items, comment resolution, or successful build validation before merge.
- Squash merge
- A pull request completion option that combines all branch commits into one new commit on the target branch, producing a linear history without merge commits.
- Rebase and fast-forward
- A pull request merge option that replays source commits onto the target tip and advances the target ref without a merge commit, preserving individual commits.
- Git LFS
- Git Large File Storage replaces large binary files in a repository with small pointer files while storing the actual content in a separate LFS endpoint.
- Trunk-based development
- A branching model where developers commit small changes frequently to a shared main branch and use short-lived feature branches, reducing merge conflicts and integration risk.
- Required reviewer policy
- An Azure Repos branch policy that automatically adds specific users or groups as reviewers when a pull request touches configured folders or files.
- Protected tag
- A Git tag rule that restricts who can create or delete matching tags, commonly used to safeguard release version labels.
- Deployment job
- An Azure Pipelines job that targets an environment and applies a deployment strategy such as runOnce, rolling, or canary while supporting approvals and gates.
- Pipeline template
- A reusable YAML file that defines stages, jobs, or steps and is included or extended by other pipelines to enforce consistency and reduce duplication.
- Variable group
- A shared collection of variables in Azure DevOps that can be linked to Azure Key Vault and authorized for use by selected pipelines.
- Pipeline artifact
- A file produced by a pipeline run and stored with that run, used to pass build outputs between stages or jobs.
- Environment check
- A condition configured on an Azure Pipelines environment, such as approval, branch control, business hours, or invocation of an Azure Function.
- Canary deployment
- A release strategy that routes a small percentage of traffic to a new version, monitors health metrics, and gradually increases traffic or rolls back.
- Workload identity federation
- An Azure Pipelines service connection authentication method that exchanges a pipeline token for short-lived Microsoft Entra credentials, avoiding stored client secrets.
- Secret scanning
- A security control that detects credentials and other sensitive strings in repository commits or pull requests and can block pushes when push protection is enabled.
- Key Vault variable group
- An Azure DevOps variable group linked to Azure Key Vault so pipeline secrets are fetched at runtime and not stored directly in Azure DevOps.
- Audit log
- An Azure DevOps record of organization-level events such as permission changes, policy edits, and access, often streamed to a SIEM for retention.
- Least privilege
- A security principle that grants identities and pipeline service connections only the permissions required for their tasks, reducing blast radius if compromised.
- Software composition analysis
- A security practice that inventories open-source dependencies and flags known vulnerabilities and license issues, often integrated as a pipeline scanning task.
- Application Insights
- An Azure Monitor feature that collects application telemetry such as requests, dependencies, exceptions, traces, and metrics for performance and failure analysis.
- Sampling
- An Application Insights feature that reduces telemetry volume by keeping a representative subset of items while preserving correlated traces and estimated metric counts.
- Availability test
- A synthetic monitor that sends requests to an endpoint from multiple locations, verifying uptime and alerting when response time or success rate degrades.
- KQL
- Kusto Query Language, used in Azure Monitor Log Analytics and Application Insights to filter, summarize, and visualize telemetry stored in tables.
- Distributed tracing
- Tracking a request across services by propagating a correlation identifier, allowing end-to-end latency and dependency failures to be reconstructed in telemetry.
- Release annotation
- A marker sent to Application Insights when a deployment occurs, letting teams correlate telemetry changes and failures with released application versions.