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

 

Q381. Which Azure DevOps feature allows a team to store and manage reusable packages such as NuGet or npm packages?

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

Correct Answer: 1)

Explanation:

Azure Artifacts provides package management capabilities within Azure DevOps. Teams can create and consume package feeds for formats such as NuGet, npm, Maven, and Python packages. Using an internal feed allows organizations to share reusable components while controlling package access and versions. Azure Artifacts can also support upstream sources, allowing teams to consume packages from public registries while maintaining centralized management. Azure Boards is designed for work tracking, Azure Repos provides source control, and Azure Test Plans supports testing activities. Therefore, Azure Artifacts is the appropriate Azure DevOps service for managing reusable software packages.

Q382. What is a major benefit of using an internal package feed for application dependencies?

1) It removes the need for versioning
2) It provides controlled access to packages
3) It prevents all dependency updates
4) It replaces source repositories

Correct Answer: 2)

Explanation:

An internal package feed provides centralized control over software packages used by development teams. Organizations can manage package versions, permissions, retention, and publishing policies while reducing dependence on uncontrolled external package sources. Internal feeds are particularly useful for distributing private libraries and approved third-party dependencies across multiple applications. They also improve consistency because teams can reference known package versions from a controlled location. Package feeds do not eliminate versioning, prevent all updates, or replace source repositories. Source control remains responsible for application code and configuration. Therefore, controlled access to packages is a major benefit of using an internal package feed.

Q383. Which package-management practice reduces unexpected changes caused by automatically receiving newer dependency versions?

1) Dependency pinning
2) Random upgrades
3) Unversioned packages
4) Manual copying

Correct Answer: 1)

Explanation:

Dependency pinning specifies the versions of packages that an application should use. This reduces unexpected changes because builds do not automatically consume newer dependency versions simply because they became available. Predictable dependency versions are important for reproducible builds and stable CI/CD pipelines. Teams should still monitor pinned dependencies for security vulnerabilities and intentionally upgrade them when appropriate. Random upgrades or unversioned dependencies can introduce compatibility problems and make troubleshooting more difficult. Manual copying is also difficult to manage consistently. Therefore, dependency pinning is the recommended practice for controlling dependency changes and improving build predictability.

Q384. Which practice helps ensure that only approved open-source licenses are used by an organization?

1) License compliance scanning
2) Load testing
3) Deployment slots
4) Branch merging

Correct Answer: 1)

Explanation:

License compliance scanning examines application dependencies and identifies the licenses associated with third-party components. Organizations can use this information to determine whether dependencies comply with internal policies, contractual requirements, or legal guidelines. This is especially important for applications that use many open-source libraries because each dependency may have different licensing terms. License scanning can be integrated into CI pipelines so that potentially noncompliant packages are identified before software is released. Load testing measures performance, deployment slots support application releases, and branch merging integrates source changes. Therefore, license compliance scanning is the appropriate practice for managing open-source license requirements.

Q385. Which software supply-chain document provides information about the components included in an application?

1) Software Bill of Materials
2) Sprint backlog
3) Deployment approval
4) Agent capability list

Correct Answer: 1)

Explanation:

A Software Bill of Materials, commonly called an SBOM, provides an inventory of software components included in an application or software artifact. It can identify direct and transitive dependencies and provide useful information for security, vulnerability management, compliance, and incident response. When a vulnerability is discovered in a particular library, an SBOM can help an organization determine which applications contain that component. Sprint backlogs manage development work, deployment approvals provide governance, and agent capabilities describe build environment features. Therefore, an SBOM is the appropriate software supply-chain document for describing application components and dependencies.

Q386. Why should an SBOM be generated as part of a CI/CD process?

1) To provide visibility into software components
2) To eliminate all security vulnerabilities
3) To replace application testing
4) To remove dependency management

Correct Answer: 1)

Explanation:

Generating an SBOM during CI/CD provides a consistent inventory of the software components included in an application or artifact. This visibility supports vulnerability management, compliance activities, software supply-chain analysis, and incident response. When security teams discover a vulnerability in a specific package, an accurate SBOM can help determine whether affected applications contain that component. An SBOM does not automatically eliminate vulnerabilities, replace testing, or remove the need for dependency management. Instead, it provides valuable information that complements those practices. Therefore, providing visibility into the components contained in software is a major reason to generate an SBOM during CI/CD.

Q387. Which security practice identifies vulnerabilities in container images before deployment?

1) Container image scanning
2) Sprint planning
3) Work item estimation
4) Branch naming

Correct Answer: 1)

Explanation:

