Objective: Apply Test Automation at Different Test Levels Within Pipelines CTAL-TAE Practice Questions (Page 1)

Questions 1–5

1. 1expert · hard

   A team stores test automation code in a separate repository from the application code. They want to ensure that test code changes are compatible with the application code in the pipeline. Which approach best ensures this compatibility?

   • AAlways use the latest version of the test code from the main branch, regardless of the application version.
   • BUse a pipeline that checks out both the application and test code at the same commit or version, and run tests against that combination.
   • CStore test code in the same repository as the application code to avoid version mismatches.
   • DManually coordinate test code and application code releases, and update the pipeline configuration each time.
   Reveal Solution Discussion Select an answer first
2. 2expert · hard

   A pipeline has a quality gate that requires all unit and integration tests to pass before a build can be promoted to staging. The team has noticed that the integration tests are slow and often fail due to environment issues, causing delays. They want to maintain the quality gate while reducing delays. Which approach best achieves this?

   • ARun unit tests as a fast gate for every commit, and run integration tests as a separate gate only for builds that pass the unit tests.
   • BIncrease the timeout for integration tests to reduce the chance of environment-related failures.
   • CRemove the integration tests from the quality gate and run them only in a nightly pipeline.
   • DRun integration tests in parallel with unit tests to reduce overall pipeline time.
   Reveal Solution Discussion Select an answer first
4. 3foundation · easy

   Which pipeline stage is typically used to verify that newly integrated code does not break existing functionality by running a broad set of regression tests?

   • ARegression test stage
   • BSecurity scan stage
   • CCompilation stage
   • DDeployment stage
   Reveal Solution Discussion Select an answer first
5. 4application · medium

   A team maintains a separate repository for test automation code. They want to ensure that changes to the test code are automatically validated when a pull request is created. Which version control integration practice best supports this?

   • AStore test code in the same repository as the application code and run tests only on application code changes.
   • BConfigure the pipeline to trigger a test build and run a subset of tests on every pull request to the test repository.
   • CMerge test code changes directly to the main branch without any pipeline triggers, and run tests only during the nightly build.
   • DRequire manual approval before any test code change is merged, without running any automated checks.
   Reveal Solution Discussion Select an answer first
6. 5application · medium

   A team is setting up a CI/CD pipeline for a web application. They want to run unit tests as early as possible to catch defects quickly, but they also need to run integration tests that require a database and a message broker. Which pipeline stage placement best satisfies both goals?

   • ARun unit tests in the build stage and integration tests in a later test stage after provisioning the required services.
   • BRun all tests in a single test stage after deployment to production to test the real environment.
   • CRun both unit and integration tests in the build stage on the same machine to minimize pipeline duration.
   • DRun integration tests in the build stage and unit tests in the test stage to ensure the environment is ready for the slower tests.
   Reveal Solution Discussion Select an answer first