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

 

Q341. Which Azure DevOps feature can automatically link a commit or pull request to an Azure Boards work item?

1) Work item integration
2) Pipeline caching
3) Agent demand
4) Artifact retention

Correct Answer: 1)

Explanation:

Work item integration connects development activities with Azure Boards work items, helping teams maintain traceability between planned work and implementation changes. Depending on the workflow and configuration, commits, pull requests, builds, and other development activities can be associated with work items. This allows teams to determine which changes were made to address a particular requirement, bug, or task. Traceability is valuable for project management, auditing, troubleshooting, and reporting because it connects planning information with actual development activity. Pipeline caching improves execution speed, agent demands control job requirements, and artifact retention manages stored outputs. Therefore, work item integration is the appropriate capability for linking development changes to tracked work.

Q342. Which Azure Boards capability helps a team prioritize and organize upcoming work before development begins?

1) Deployment slot
2) Product backlog
3) Service connection
4) Pipeline artifact

Correct Answer: 2)

Explanation:

The Azure Boards product backlog provides a prioritized list of work items that a team can plan and organize before implementation. Teams can add requirements, user stories, bugs, and other work items, then prioritize them according to business value and delivery goals. Backlog management helps teams decide what should be addressed next and provides a foundation for sprint planning. Deployment slots are used for application deployment, service connections provide authenticated access to external resources, and pipeline artifacts contain build outputs. Therefore, the product backlog is the appropriate Azure Boards capability for organizing and prioritizing upcoming development work.

Q343. Which Agile practice divides planned work into short, time-boxed periods for focused delivery?

1) Sprint planning
2) Artifact publishing
3) Continuous monitoring
4) Container scanning

Correct Answer: 1)

Explanation:

Sprint planning is an Agile practice used to determine which work items a team intends to complete during a defined sprint. A sprint is a short, time-boxed period during which the team focuses on delivering a selected set of work. During planning, the team reviews priorities, considers available capacity, and agrees on the work that can realistically be completed. This approach provides regular opportunities to inspect progress and adjust priorities in subsequent iterations. Artifact publishing, monitoring, and container scanning are technical DevOps activities rather than Agile planning practices. Therefore, sprint planning is the appropriate practice for organizing work into focused delivery periods.

Q344. Which Azure Boards feature helps teams visualize work remaining across iterations and identify progress toward completion?

1) Burndown chart
2) Service connection
3) Artifact feed
4) Deployment job

Correct Answer: 1)

Explanation:

A burndown chart provides a visual representation of remaining work over time during an iteration or sprint. Teams can use it to compare actual progress with the amount of work expected to remain and identify whether they are likely to complete the planned work. Burndown information can help highlight changes in scope, slow progress, or potential delivery risks. Service connections provide authentication to external resources, artifact feeds manage packages, and deployment jobs execute deployment activities. Therefore, a burndown chart is the appropriate Azure Boards feature for visualizing remaining work and tracking progress toward completion.

Q345. What is the primary purpose of Azure Test Plans in a DevOps workflow?

1) Manage and execute structured software tests
2) Store production secrets
3) Host container images
4) Configure DNS records

Correct Answer: 1)

Explanation:

Azure Test Plans provides tools for organizing and managing structured testing activities within Azure DevOps. Teams can create test cases, organize test suites, execute tests, and track results. This is useful for manual testing, user acceptance testing, exploratory testing, and other quality-validation activities. Test Plans can complement automated tests executed through CI/CD pipelines by providing a broader view of software quality. It is not intended to store production secrets, host container images, or manage DNS records. Those functions belong to other services. Therefore, managing and executing structured software tests is the primary purpose of Azure Test Plans.

Q346. Which testing activity allows business users to verify that a solution meets their requirements before production release?

1) User acceptance testing
2) Dependency restoration
3) Static compilation
4) Container publishing

Correct Answer: 1)

Explanation:

User acceptance testing, or UAT, allows business representatives or intended users to verify that an application meets defined business requirements and behaves appropriately for real-world scenarios. UAT typically occurs after earlier development and technical testing activities and before production release. It focuses on whether the solution satisfies business needs rather than only checking technical implementation details. Successful UAT can provide confidence that the application is ready for business use. Dependency restoration, compilation, and container publishing are technical activities and do not directly validate business acceptance. Therefore, user acceptance testing is the appropriate activity for business users to verify solution requirements.

Q347. Which testing technique checks whether existing functionality continues to work after application changes?

1) Regression testing
2) Capacity planning
3) License scanning
4) Infrastructure provisioning

Correct Answer: 1)

Explanation:

Regression testing verifies that previously working functionality continues to behave correctly after changes are introduced. Application modifications can unintentionally affect existing features, integrations, or workflows, even when the change appears unrelated. Regression tests provide confidence that new development has not introduced unexpected defects into established functionality. These tests can be automated and incorporated into CI/CD pipelines so that they run consistently whenever relevant changes are submitted. Capacity planning focuses on resource requirements, license scanning examines software licensing, and infrastructure provisioning creates resources. Therefore, regression testing is the appropriate testing technique for verifying that existing functionality remains stable after changes.

