TWC Practice Questions
Prepare for TWC with more than an answer.
- Exam fee
- $200 USD
- Level
- Specialist Designation
- Valid for
- Maintained as long as all four component credentials remain active
Domains covered on the exam 18
- Working with Work Items37%
- Issue Lifecycle, Workflow, and Boards24%
- Basic Concepts21%
- Jira Navigation15%
- Rovo Basics (in Jira)3%
- Creating Pages and Basic Editing32%
- Working with Pages32%
- Advanced Editing16%
- Intro to Confluence Terms and Navigation12%
- Advanced Features8%
- Creating and Editing Videos36%
- Sharing and Collaborating32%
- Managing Content and Settings20%
- Overview of Loom12%
- Rovo Basic Operations39%
- Agents23%
- Search20%
- Chat18%
- 1
A Product Owner has created a highly customized Jira Dashboard containing multiple Filter Results gadgets to track sprint progress. When sharing this dashboard with the development team, several team members report that the gadgets display "The filter configured for this gadget could not be retrieved" errors. What is the most likely cause of this issue?
Show answer details
Correct answer: B
When a dashboard is shared, the filters powering the gadgets on that dashboard are NOT automatically shared. The filter owner must manually update the share permissions of the specific JQL filters so the target audience can access the data.
- 2
True or False: To utilize Rovo's AI-powered search capabilities directly within the Jira issue navigator, a Jira Administrator must first enable Atlassian Intelligence at the organization level.
Show answer details
Correct answer: A
Rovo is deeply integrated with Atlassian Intelligence. For users to access Rovo's AI search and chat features within Jira, an organization admin must explicitly activate Atlassian Intelligence in the administration settings.
- 3
As a Scrum Master configuring a new company-managed project, you notice that team members are creating standard 'Task' issue types to represent granular technical steps for a 'Story', rather than using sub-tasks. Which statement accurately describes the hierarchical restriction of sub-tasks in Jira that makes them structurally different from standard Tasks?
Show answer details
Correct answer: A
In Jira's hierarchy, sub-tasks are strictly child issues that must be associated with a standard parent issue (like a Story, Bug, or Task). They cannot exist as standalone items in a backlog, whereas standard Tasks can.
- 4
While planning a complex release, a Release Manager needs to map dependencies between three teams. Issue A must be completed before Issue B can start, and Issue C is a duplicate of Issue B. Which combination of issue links correctly establishes this exact relationship?
Show answer details
Correct answer: B
This correctly establishes the directional dependency (A must finish before B) and the specific duplicate relationship (C is a duplicate of B).
graph TD A[Issue A] -- blocks --> B[Issue B] B -- is blocked by --> A C[Issue C] -- duplicates --> B
