Bash, the Crucial Exams Chat Bot
AI Bot
Implementing Continuous Integration Flashcards
Microsoft DevOps Engineer Expert AZ-400 Flashcards
| Front | Back |
| Benefit of integrating Git repositories in a CI pipeline | Automatic fetching of the latest code for building and testing |
| Best practice for naming pipelines | Use descriptive names that reflect the pipeline's purpose, such as "Build-Frontend-App" or "Test-Backend-API" |
| Command to add a Git remote repository | git remote add [name] [repository URL] |
| Command to fetch the latest changes from a Git repository | git pull |
| Command to run a build pipeline in Azure DevOps | Triggered by committing code to the repository or manually initiating |
| Common build validation methods in CI | Code coverage, linting, and running unit tests |
| Core components of a YAML pipeline in Azure DevOps | Trigger, stages, jobs, steps |
| How can you ensure a pipeline runs on a specific agent pool | Specify the agent pool name within the 'pool' section of the pipeline YAML |
| How do you secure sensitive data in a build pipeline | Use Azure DevOps secrets and environment variables |
| How to enable parallel jobs in a build pipeline | Define multiple jobs in the 'stages' section and mark them for parallel execution |
| How to link a GitHub repository to Azure Pipelines | Use the "GitHub" option when setting up a new pipeline and authenticate with your GitHub account |
| How to set up a new pipeline in Azure DevOps | Navigate to the Pipelines section and use the "New Pipeline" option to configure a new build or release process |
| How to specify the branch for a pipeline in YAML | Use the 'trigger' section and define the branches to monitor |
| How to store reusable code or templates in Azure Pipelines | Use templates in YAML files to define reusable pipeline components |
| How to test a pipeline change before applying it to a main branch | Use a feature branch to create and run the pipeline changes before merging |
| How to view pipeline execution logs in Azure Pipelines | Navigate to the pipeline run and select the job or task to view detailed logs |
| Key benefit of Continuous Integration | Early detection of integration bugs and reduced integration effort |
| Key benefit of using YAML pipelines over classic UI pipelines | Version control and ease of sharing the pipeline configuration |
| Key metric for evaluating CI pipelines | Build frequency and success rate |
| Primary tool in Azure DevOps for creating pipelines | Azure Pipelines |
| Tool in Azure DevOps for managing pull requests | Azure Repos |
| What does 'checkout' do in a YAML pipeline | Fetches source code from the repository for the pipeline to work on |
| What does 'CI/CD' stand for | Continuous Integration and Continuous Deployment or Delivery |
| What does caching do in a build pipeline | Stores dependencies or outputs to reduce build times for future runs |
| What does the 'runOnce' deployment strategy in YAML do | Executes a job or stage only once during the pipeline run |
| What does the 'trigger' section in a YAML pipeline define | The events that will start the pipeline |
| What is a build pipeline | An automated process that compiles source code, runs tests, and creates deployable artifacts |
| What is a self-hosted agent | An agent installed on your own infrastructure to execute pipeline jobs |
| What is a YAML file in Azure Pipelines | A configuration file defining steps of a pipeline in an easy-to-read format |
| What is conditional execution in a build pipeline | Running certain steps or tasks only if specified conditions are met |
| What is Continuous Integration | A development practice where developers frequently integrate code into a shared repository to detect issues early |
| What is the 'agent' in an Azure Pipeline job | A virtual machine or container where the pipeline runs |
| What is the 'condition' property in a pipeline step | A condition that determines whether a particular step will execute |
| What is the purpose of 'stages' in a build pipeline | To organize and divide the pipeline into sequential or parallel steps |
| What is the purpose of a build artifact | To package the output of a build process for use in deployment or later stages |
| What is the purpose of automated unit testing | To ensure individual units of source code work as expected |
| What is the purpose of continuous feedback | To provide developers with immediate insights on their changes |
This deck covers configuring build pipelines, integrating Git repositories, and setting up automated unit testing within Azure DevOps.