Download Zephyr Release Manager Practice Exam and more Exams Technology in PDF only on Docsity!
Question 1. Which of the following best describes a time‑based release cycle in Zephyr? A) Releases are triggered only when a specific feature set is completed. B) Releases occur at fixed intervals regardless of feature completion. C) Releases are based on the number of test cases executed. D) Releases depend on the number of defects found. Answer: B Explanation: A time‑based cycle (e.g., every 6 months) follows a calendar schedule, independent of feature readiness. Question 2. In Zephyr, the “Definition of Done” for a release should NOT include which element? A) All functional requirements verified. B) Performance benchmarks met. C) All test cases marked as “Not Run”. D) Security standards satisfied. Answer: C Explanation: “Not Run” test cases indicate incomplete verification, contradicting a “Done” definition. Question 3. How does Zephyr synchronize releases with Jira versions? A) By manually copying version names. B) Using the “Link Jira Version” feature to map Zephyr releases to Jira versions. C) By exporting releases to CSV and importing into Jira. D) Zephyr cannot synchronize with Jira versions. Answer: B Explanation: The built‑in integration lets you map Zephyr releases directly to Jira versions for alignment.
Question 4. Which resource allocation strategy helps balance testing workload across multiple teams? A) Assign all test cycles to a single lead tester. B) Distribute test cycles based on team expertise and capacity. C) Randomly assign test cases without considering skill sets. D) Allocate resources only after the release is complete. Answer: B Explanation: Matching expertise and capacity ensures efficient test execution and higher quality. Question 5. A rollback plan is primarily used for which purpose? A) To add new features after release. B) To revert the system to a stable state if a release fails. C) To increase test coverage. D) To generate release notes. Answer: B Explanation: Rollback plans define steps to restore the previous stable version when a release introduces blockers. Question 6. When defining a feature‑driven release, which criterion is most critical? A) Calendar date. B) Completion of a predefined set of user stories. C) Number of test cycles executed. D) Total defect count. Answer: B Explanation: Feature‑driven releases are gated by the delivery of specific functionality, not by time.
Question 10. Which import format preserves test case hierarchy (folders, sub‑folders) when migrating into Zephyr? A) Simple CSV. B) Excel with separate sheets. C) Zephyr’s native ZIP archive. D) JSON with folder structure. Answer: D Explanation: JSON can encode nested folder structures, allowing hierarchy preservation during import. Question 11. What is the purpose of a “Test Plan” in Zephyr? A) To store raw test data only. B) To aggregate multiple test cycles and provide an overview of release testing. C) To replace Jira issues. D) To generate automated scripts. Answer: B Explanation: A Test Plan groups related cycles, giving a high‑level view of testing progress for a release. Question 12. When a test execution fails, what is the recommended immediate action in Zephyr? A) Delete the test case. B) Link the failure to a newly created defect in Jira. C) Change the status to “Pass”. D) Ignore the failure if the defect already exists. Answer: B
Explanation: Linking to a defect creates traceability and ensures the issue is tracked for resolution. Question 13. Which Zephyr feature allows tracking test results across different browsers? A) Test Steps. B) Environments. C) Labels. D) Priorities. Answer: B Explanation: Environments capture configuration details such as browser type, OS, and hardware. Question 14. How does Zephyr’s Automation API receive test results from Selenium? A) By reading Selenium logs directly. B) Through REST calls that push execution status to Zephyr. C) By importing CSV files after each run. D) Automation API does not support Selenium. Answer: B Explanation: The Automation API provides endpoints for external tools like Selenium to post results via REST. Question 15. Which CI/CD tool is NOT natively supported for Zephyr integration? A) Jenkins B) Bamboo C) GitLab CI D) Travis CI Answer: D
Answer: B Explanation: Defect density reflects how many defects are found relative to test effort, indicating stability. Question 19. Which Zephyr gadget would you add to a Jira dashboard to show real‑time pass/fail trends? A) Test Execution Summary Gadget. B) Sprint Burndown Gadget. C) Issue Statistics Gadget. D) Pie Chart Gadget. Answer: A Explanation: The Test Execution Summary visualizes pass/fail counts over time, ideal for release health monitoring. Question 20. For a technical audience, which report format is most appropriate after a release? A) High‑level executive summary with graphs. B) Detailed CSV export of every test step and result. C) One‑page slide deck with only pass percentages. D) A video walkthrough of the UI. Answer: B Explanation: Technical stakeholders often need granular data; a CSV provides full detail for deeper analysis. Question 21. Which Zephyr feature helps capture “lessons learned” after a release? A) Test Cycle Archive. B) Release Retrospective Report.
C) Test Plan Comments. D) Defect Resolution Time field. Answer: B Explanation: The Release Retrospective Report aggregates metrics and notes to support post‑release analysis. Question 22. In Zephyr, what is the effect of assigning a label to a test case? A) It changes the test case priority automatically. B) It enables bulk operations and easier filtering. C) It locks the test case from editing. D) It creates a new test cycle. Answer: B Explanation: Labels act as tags, allowing users to group, filter, and perform bulk actions on related test cases. Question 23. Which of the following is a best practice for writing test steps in Zephyr? A) Use ambiguous language to allow flexibility. B) Include only the expected result, not the action. C) Write clear, atomic actions followed by expected outcomes. D) Combine multiple actions into a single step. Answer: C Explanation: Atomic steps improve readability, reusability, and accurate defect linkage. Question 24. How does Zephyr handle version control for test cases? A) Test cases are immutable after creation. B) Each edit creates a new revision that can be reviewed in the history tab. C) Version control is only available for test cycles.
B) Browser version, OS, and hardware configuration. C) Defect severity. D) Sprint end date. Answer: B Explanation: Environments capture the specific test setup, such as browsers, OS, and hardware. Question 28. Which Zephyr API endpoint is used to create a new test execution record? A) /rest/api/2/issue B) /rest/api/2/execution/create C) /rest/api/2/testcase/create D) /rest/api/2/cycle/create Answer: B Explanation: The /execution/create endpoint allows external tools to post execution results. Question 29. What is the primary advantage of using a “Smoke” test cycle before a full regression cycle? A) It validates critical functionality quickly to determine if deeper testing is worthwhile. B) It replaces the need for regression testing. C) It increases the number of defects logged. D) It tests every possible user story. Answer: A Explanation: Smoke testing provides a quick health check, ensuring the build is stable enough for extensive testing. Question 30. Which of the following statements about Zephyr’s “Test Execution” status options is correct? A) “Blocked” can be used when a prerequisite test has not passed.
B) “Pass” automatically closes any linked defect. C) “Not Run” indicates the test was executed but failed. D) “WIP” is not a valid status in Zephyr. Answer: A Explanation: “Blocked” signals that execution cannot proceed due to external dependencies. Question 31. How can a Release Manager ensure that security testing is part of every release in Zephyr? A) By creating a dedicated “Security” test cycle and marking it mandatory in the release criteria. B) By ignoring security tests and handling them later. C) By assigning security tests to a separate project. D) By running security tests only when a vulnerability is reported. Answer: A Explanation: Defining a mandatory security cycle embeds security validation into the release process. Question 32. Which of the following is a key difference between a Test Plan and a Test Cycle in Zephyr? A) Test Plans store test cases; Test Cycles store defects. B) Test Plans aggregate multiple cycles; cycles are actual execution containers. C) Test Plans cannot be linked to releases. D) Test Cycles cannot be exported. Answer: B Explanation: A Test Plan provides a high‑level view, while each Test Cycle represents a specific execution batch. Question 33. When using Zephyr’s “Clone” feature on a test case, what is duplicated?
Question 36. Which action should be taken if a test case’s expected result changes due to a requirement update? A) Delete the test case and create a new one. B) Update the test case steps and expected result, and record the change in the revision history. C) Keep the old expected result to preserve historical data. D) Change the test case status to “Obsolete”. Answer: B Explanation: Updating the test case while preserving revision history maintains traceability. Question 37. What is the benefit of using the “Bulk Change” feature for test executions in Zephyr? A) It allows mass deletion of test cycles. B) It enables updating status, assignee, or environment for many executions simultaneously, saving time. C) It automatically generates defects for all failures. D) It merges multiple test plans into one. Answer: B Explanation: Bulk Change streamlines repetitive updates across many executions. Question 38. Which Zephyr dashboard gadget provides a visual representation of defect trends linked to test executions? A) Test Execution Burndown Gadget. B) Defect Trend Gadget. C) Pie Chart Gadget. D) Sprint Health Gadget. Answer: B
Explanation: The Defect Trend Gadget charts defect creation and resolution over time, showing testing impact. Question 39. When integrating Zephyr with Jenkins, which step is essential to ensure test results are posted back to Zephyr? A) Install the Zephyr for Jira plugin on the Jenkins server. B) Export test cases as CSV before each build. C) Manually copy results into Zephyr after each run. D) Disable Jenkins notifications. Answer: A Explanation: The Zephyr for Jira plugin provides the necessary hooks for Jenkins to push execution data. Question 40. In a release where multiple environments are used, how should a Release Manager organize test executions for clear reporting? A) Create a single test cycle for all environments. B) Create separate test cycles per environment and aggregate results in a Test Plan. C) Run tests only on the production environment. D) Use the same cycle but change the “Environment” field on each execution. Answer: B Explanation: Separate cycles per environment simplify tracking and enable environment‑specific reporting, while the Test Plan aggregates overall status. Question 41. Which of the following best illustrates a “Feature‑driven” release strategy? A) Releasing every two weeks regardless of work completed. B) Releasing when the “User Login” and “Dashboard” features are both marked as Done. C) Releasing after executing 10,000 test cases.
D) DELETE
Answer: B Explanation: POST creates a new execution record with the results sent from the automation tool. Question 45. Which of the following is a key indicator that a release is ready for “Go/No‑Go” decision? A) All test cycles are marked “Not Run”. B) Pass rate ≥ 95 % and no critical blockers. C) Number of test cases exceeds 500. D) All defects are still open. Answer: B Explanation: High pass rate and absence of critical blockers signal release readiness. Question 46. In Zephyr, what does the “Test Cycle Clone” operation facilitate? A) Copying an entire cycle’s configuration and test assignments to reuse for a new build. B) Deleting a cycle and its executions. C) Merging two cycles into one. D) Exporting the cycle to PDF. Answer: A Explanation: Cloning a cycle replicates its setup, saving time when the same test set is needed for a subsequent build. Question 47. Which of the following best describes a “Back‑out” plan? A) A schedule for adding new features after release. B) A predefined set of steps to revert the system to its previous state if the release fails. C) A method for increasing test coverage.
D) A communication plan for stakeholders. Answer: B Explanation: A back‑out plan outlines the reversal process to mitigate release risk. Question 48. How can a Release Manager enforce that test cases meet a minimum level of detail? A) By configuring a mandatory checklist in the test case template that requires steps, data, and expected results. B) By allowing testers to write free‑form notes. C) By disabling the “Description” field. D) By limiting test case creation to administrators only. Answer: A Explanation: Mandatory template fields ensure consistent, detailed test case documentation. Question 49. Which Zephyr report is most useful for identifying flaky tests that pass and fail intermittently? A) Execution History Report. B) Test Case Creation Report. C) Defect Aging Report. D) Sprint Velocity Report. Answer: A Explanation: Execution History shows pass/fail trends per test case, highlighting instability. Question 50. When linking a defect to a test execution, which Zephyr field captures the relationship? A) Linked Issue. B) Test Cycle.
A) Labels can be applied to multiple test cases simultaneously without affecting component hierarchy. B) Labels automatically change test case priority. C) Labels are visible only to administrators. D) Labels replace the need for folders. Answer: A Explanation: Labels are flexible tags that can be added or removed easily, unlike the more rigid component structure. Question 54. Which of the following best describes “Traceability” in the context of Zephyr? A) The ability to revert test cases to previous versions. B) Mapping test cases to requirements, defects, and builds to show coverage and impact. C) Exporting test results to Excel. D) Scheduling test cycles. Answer: B Explanation: Traceability ensures every requirement, defect, and build is linked to its corresponding test artifacts. Question 55. When configuring a Zephyr test cycle for “Sanity”, which scope should be selected? A) All test cases in the repository. B) A small subset of high‑risk test cases that verify basic functionality. C) Only performance tests. D) Only security tests. Answer: B Explanation: Sanity testing validates core functionality with a focused set of critical tests.
Question 56. Which Zephyr feature allows you to automatically assign test cases to testers based on their skill set? A) Auto‑Assignment Rules. B) Manual Assignment only. C) Random Assignment. D) Defect Assignment. Answer: A Explanation: Auto‑Assignment Rules can be configured to match test cases with testers’ expertise. Question 57. What does the “Defect Density” metric calculate in Zephyr? A) Number of defects per test case executed. B) Number of test cycles per release. C) Number of requirements per test case. D) Number of environments used. Answer: A Explanation: Defect density = total defects / total test cases executed, indicating quality. Question 58. Which of the following is a key consideration when importing test cases from an external CSV file? A) Ensuring the CSV includes a column for the Zephyr test case ID. B) Mapping CSV columns to Zephyr fields correctly (e.g., Summary, Steps, Expected Result). C) Importing only the first 10 rows. D) Deleting all existing test cases before import. Answer: B Explanation: Proper column mapping guarantees that data lands in the correct Zephyr fields.