Container image scanning examines container images for known vulnerabilities, insecure packages, outdated components, and sometimes configuration weaknesses. Integrating image scanning into CI/CD helps teams identify security issues before an image is promoted to production. A pipeline can be configured to fail or require additional review when vulnerabilities exceed an organization’s defined risk threshold. This supports a shift-left security approach by identifying issues earlier in the software delivery lifecycle. Sprint planning, work item estimation, and branch naming support development management rather than container security. Therefore, container image scanning is the appropriate practice for detecting vulnerabilities before container deployment.

Q388. Which container registry service integrates with Azure DevOps to store and distribute private container images?

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

Correct Answer: 1)

Explanation:

Azure Container Registry, or ACR, is a managed registry service for storing and distributing container images and related artifacts. It can integrate with Azure DevOps pipelines so that container images are built, tested, scanned, tagged, and pushed to a private registry as part of an automated workflow. ACR supports access controls and can be used as a reliable source for deployment systems such as Azure Kubernetes Service. Azure Boards manages work items, Azure Test Plans manages testing, and Azure Monitor provides monitoring capabilities. Therefore, Azure Container Registry is the appropriate service for storing and distributing private container images.

Q389. Which container image tagging approach provides stronger traceability between an image and the source code that produced it?

1) Using a unique build or commit identifier
2) Using only the tag latest
3) Using random tag names
4) Removing all image tags

Correct Answer: 1)

Explanation:

Using a unique build number, commit identifier, or another immutable version reference improves traceability between a container image and the source code or pipeline execution that produced it. This allows teams to determine exactly which version was deployed and makes troubleshooting and rollback easier. The latest tag alone can be ambiguous because it may point to different images over time. Random names and removing tags provide even less useful traceability. Organizations should generally prefer identifiable and immutable references, often combined with image digests when appropriate. Therefore, using a unique build or commit identifier is the best approach for container image traceability.

Q390. Which Kubernetes deployment check confirms that an application instance is ready to receive traffic?

1) Readiness probe
2) Liveness probe
3) CPU request
4) Replica count

Correct Answer: 1)

Explanation:

A Kubernetes readiness probe determines whether an application instance is ready to receive traffic. If the readiness check fails, Kubernetes can temporarily remove the pod from service endpoints while allowing the application time to initialize or recover. This prevents traffic from being directed to an application that is running but not yet ready to serve requests correctly. A liveness probe has a different purpose: it helps determine whether a container should be restarted because it is unhealthy. CPU requests and replica counts control resource allocation and scaling behavior. Therefore, the readiness probe is the correct mechanism for determining whether an application instance should receive traffic.

Q391. What is the primary purpose of a Kubernetes liveness probe?

1) Determine whether an application should be restarted
2) Assign users to deployment groups
3) Store application secrets
4) Create source branches

Correct Answer: 1)

Explanation:

A Kubernetes liveness probe helps determine whether a container is still functioning properly. If the liveness check repeatedly fails according to the configured thresholds, Kubernetes can restart the affected container. This can help recover applications that have become unresponsive or entered an unhealthy state that cannot be corrected without restarting. A liveness probe differs from a readiness probe, which determines whether an application should receive traffic. Secrets are managed separately, while source branches are handled by version-control systems. Therefore, determining whether an application should be restarted is the primary purpose of a Kubernetes liveness probe.

Q392. Which Kubernetes resource is commonly used to define the desired number of application replicas?

1) Deployment
2) ConfigMap only
3) Service connection
4) Git repository

Correct Answer: 1)

Explanation:

A Kubernetes Deployment manages the desired state of a set of replicated application pods. The Deployment specification can define the desired number of replicas, container image, update strategy, and other deployment-related settings. Kubernetes continuously works to maintain the desired number of running replicas and can perform controlled rolling updates when the application definition changes. ConfigMaps store non-sensitive configuration data, while service connections and Git repositories are not Kubernetes resources for managing replica counts. Therefore, a Kubernetes Deployment is the appropriate resource for defining and maintaining the desired number of application replicas.

Q393. Which deployment strategy gradually replaces old application instances with new instances?

1) Rolling deployment
2) Big-bang deployment
3) Manual-only deployment
4) Source checkout

Correct Answer: 1)

Explanation:

A rolling deployment gradually replaces existing application instances with new versions rather than replacing everything simultaneously. This can reduce downtime and deployment risk because part of the application can continue serving users while new instances are being introduced. Health checks and rollout controls can help ensure that unhealthy instances are not promoted further. Rolling deployments are commonly supported by orchestration platforms such as Kubernetes. A big-bang deployment would replace the environment more abruptly, while source checkout simply retrieves code. Therefore, a rolling deployment is the strategy that gradually replaces old application instances with new ones.

Q394. Which deployment strategy maintains two separate environments so traffic can be switched between the current and new versions?

1) Blue-green deployment
2) Rolling deployment
3) Dependency scanning
4) Unit testing

Correct Answer: 1)

Explanation:

Blue-green deployment maintains two environments representing different application versions. The currently active environment serves production traffic, while the new version is deployed and validated in the other environment. Once validation is successful, traffic can be switched to the new environment. If a serious problem occurs, traffic can potentially be switched back to the previous environment, simplifying rollback. Rolling deployment gradually replaces instances within an environment instead of maintaining two complete environments. Dependency scanning and unit testing are quality and security practices rather than deployment strategies. Therefore, blue-green deployment is the correct strategy for maintaining two switchable environments.

Q395. Which technique gradually exposes a new application version to a small percentage of users before wider release?

1) Canary deployment
2) Full replacement
3) Source branching
4) Artifact retention

Correct Answer: 1)

Explanation:

Canary deployment introduces a new application version to a limited subset of users or traffic before expanding the release to the broader population. Teams can monitor application performance, errors, availability, and business metrics during the limited rollout. If the new version performs well, traffic can gradually increase; if significant problems appear, the rollout can be stopped or reversed while limiting the number of affected users. This approach provides a controlled way to validate releases in realistic conditions. Full replacement exposes all users immediately, while branching and artifact retention address other parts of the DevOps lifecycle. Therefore, canary deployment is the appropriate strategy.

Q396. Which monitoring metric is especially useful for determining whether a deployed application is experiencing an increase in failures?

1) Error rate
2) Branch count
3) Package name
4) Sprint capacity

Correct Answer: 1)

Explanation:

Error rate measures the proportion or frequency of requests, operations, or transactions that fail. Monitoring this metric after deployment can help teams quickly determine whether a release has introduced reliability problems. A sudden increase in errors may indicate application defects, dependency failures, configuration problems, or infrastructure issues. Teams often combine error-rate monitoring with latency, availability, resource utilization, and business metrics to gain a more complete understanding of application health. Branch count, package names, and sprint capacity do not directly indicate production reliability. Therefore, error rate is an important monitoring metric for identifying increases in application failures.

Q397. Which Azure service provides centralized monitoring and analysis of logs using Kusto Query Language?

1) Azure Log Analytics
2) Azure Boards
3) Azure Repos
4) Azure Artifacts

Correct Answer: 1)

Explanation:

Azure Log Analytics provides a centralized workspace for collecting and analyzing telemetry and log data using Kusto Query Language, commonly called KQL. DevOps teams can use KQL queries to investigate application behavior, infrastructure events, failures, and performance information. Centralized logs are particularly valuable during incident investigation because engineers can correlate information from multiple services and resources. Azure Boards manages work items, Azure Repos manages source code, and Azure Artifacts manages packages. Therefore, Azure Log Analytics is the appropriate Azure service for centralized log analysis using KQL.

Q398. Which Azure Monitor feature determines what action should occur when an alert is triggered?

1) Action group
2) Workbook query
3) Resource tag
4) Deployment slot

Correct Answer: 1)

Explanation:

An Azure Monitor action group defines the actions that should occur when an alert rule is triggered. Actions can include sending notifications through supported channels or invoking automated responses, depending on the configured integration. Separating alert conditions from notification or response actions allows the same action group to be reused across multiple alerts. This can simplify monitoring configuration and help standardize incident notification processes. Workbooks provide interactive monitoring and visualization, while resource tags organize resources and deployment slots support application deployment strategies. Therefore, an action group is the appropriate Azure Monitor feature for defining responses to triggered alerts.

Q399. Which Azure Monitor feature provides interactive visualizations that can combine multiple monitoring queries and metrics?

1) Workbooks
2) Action groups
3) Branch policies
4) Package feeds

Correct Answer: 1)

Explanation:

Azure Monitor Workbooks provide interactive reports and visualizations that can combine metrics, logs, queries, and other monitoring information into a single interface. Teams can use workbooks to create operational dashboards for applications, infrastructure, incidents, and performance analysis. Because workbooks can present information from multiple sources, they are useful for troubleshooting and operational reviews. Action groups perform notification or automated-response actions when alerts fire, while branch policies govern source-code changes and package feeds manage software packages. Therefore, Workbooks are the appropriate Azure Monitor feature for creating interactive monitoring visualizations.

Q400. Which DevOps practice uses telemetry and operational data to continuously improve future releases?

1) Continuous improvement
2) Manual configuration only
3) Untracked deployment
4) Source deletion

Correct Answer: 1)

Explanation:

Continuous improvement uses feedback from development activities, deployments, incidents, customer behavior, and operational telemetry to improve future processes and releases. DevOps teams can analyze metrics such as deployment frequency, change failure rate, recovery time, application errors, and performance trends to identify opportunities for improvement. Findings can then be converted into actionable work, such as improving tests, modifying deployment strategies, enhancing monitoring, or addressing recurring defects. Continuous improvement helps organizations evolve rather than treating each release as an isolated event. Therefore, using telemetry and operational data to improve future releases is an important DevOps continuous improvement practice.