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

 

Q141. Which Azure DevOps feature can restrict who is allowed to approve a production deployment?

1) Pipeline cache
2) Deployment approval
3) Git clone
4) Artifact feed

Correct Answer: 2)

Explanation:

Deployment approvals provide a control mechanism that can require designated users or groups to authorize a deployment before it proceeds. This is particularly useful for production environments where organizations want human oversight before releasing changes. Approvals can be combined with automated checks and other environment protections to create a controlled release process. For example, a team may automatically deploy to development and testing environments but require an authorized production owner to approve the final deployment. This approach helps reduce accidental releases and supports organizational governance while still allowing most of the delivery process to remain automated.

Q142. Which feature allows a pipeline to use a previously published package without rebuilding the application?

1) Pipeline artifact or package artifact
2) Branch policy
3) Agent demand
4) Work item query

Correct Answer: 1)

Explanation:

Published artifacts allow a pipeline or downstream deployment process to consume files that were already produced by an earlier build. This supports the build-once-and-deploy approach, where the application is compiled and packaged once and then promoted through different environments. Reusing the same artifact reduces the possibility that different environments receive different builds. Artifacts can include application packages, binaries, deployment manifests, or other required files. Keeping artifacts associated with their originating build also improves traceability because teams can determine which source revision and pipeline execution produced the deployed version.

Q143. Which Git operation is most appropriate for temporarily saving uncommitted changes before switching branches?

1) Git merge
2) Git tag
3) Git stash
4) Git revert

Correct Answer: 3)

Explanation:

Git stash temporarily stores uncommitted changes so that a developer can work with a clean working directory without committing unfinished work. This can be useful when a developer needs to switch branches quickly to investigate an urgent issue or perform another task. Afterward, the stashed changes can be reapplied to continue the original work. Stashing is different from committing because the changes are not recorded as a normal project commit. Developers should still review the working tree after applying a stash because conflicts can occur if the underlying files changed while the work was stored.

Q144. Which Azure DevOps feature helps identify whether a pull request satisfies required build validation before merging?

1) Azure Monitor
2) Build validation policy
3) Secure file
4) Package feed

Correct Answer: 2)

Explanation:

A build validation policy can require a successful build or pipeline execution before a pull request can be merged into a protected branch. This helps ensure that proposed changes compile successfully and can pass required automated validation. The policy can be configured on important branches so that developers receive feedback before changes enter the main codebase. Build validation is especially useful when combined with automated unit tests, security scans, and other quality checks. By enforcing validation automatically, teams reduce the chance of introducing broken code into shared branches and create a consistent quality-control process for collaborative development.

Q145. Which practice is most effective for reducing security risks caused by excessive permissions in a service connection?

1) Grant administrator permissions to every pipeline
2) Use the principle of least privilege
3) Store credentials in source code
4) Disable authentication

Correct Answer: 2)

Explanation:

The principle of least privilege means granting a service connection only the permissions required for its intended operations. For example, a pipeline that only needs to deploy to a particular resource should not automatically receive broad administrator access across an entire subscription. Restricting permissions reduces the potential impact if a pipeline or credential is compromised. Teams should also review which pipelines are authorized to use each service connection and remove unnecessary access. Least-privilege service connections are an important part of DevSecOps because automated pipelines often have access to valuable infrastructure and deployment resources.

Q146. Which Azure DevOps capability can store credentials and configuration values that multiple pipelines need to share?

1) Variable group
2) Git branch
3) Test plan
4) Deployment slot

Correct Answer: 1)

Explanation:

Variable groups provide a centralized way to manage values that can be shared across multiple Azure Pipelines. They can contain configuration values and, when appropriately secured, secret values used by pipeline tasks. Centralizing shared configuration reduces duplication and makes pipeline maintenance easier. Variable groups can also be linked with Azure Key Vault for stronger secret management. Teams should carefully control who can modify or consume sensitive variable groups because a compromised pipeline could potentially access their contents. Proper authorization and separation of environment-specific configuration help maintain security while allowing multiple pipelines to reuse common settings.

Q147. Which deployment approach gradually moves users or traffic to a new application version while monitoring its behavior?

1) Canary deployment
2) Full replacement deployment
3) Manual rebuild
4) Source synchronization

Correct Answer: 1)

Explanation:

A canary deployment introduces a new application version to a small portion of users or infrastructure before expanding the release to a larger population. Teams can monitor performance, errors, availability, and other signals during the initial exposure. If the new version behaves as expected, the deployment can gradually increase its traffic. If serious problems are detected, the rollout can be stopped or reversed before all users are affected. Canary releases are useful for reducing deployment risk, particularly when changes are significant or production behavior cannot be completely predicted through preproduction testing alone.

