View Full Microsoft AZ-400 Exam Dumps and Practice Test Dumps

 

Q101. Which Azure Pipelines feature allows a stage to run only when a specified condition is satisfied?

1) Pipeline artifact
2) Agent pool
3) Conditional expression
4) Variable group

Correct Answer: 3)

Explanation:

Conditional expressions in Azure Pipelines control whether a job, stage, or step should execute based on defined criteria. Conditions can evaluate variables, the result of previous stages, branch information, or other pipeline states. For example, a deployment stage can be configured to run only when the build succeeds and the pipeline is running from a specific branch. This provides greater control over complex CI/CD workflows and prevents unnecessary or inappropriate deployments. Conditional execution is especially useful when different environments require different rules, such as deploying to production only after successful testing and approval.

Q102. A pipeline needs to pass a value generated in one job to another job. Which feature should be used?

1) Output variables
2) Pipeline artifact
3) Secure file
4) Agent demand

Correct Answer: 1)

Explanation:

Output variables allow values generated during one Azure Pipelines job to be consumed by another dependent job or stage. They are useful when a pipeline dynamically creates information that later tasks need, such as a version number, deployment identifier, or generated configuration value. The producing task must mark the variable as an output, and the consuming job can reference it through the appropriate dependency syntax. This approach avoids manually copying values between jobs and keeps information flowing automatically through the pipeline. Output variables are particularly helpful in multi-stage YAML pipelines where earlier processing determines values required by later deployment activities.

Q103. Which Azure Pipelines feature allows users to provide values when manually starting a pipeline?

1) Service connection
2) Runtime parameter
3) Secure file
4) Agent pool

Correct Answer: 2)

Explanation:

Runtime parameters allow users to provide values when manually running an Azure Pipeline. They are defined in YAML and can control pipeline behavior, such as selecting an environment, choosing a deployment mode, or specifying which component should be processed. Unlike ordinary variables, parameters are evaluated when the pipeline is expanded and can influence the structure of the pipeline itself. This makes them useful for creating reusable pipelines that support different scenarios without requiring separate YAML definitions. Runtime parameters should be designed carefully so users cannot accidentally select unsafe production options or bypass required controls.

Q104. A deployment pipeline must securely provide a certificate file to a build agent. Which Azure DevOps feature is most appropriate?

1) Pipeline artifact
2) Variable group
3) Secure file
4) Pipeline cache

Correct Answer: 3)

Explanation:

Secure files are designed to store sensitive files such as certificates, provisioning profiles, signing keys, or configuration files that pipelines need during execution. Access to these files can be controlled through pipeline permissions and authorization settings. During execution, an authorized task can download the secure file to the agent and use it for the required operation. This is safer than placing sensitive files directly in source control or embedding them in YAML definitions. Secure files are therefore useful when a CI/CD process requires protected file-based credentials while maintaining centralized security and access management.

Q105. Which Azure service is designed to centrally manage application configuration settings and feature flags?

1) Azure App Configuration
2) Azure Repos
3) Azure Artifacts
4) Azure Boards

Correct Answer: 1)

Explanation:

Azure App Configuration provides a centralized location for application configuration settings and feature flags. Instead of storing configuration values independently within application deployments, teams can manage common settings centrally and allow applications to retrieve the appropriate configuration at runtime. This supports DevOps practices by separating application code from environment-specific configuration. Feature flags can also be used to enable or disable functionality without requiring a complete application redeployment. Azure App Configuration can work alongside other Azure security services when sensitive values must be protected. It is especially useful for applications deployed across multiple environments with different configuration requirements.

Q106. An organization wants to test a new version of an Azure App Service application without immediately replacing the production version. Which feature should be used?

1) Azure Boards
2) Deployment slot
3) Variable group
4) Pipeline artifact

Correct Answer: 2)

Explanation:

Azure App Service deployment slots provide separate environments within an App Service application, such as staging and production. A development team can deploy a new application version to a staging slot, perform testing, validate configuration, and monitor behavior before exposing the version to production users. This reduces deployment risk because the existing production version remains available while validation occurs. Slots are particularly valuable for release strategies that require controlled testing before traffic is moved. They can also support quick transitions between application versions when properly configured, making them an important capability for reliable continuous delivery.

Q107. After testing an application in a staging slot, which operation can move that version into production with minimal downtime?

1) Slot swap
2) Git reset
3) Package restore
4) Build validation

Correct Answer: 1)

Explanation:

A slot swap exchanges the application content and applicable configuration between two Azure App Service deployment slots, commonly staging and production. This allows a team to validate a new application version in staging before making it available through the production slot. Swapping can provide a controlled transition and helps reduce deployment downtime compared with rebuilding the application directly in production. Teams should carefully review which settings are slot-specific and which settings move during the swap. Slot swaps are therefore useful for controlled releases where the application must be thoroughly tested before receiving production traffic.