Q348. What is the main purpose of unit testing in a CI pipeline?

1) Validate individual pieces of application logic automatically
2) Deploy the entire production environment
3) Manage employee permissions
4) Create cloud subscriptions

Correct Answer: 1)

Explanation:

Unit testing focuses on validating individual units of application code, such as functions, methods, or small components, in isolation. Including unit tests in a CI pipeline allows developers to receive rapid feedback when code changes introduce defects. Automated unit tests can execute consistently on every relevant build, helping detect problems before changes progress to later testing or deployment stages. Unit tests are generally faster than broader integration or end-to-end tests, making them especially valuable early in the pipeline. They do not deploy production environments, manage permissions, or create subscriptions. Therefore, automatically validating individual pieces of application logic is the primary purpose of unit testing in CI.

Q349. Which practice helps ensure that a failed automated test prevents an unsafe deployment from continuing?

1) Configure the pipeline to require successful test results
2) Ignore test failures
3) Delete failed test records
4) Run tests only after production deployment

Correct Answer: 1)

Explanation:

A pipeline should be configured so that required automated tests must succeed before deployment stages can proceed. This creates a quality gate that prevents known test failures from being automatically promoted into later environments. For example, a CI stage can execute unit and integration tests, and the deployment stage can depend on successful completion of those tests. If a required test fails, the pipeline should stop or follow an appropriate failure-handling path. Ignoring failures or running tests only after production deployment increases risk. Therefore, requiring successful test results before deployment is an important CI/CD quality-control practice.

Q350. Which security practice scans source code for common coding vulnerabilities without executing the application?

1) Dynamic application testing
2) Static application security testing
3) Load testing
4) User acceptance testing

Correct Answer: 2)

Explanation:

Static application security testing, commonly called SAST, analyzes source code or compiled representations to identify potential security weaknesses without requiring the application to execute. SAST tools can detect patterns associated with issues such as insecure coding practices, injection risks, or improper handling of sensitive information. Integrating SAST into CI helps identify security problems early, allowing developers to address them before software reaches later environments. Dynamic testing evaluates an application while it is running, load testing focuses on performance under demand, and UAT validates business requirements. Therefore, SAST is the appropriate security practice for analyzing source code without executing the application.

Q351. Which security check examines third-party packages for known vulnerabilities?

1) Dependency scanning
2) Sprint planning
3) UI testing
4) Deployment scheduling

Correct Answer: 1)

Explanation:

Dependency scanning examines third-party libraries and packages used by an application to identify known security vulnerabilities. Modern applications often depend on many external components, so vulnerabilities in those components can introduce risk even when the organization’s own source code is secure. Dependency scanning can be integrated into CI pipelines to identify vulnerable packages early and support remediation or upgrade decisions. This practice complements other security controls such as SAST, secret scanning, and container image scanning. Sprint planning organizes work, UI testing validates application behavior, and deployment scheduling controls release timing. Therefore, dependency scanning is the correct security check for identifying vulnerable third-party packages.

Q352. What is the main purpose of secret scanning in a source repository?

1) Detect exposed credentials or sensitive tokens
2) Measure application response time
3) Increase package storage
4) Create database backups

Correct Answer: 1)

Explanation:

Secret scanning helps identify credentials, access tokens, API keys, passwords, and other sensitive values that may have been accidentally committed to source repositories. Detecting exposed secrets early is important because credentials stored in source control can potentially be accessed by unauthorized users. Secret scanning can be integrated into development workflows and CI pipelines to prevent or flag risky commits. If a secret is discovered, teams should also rotate or revoke it rather than simply deleting the visible text from the repository. Secret scanning does not measure application performance, increase package storage, or create backups. Therefore, detecting exposed credentials is its primary purpose.

Q353. Which approach provides developers with faster feedback by running independent pipeline jobs at the same time?

1) Parallel execution
2) Sequential execution only
3) Manual approval
4) Artifact retention

Correct Answer: 1)

Explanation:

Parallel execution allows independent pipeline jobs to run simultaneously rather than waiting for each job to finish before starting the next. This can significantly reduce overall pipeline duration when tasks do not depend on one another. For example, separate test suites, code analysis tasks, or builds for different components may be executed concurrently. Parallelism should be used carefully because dependent tasks must still execute in the appropriate order. Manual approvals introduce human checkpoints, while artifact retention controls how long outputs are stored. Therefore, running independent pipeline jobs in parallel is an effective way to improve CI/CD execution speed and provide faster feedback.

Q354. Which pipeline optimization stores previously downloaded dependencies so future builds can retrieve them faster?

1) Pipeline caching
2) Branch protection
3) Work item linking
4) Deployment approval

Correct Answer: 1)

Explanation:

