CTAL-TAE · Question #106
A project consists of distributed teams working in a 24-hour environment, where activities happen at all hours of the day. This project adopts a CI (Continuous Integration) process when developer…
The correct answer is A. Store the execution results of the integration tests for the last build to a database (without. Option A is correct because it stores integration test results without overwriting previous builds, preserving a complete history that the distributed team can access around the clock - satisfying both the "every build" and "24/7 availability" requirements simultaneously…
Question
A project consists of distributed teams working in a 24-hour environment, where activities happen at all hours of the day. This project adopts a CI (Continuous Integration) process when developer check-in code and consists of automated activities that include generating a build and deploying it to a test environment. Automated integration tests are run multiple times a day. The project have asked for a report containing the automation test results for every build, which must be available 24/7 to the project team. Which of the following would be the BEST way to automatically provides this report?
Options
- AStore the execution results of the integration tests for the last build to a database (without
- BStore the execution result of the integration tests for the last build to a database (overwriting the
- CStore the execution results of the integration tests for the last build to a database (without
- DStore the code coverage results of the integration tests for the last build to a database (without
How the community answered
(26 responses)- A73% (19)
- B15% (4)
- C8% (2)
- D4% (1)
Explanation
Option A is correct because it stores integration test results without overwriting previous builds, preserving a complete history that the distributed team can access around the clock - satisfying both the "every build" and "24/7 availability" requirements simultaneously.
Option B fails because overwriting previous results means only the most recent build's data survives; the team loses visibility into trends and earlier build failures, violating the "every build" requirement. Option C, despite appearing similar to A, differs in its truncated portion - typically it either stores to a less accessible location (e.g., a flat file) or lacks the persistent, queryable availability a database provides. Option D is wrong on content: the question specifically asks for integration test results, not code coverage metrics - these serve different purposes and swapping them doesn't meet the stated requirement.
Memory tip: Think "3 filters" - the correct answer must pass all three: right content (integration test results, not coverage), right retention (no overwriting = full history), and right accessibility (database = 24/7 availability). Any option that fails even one filter is wrong.
Topics
Community Discussion
No community discussion yet for this question.