The page is published. Can your colleague find it?
You know where the page lives because you wrote it. A colleague arrives later with a question, not the title or the memory of the meeting. They search, find two similar pages, and ask in chat which one to use.
That is a useful way to think about Confluence Essentials. Creating content is part of the work; organizing it and collaborating around it are just as important. These six tests help you examine those everyday decisions in context, with explanations that connect the feature to the reader's task.
Make the content work for someone else
Page topics cover creation, editing, formatting, and structure. Spaces provide context for grouping and navigation. Comments, mentions, sharing, and feedback support collaboration without requiring every conversation to become another disconnected page.
Labels, search, and maintenance help content remain findable as the space grows. The questions encourage you to distinguish mechanisms that can seem interchangeable: a page hierarchy is not the same as a cross-project label, and a direct link does not solve the longer-term problem of knowing where the information belongs.
The level stays practical and foundational. You are reviewing how to make an understandable page, place it appropriately, choose its audience, and help another person continue the work. The objective is not to turn every author into a global Confluence administrator.
Practice format
Six short tests covering core Confluence Cloud workflows.
You get 6 practice tests, with 30 questions in each test (180 questions in total).
The course language is English, and the course level is Foundational.
Is this the right fit?
For new and everyday Confluence users, team members preparing for ACA-920, and professionals consolidating content and collaboration skills. Use the course alongside the current official learning path. Choose an administration-focused resource instead for global controls, complex permission design, or a migration project.
A sample of the reasoning
A team publishes weekly decision pages across several projects and wants an easy way to find them together without reorganizing every page tree. Which approach best fits?
Use a consistent label and a search or view that collects those pages.
Move every decision page into one parent regardless of its project context.
Restrict the pages so only the reporting owner can open them.
Copy the full text of every decision into a second central collection.
Best answer: A. A creates a shared way to find the pages while preserving their useful project context. A single parent may unnecessarily disrupt organization, restrictions do not solve retrieval, and copied content creates a second set to maintain. The distinction is between giving content a home and providing another reliable route to it.
Illustrative public-page example, reworded for this edition; not a live examination item.
Use the reader's task to explain your answer
When reviewing a miss, ask whether the problem concerned creating content, finding it, collaborating, or keeping it understandable over time. Explain what the proposed feature changes for the reader. Then revisit that part of the official learning material. Keep correct guesses in the review and return to a fresh test only after you can describe the relationship without relying on a button label.
Related Field Notes
Continue exploring
More Confluence and Atlassian administration practice tests.
ACP 220 Confluence Administration for Cloud 6 Practice Tests
Advanced Confluence administration practice across access, spaces, content lifecycle, global settings, and integrations. Focus on the effect of a configuration choice, not only where its setting lives.
ACP-520 Exam: 6 Practice Tests - Atlassian Cloud Org Admin
Organization-administration practice in identity, access, domains, policies, and Cloud governance. Review the April 2026 refresh separately from the older 65-question practice-session format.
ACP-120 Exam: 6 Practice Tests Jira Administrator for Cloud
Advanced Jira Cloud administration practice focused on configuration relationships and shared impact. Work through permissions, schemes, fields, screens, workflows, and cross-project diagnosis.