Q148. Which technique allows application functionality to be enabled or disabled without deploying new application code?

1) Git reset
2) Feature flag
3) Agent pool
4) Package restore

Correct Answer: 2)

Explanation:

Feature flags allow teams to control application functionality through configuration rather than requiring a new code deployment every time a feature is enabled or disabled. A team can deploy code containing a new capability while keeping the feature disabled until validation is complete. The feature can then be enabled for selected users, environments, or traffic groups. This supports controlled releases and can reduce deployment risk. Feature flags should be managed carefully because unused flags can increase application complexity. Teams should document their purpose and remove obsolete flags when they are no longer needed.

Q149. Which Azure DevOps feature allows teams to store and distribute packages such as NuGet, npm, Maven, or Python packages?

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

Correct Answer: 3)

Explanation:

Azure Artifacts provides package management capabilities for supported package types such as NuGet, npm, Maven, and Python packages. Teams can publish internal packages, manage versions, and control access to package feeds. This is useful for organizations that maintain reusable libraries or components shared across multiple applications. Azure Artifacts can also support upstream sources, allowing teams to consume packages from external repositories while maintaining centralized management. Integrating package management with CI/CD improves consistency and traceability because pipeline builds can retrieve known package versions and publish newly created packages as part of an automated development workflow.

Q150. Which testing type verifies that multiple application components work correctly together?

1) Unit testing
2) Integration testing
3) Static analysis
4) Code formatting

Correct Answer: 2)

Explanation:

Integration testing verifies that multiple application components interact correctly with one another. While unit tests generally focus on individual functions or components in isolation, integration tests evaluate interactions such as database access, service communication, APIs, or message-processing workflows. These tests can identify problems that unit tests may not detect because the issue occurs at the boundary between components. Integrating automated integration tests into a CI/CD pipeline provides earlier feedback when changes break system interactions. Teams should balance execution time and test coverage so that important integration scenarios are validated without making the development feedback cycle unnecessarily slow.

Q151. Which security practice analyzes application source code for vulnerabilities without executing the application?

1) Static Application Security Testing
2) Load testing
3) User acceptance testing
4) Availability testing

Correct Answer: 1)

Explanation:

Static Application Security Testing, commonly called SAST, examines application source code or compiled representations to identify potential security weaknesses without requiring the application to run. SAST tools can detect patterns associated with issues such as insecure coding practices, injection vulnerabilities, or unsafe data handling. Integrating SAST into CI/CD allows developers to receive security feedback earlier in the development process. This supports the shift-left security approach, where security validation begins during development instead of being postponed until deployment. Teams should configure appropriate severity thresholds and review findings to distinguish genuine vulnerabilities from false positives.

Q152. Which practice helps ensure infrastructure changes do not violate defined organizational security requirements before deployment?

1) Manual source editing
2) Policy and compliance checks
3) Git stash
4) Pipeline caching

Correct Answer: 2)

Explanation:

Policy and compliance checks can evaluate infrastructure definitions or target resources against organizational requirements before changes are applied. This helps prevent configurations that violate security, governance, or regulatory expectations from reaching controlled environments. For example, an organization may require approved regions, mandatory tags, encryption settings, or restricted resource types. Integrating these checks into infrastructure delivery creates automated guardrails and reduces reliance on manual review. Policy validation is especially useful in Infrastructure as Code workflows because infrastructure changes can be evaluated before deployment. This supports consistent governance while allowing teams to continue using automated delivery processes.

Q153. Which practice helps identify whether a deployed application is experiencing increased response times?

1) Application performance monitoring
2) Git branching
3) Package publishing
4) Artifact retention

Correct Answer: 1)

Explanation:

Application performance monitoring collects and analyzes information about application behavior, including response times, request rates, failures, dependencies, and resource utilization. Monitoring performance trends allows teams to identify slow requests or degraded application behavior after deployment. Tools such as Application Insights can provide telemetry that helps engineers investigate performance issues and understand which components contribute to delays. Performance monitoring should be part of the overall observability strategy rather than being used only after an incident occurs. Continuous monitoring provides feedback that can guide optimization, capacity planning, and future development decisions.

Q154. Which testing approach evaluates how an application behaves under expected and increased levels of user traffic?

1) Unit testing
2) Load testing
3) Static code analysis
4) Branch validation

Correct Answer: 2)

Explanation:

Load testing evaluates an application’s behavior under a defined level of expected or increased traffic. It can help teams determine whether the application maintains acceptable response times, reliability, and resource utilization as demand changes. Load testing can identify performance bottlenecks in application code, databases, APIs, infrastructure, or network dependencies. Including performance tests in appropriate stages of the delivery process allows teams to identify capacity problems before major production releases. Test scenarios should represent realistic workloads, and results should be compared against clearly defined performance objectives rather than simply focusing on whether the application remains available.

Q155. Which practice helps reduce the risk of deploying a change that has not been tested with real production traffic?

1) Increasing repository size
2) Using a staging environment
3) Removing automated tests
4) Disabling monitoring

Correct Answer: 2)

Explanation:

A staging environment provides a controlled location where an application version can be deployed and validated before production release. Teams can perform functional testing, integration testing, security checks, performance validation, and deployment verification in an environment designed to resemble production. Although staging cannot reproduce every real-world condition, it reduces the risk of discovering basic release problems only after production deployment. Teams can also combine staging validation with monitoring, approvals, and controlled deployment strategies. Keeping staging configuration reasonably representative of production is important because large differences between environments can reduce the value of preproduction testing.

Q156. Which Git practice is useful for marking a specific version of the source code?

1) Git tag
2) Git stash
3) Git fetch
4) Git diff

Correct Answer: 1)

Explanation:

Git tags provide a way to identify a specific commit as an important point in the repository’s history. Teams commonly use tags to mark application releases, such as version numbers, allowing developers and automated processes to reference a stable source revision. Tags improve traceability because a release can be associated with an exact point in source control. They can also be used by CI/CD workflows to trigger release processes or identify the source version associated with an artifact. Teams should establish a consistent tagging convention and protect release-related tags when necessary to prevent unauthorized changes.

Q157. Which Azure DevOps feature helps teams manage automated and manual testing activities?

1) Azure Test Plans
2) Azure Repos
3) Azure Monitor
4) Azure Key Vault

Correct Answer: 1)

Explanation:

Azure Test Plans provides capabilities for planning, organizing, and tracking software testing activities. Teams can create test cases, organize test suites, execute manual tests, and review testing outcomes. Test Plans can complement automated testing by providing structured coverage for scenarios that require human validation or exploratory testing. Linking testing activities with development work can improve traceability between requirements, defects, and validation. In a DevOps environment, testing should be integrated throughout the delivery lifecycle rather than being treated as a final activity. Azure Test Plans can help teams maintain visibility into testing progress and results.

Q158. Which approach helps reduce bottlenecks caused by too many work items being started simultaneously?

1) Increasing work in progress
2) Removing priorities
3) Limiting work in progress
4) Disabling the board

Correct Answer: 3)

Explanation:

Limiting work in progress, commonly called WIP limits, helps teams avoid starting more work than they can efficiently complete. When too many items are active simultaneously, context switching increases and tasks may remain unfinished for long periods. WIP limits encourage teams to finish existing work before starting additional tasks. This can improve flow, expose process bottlenecks, and make delivery times more predictable. Kanban-style workflows commonly use WIP limits as part of continuous improvement. Teams should establish limits based on their capacity and review them regularly rather than selecting arbitrary values without considering the actual workflow.

Q159. Which practice provides evidence that a released artifact can be traced back to its source commit and build?

1) Artifact traceability
2) Manual configuration
3) Branch deletion
4) UI redesign

Correct Answer: 1)

Explanation:

Artifact traceability connects a released software artifact to information about its origin, such as the source commit, repository, build pipeline, and associated work items. This allows teams to determine exactly which source changes contributed to a particular release. Strong traceability is useful for troubleshooting, auditing, security investigations, and release management. If a production issue occurs, engineers can identify the deployed artifact and trace it back through the build process to the source changes that produced it. Maintaining this relationship throughout the CI/CD lifecycle improves confidence that teams understand what software is actually running in each environment.

Q160. Which DevOps practice encourages teams to review failures without assigning personal blame and focus on system improvements?

1) Forced deployment
2) Blameless postmortem
3) Manual approval bypass
4) Branch deletion

Correct Answer: 2)

Explanation:

A blameless postmortem focuses on understanding the causes and contributing factors behind an incident rather than assigning fault to individuals. Teams examine system design, processes, communication, monitoring, testing, deployment practices, and other conditions that influenced the outcome. The purpose is to identify actionable improvements that reduce the likelihood or impact of similar incidents in the future. This approach encourages team members to share accurate information without fear of punishment, which can lead to better organizational learning. Blameless postmortems are an important part of continuous improvement because they turn operational failures into opportunities to strengthen systems and processes.