Q108. Which Azure Pipelines capability allows a job to execute inside a Docker container?

1) Environment approval
2) Container job
3) Variable group
4) Deployment gate

Correct Answer: 2)

Explanation:

A container job allows Azure Pipelines tasks to execute within a specified Docker container environment. This provides greater consistency between pipeline runs because the job can use a known image containing the required operating system, runtime, and dependencies. Containerized jobs can reduce differences between agents and help teams create more reproducible build or test environments. They are particularly useful when a project requires a specific toolchain that would otherwise need to be installed on every agent. Teams should ensure that the selected container image is trusted, maintained, and compatible with the tasks and agent capabilities required by the pipeline.

Q109. Which Azure service provides a private registry for storing and managing container images?

1) Azure Monitor
2) Azure Boards
3) Azure Container Registry
4) Azure Test Plans

Correct Answer: 3)

Explanation:

Azure Container Registry, commonly called ACR, provides a managed private registry for storing and distributing container images and related artifacts. CI/CD pipelines can build container images and push them to an ACR repository, where authorized deployment systems can retrieve them later. Using a private registry provides better control over image access, versioning, and distribution than relying exclusively on public registries. ACR integrates with Azure services and DevOps workflows, making it suitable for applications deployed to services such as Azure Kubernetes Service. Access should be controlled using appropriate identities, permissions, and authentication mechanisms.

Q110. Which tool is commonly used to package and manage Kubernetes applications as charts?

1) Bicep
2) Git
3) Helm
4) KQL

Correct Answer: 3)

Explanation:

Helm is a package manager for Kubernetes that uses charts to define, package, and deploy Kubernetes applications. A Helm chart can contain Kubernetes resource definitions along with templates and configuration values. This makes it easier to deploy the same application across multiple environments while changing environment-specific settings through values. Helm can also manage application versions and support upgrades or rollbacks. In DevOps workflows, Helm charts can be stored and versioned alongside application configuration and deployed through automated pipelines. This helps standardize Kubernetes deployments and reduces repetitive manual configuration across development, testing, and production environments.

Q111. Which deployment approach is commonly used in Azure DevOps to apply Kubernetes resource definitions stored in YAML files?

1) Kubernetes manifest deployment
2) Azure Boards query
3) Git tagging
4) Variable group linking

Correct Answer: 1)

Explanation:

Kubernetes manifest deployment uses YAML manifest files to describe Kubernetes resources such as deployments, services, namespaces, and configuration objects. Azure DevOps pipelines can use Kubernetes-related tasks to apply these manifests to a target Kubernetes cluster. Keeping manifests under version control provides traceability because changes can be reviewed, approved, and linked to pipeline executions. This approach also supports repeatable deployments because the desired Kubernetes state is represented declaratively. Teams can combine manifest deployment with container image versioning, environment-specific configuration, security controls, and automated testing to create a consistent Kubernetes CI/CD process.

Q112. Which Azure capability can be used to enforce organizational compliance rules on Azure resources?

1) Azure Repos
2) Azure Policy
3) Azure Test Plans
4) Azure Artifacts

Correct Answer: 2)

Explanation:

Azure Policy helps organizations define and enforce rules for Azure resources. Policies can evaluate resource configurations and identify or prevent deployments that do not meet organizational requirements. For example, an organization can require specific resource locations, approved resource types, tagging standards, or security configurations. Policy can therefore support compliance as part of a DevOps workflow by applying consistent governance controls across environments. Teams can also monitor policy compliance and use policy results to identify configuration issues. Integrating governance checks into delivery processes helps prevent noncompliant infrastructure from reaching production and supports more consistent operational standards.

Q113. What does a Software Bill of Materials (SBOM) provide?

1) A list of application dependencies and components
2) A database backup
3) A deployment approval record
4) A network routing table

Correct Answer: 1)

Explanation:

A Software Bill of Materials, or SBOM, provides an inventory of the software components, libraries, packages, and dependencies included in an application or software artifact. It improves software supply-chain visibility by helping organizations understand what components are present in a delivered application. If a vulnerability is discovered in a particular library, an SBOM can help teams determine which applications may be affected. SBOMs can also support compliance, auditing, vulnerability management, and risk assessment. Including SBOM generation within a CI/CD workflow provides a more transparent view of software composition and can improve the organization’s ability to respond to security issues.

Q114. Which practice helps establish where a software artifact came from and how it was produced?

1) Manual testing
2) Branch deletion
3) Artifact provenance
4) UI testing

Correct Answer: 3)

Explanation:

