701.2 Standard Components and Platforms for Software (weight: 3) DEVOPS-TOOLS-ENGINEER Practice Questions (Page 2)

Questions 6–10

1. 6foundation · easy

   What is the primary goal of continuous integration (CI)?

   • ATo deploy every code change directly to production without manual approval.
   • BTo automatically build and test code changes as they are integrated into a shared repository.
   • CTo manually review every line of code before it is committed.
   • DTo store compiled binaries in a central artifact repository.
   Reveal Solution Discussion Select an answer first
2. 7expert · hard

   A company is migrating from a centralized version control system to Git. They have a large codebase with a long history. They want to preserve the existing history and allow developers to work offline. They also want to enforce a code review process before changes are merged into the main branch. Which migration and workflow strategy best meets these requirements?

   • AKeep the centralized VCS and use Git only for new projects.
   • BUse Git but allow direct commits to main and rely on post-commit reviews.
   • CStart a new Git repository without history and use a centralized workflow.
   • DUse a migration tool to convert the repository to Git, then adopt a feature-branch workflow with pull requests and branch protection.
   Reveal Solution Discussion Select an answer first
4. 8application · medium

   A team uses a shared main branch. A developer accidentally pushed a commit with a syntax error directly to main, breaking the CI build for everyone. The team wants to prevent this from happening again while keeping the workflow simple. Which action best addresses the problem?

   • ACreate a new branch for each developer and merge to main only at the end of the sprint.
   • BAsk developers to run tests locally before pushing, and rely on peer review after the fact.
   • CEnable branch protection on main so all changes require a pull request and passing CI checks before merging.
   • DSwitch to a centralized version control system to have better control over commits.
   Reveal Solution Discussion Select an answer first
5. 9expert · hard

   A company runs a microservices application on Kubernetes. They want to implement monitoring and logging to quickly identify the root cause of failures. They need to correlate metrics, logs, and traces across services. They also want to set up alerts based on service-level objectives (SLOs). Which approach best meets these requirements?

   • AUse Prometheus for metrics, Grafana for dashboards and alerts, and Jaeger for distributed tracing, with centralized log aggregation.
   • BUse Kubernetes built-in monitoring only.
   • CUse only a log aggregation tool like ELK.
   • DUse only a metrics tool like Prometheus.
   Reveal Solution Discussion Select an answer first
6. 10application · medium

   A development team frequently integrates code changes, but they do not have an automated build or test process. As a result, integration errors are discovered late and fixing them takes significant time. They want to adopt a practice that detects integration issues early and provides rapid feedback. Which practice should they implement?

   • ADeploying to production after each merge.
   • BManual code reviews before merging.
   • CNightly builds with manual testing.
   • DContinuous integration with automated builds and tests triggered on every commit.
   Reveal Solution Discussion Select an answer first