Pipeline caching stores reusable files, such as package dependencies, so subsequent pipeline executions can retrieve them from a cache instead of downloading or rebuilding everything from scratch. This can reduce build duration and network usage, particularly for projects with large dependency sets. Cache keys and restore behavior should be configured carefully so that stale or incompatible dependencies are not reused incorrectly. Pipeline caching is primarily an optimization technique and does not replace dependency management or testing. Branch protection controls source integration, work item linking provides traceability, and deployment approvals provide governance. Therefore, pipeline caching is the appropriate optimization for speeding up repeated dependency retrieval.

Q355. Which approach can improve pipeline reliability by ensuring dependencies are explicitly versioned?

1) Dependency pinning
2) Random dependency selection
3) Manual production installation
4) Removing package versions

Correct Answer: 1)

Explanation:

Dependency pinning specifies exact or controlled versions of external packages used by an application. This helps make builds more predictable because the same dependency versions can be restored consistently rather than allowing an unexpected newer release to be introduced automatically. Predictable dependencies are particularly important for CI/CD pipelines because a build should ideally produce consistent results when the application source has not changed. Teams should still monitor pinned dependencies for security updates and deliberately upgrade them when appropriate. Random dependency selection or removing version information can introduce unexpected changes. Therefore, dependency pinning is an effective practice for improving build reproducibility and pipeline reliability.

Q356. Which concept describes the ability to reproduce a build using the same source and dependency inputs?

1) Reproducible build
2) Manual deployment
3) Emergency approval
4) Untracked release

Correct Answer: 1)

Explanation:

A reproducible build is a build process designed so that the same source code and controlled inputs produce an equivalent output when executed again. Reproducibility improves confidence in build integrity, troubleshooting, auditing, and software supply-chain security. To support reproducibility, teams commonly control dependency versions, build tools, configuration, and other relevant inputs. If builds depend on uncontrolled external changes, the same source may produce different results at different times. Manual deployments and emergency approvals do not define build reproducibility. Therefore, the concept describing consistent build output from the same controlled inputs is a reproducible build.

Q357. Which deployment practice reduces risk by validating a release in a staging environment before production?

1) Pre-production validation
2) Immediate production deployment
3) Skipping automated tests
4) Removing environment separation

Correct Answer: 1)

Explanation:

Pre-production validation provides an opportunity to verify a release in an environment that closely resembles production before exposing it to production users. Teams can perform automated tests, integration checks, performance validation, security checks, and manual acceptance activities in the staging environment. This helps identify configuration or application problems before production deployment. The staging environment should ideally use the same artifact that will later be promoted to production to maintain consistency. Deploying immediately to production or skipping validation increases release risk. Therefore, validating a release in a staging or pre-production environment is an important practice for reducing deployment failures.

Q358. Which approach helps ensure infrastructure changes are reviewed before they are applied to production?

1) Infrastructure pull requests
2) Direct production editing
3) Untracked manual changes
4) Shared administrator passwords

Correct Answer: 1)

Explanation:

Infrastructure pull requests provide a controlled review process for Infrastructure as Code changes before they are merged and applied to production. Team members can inspect proposed changes, run automated validation, perform security checks, review Terraform plans or Bicep validation results, and provide approval. This creates traceability and reduces the risk of accidental or unauthorized infrastructure modifications. Direct production editing bypasses source-controlled review and makes changes harder to reproduce. Untracked changes and shared administrator passwords further reduce accountability and security. Therefore, using infrastructure pull requests is an effective way to introduce review, validation, and governance into infrastructure delivery.

Q359. What is a major benefit of treating infrastructure definitions as source-controlled code?

1) Changes can be reviewed, versioned, and reproduced
2) Cloud resources never require monitoring
3) Security testing becomes unnecessary
4) Production access becomes unrestricted

Correct Answer: 1)

Explanation:

Treating infrastructure definitions as source-controlled code provides version history, review processes, traceability, and the ability to reproduce infrastructure configurations. Teams can review infrastructure changes through pull requests, identify who made modifications, compare versions, and return to an earlier configuration when appropriate. Infrastructure as Code also enables automation and consistent deployments across environments. However, source-controlled infrastructure does not eliminate the need for monitoring, security testing, or access controls. These remain important operational requirements. Therefore, the major benefit is that infrastructure changes can be systematically reviewed, versioned, tracked, and reproduced rather than relying entirely on manual configuration.

Q360. Which DevOps practice helps identify differences between the desired infrastructure configuration and the actual deployed environment?

1) Infrastructure drift detection
2) Manual source editing
3) User acceptance testing
4) Pipeline notification

Correct Answer: 1)

Explanation:

Infrastructure drift detection identifies differences between the infrastructure described by the desired configuration and the resources that actually exist in an environment. Drift can occur when someone manually changes a resource outside the Infrastructure as Code workflow or when another process modifies infrastructure unexpectedly. Detecting drift helps teams determine whether deployed resources still match the approved configuration. Once identified, the team can investigate and decide whether to reconcile the infrastructure with the desired state or update the source-controlled definition. User acceptance testing validates business functionality, while pipeline notifications communicate events. Therefore, infrastructure drift detection is the appropriate practice for identifying configuration differences.