Artifact provenance provides information about the origin and production history of a software artifact. It can identify details such as the source repository, commit, build process, dependencies, and pipeline that produced the artifact. Provenance improves software supply-chain security because teams can verify that an artifact originated from an expected source and passed through authorized build processes. This information also supports troubleshooting and auditing because teams can trace deployed software back to its source and build. Establishing provenance is especially valuable when organizations need stronger controls around software integrity, reproducibility, and trusted deployment processes.

Q115. A test sometimes passes and sometimes fails without any code changes. What should the team investigate first?

1) Increase the number of production servers
2) Flaky test behavior
3) Delete the repository
4) Disable all automated testing

Correct Answer: 2)

Explanation:

A flaky test produces inconsistent results even when the relevant application code has not changed. Such tests may pass during one pipeline execution and fail during another because of timing issues, shared test data, concurrency, external dependencies, environment instability, or improper test isolation. Flaky tests can reduce confidence in CI/CD because developers may begin ignoring legitimate failures. Teams should identify the cause, stabilize the test, improve isolation, and monitor recurring failures. Automatically disabling tests should generally be avoided because it can hide real defects. Maintaining reliable automated tests is important for fast and trustworthy continuous integration.

Q116. Which Azure DevOps capability allows automated test execution results to be displayed and tracked in pipeline runs?

1) Publish test results
2) Git tagging
3) Service connection
4) Agent demand

Correct Answer: 1)

Explanation:

Publishing test results allows Azure DevOps pipelines to collect and display results produced by automated testing tools. Depending on the test framework and configuration, the pipeline can publish information such as passed tests, failed tests, skipped tests, and execution details. This makes test outcomes visible directly within pipeline runs and helps teams identify failures quickly. Test result reporting also supports historical analysis and improves traceability between code changes and testing outcomes. Integrating result publication into CI/CD ensures that automated tests are not only executed but that their outcomes become an observable part of the software delivery process.

Q117. Which Azure service provides application performance monitoring and telemetry collection for applications?

1) Azure Boards
2) Azure Artifacts
3) Application Insights
4) Azure Repos

Correct Answer: 3)

Explanation:

Application Insights is an application performance monitoring capability within Azure Monitor. It collects telemetry that can help teams understand application availability, performance, failures, requests, dependencies, and other operational behavior. Developers and operations teams can use this information to investigate problems and identify performance trends after deployment. Application Insights is especially valuable in DevOps because monitoring provides feedback from real production usage and can help teams detect issues that automated testing may not reveal. Integrating application telemetry into the delivery process supports continuous feedback, faster troubleshooting, and more informed decisions about application reliability and performance.

Q118. Which monitoring capability helps trace a request across multiple distributed application components?

1) Branch policy
2) Distributed tracing
3) Pipeline caching
4) Package retention

Correct Answer: 2)

Explanation:

Distributed tracing helps teams follow a request as it travels through multiple services or components in a distributed application. Instead of examining each service independently, engineers can use trace information to understand the sequence of operations, identify slow dependencies, and locate failures within a request path. This is especially important for microservices architectures where one user action may involve many independent services. Distributed tracing improves observability and makes troubleshooting more efficient. When combined with logs, metrics, and application telemetry, tracing provides a broader understanding of application behavior and helps teams identify performance or reliability problems.

Q119. Which Azure service can create alerts when monitored metrics or log conditions indicate a problem?

1) Azure Monitor
2) Azure Repos
3) Azure Boards
4) Azure Artifacts

Correct Answer: 1)

Explanation:

Azure Monitor provides monitoring and alerting capabilities for Azure resources and applications. Alerts can be configured around metrics, log query results, activity events, and other monitored signals. When a configured condition is met, an alert can trigger notifications or automated actions according to the organization’s operational process. This helps teams detect availability, performance, or infrastructure issues without continuously watching dashboards. Effective alerting should focus on meaningful conditions to avoid excessive noise and alert fatigue. When integrated with incident-management processes, Azure Monitor alerts can help teams respond quickly and maintain reliable application and infrastructure operations.

Q120. After resolving a production incident, which practice helps a team identify improvements and prevent similar problems?

1) Delete the incident records
2) Increase deployment frequency immediately
3) Disable monitoring
4) Conduct a blameless postmortem

Correct Answer: 4)

Explanation:

A blameless postmortem reviews an incident to understand what happened, why it happened, how the team responded, and what improvements can prevent recurrence. The goal is not to assign personal blame but to identify weaknesses in systems, processes, monitoring, testing, communication, or deployment practices. Teams can document contributing factors, establish corrective actions, and assign owners for improvements. This creates a continuous learning process and strengthens reliability over time. Blameless postmortems are particularly valuable in DevOps because they encourage transparency and help organizations turn production incidents into actionable improvements rather than simply treating each incident as an isolated failure.