Which two macros work together to create a table of information drawn from multiple pages?

Prepare for the Confluence Admin Certification exam. Use quizzes and multiple choice questions with explanations to master the key concepts. Ace your certification!

Multiple Choice

Which two macros work together to create a table of information drawn from multiple pages?

Explanation:
The idea being tested is how to collect structured metadata from many pages into a single table. This is achieved by placing a Page Properties macro on each page to define a small, consistent set of fields (like Status, Owner, Due Date, Priority), and then using a Page Properties Report macro on a summary or index page to gather those fields from all pages that match a scope (space, label, or other criteria) and render them as one table. The report macro reads the Page Properties data from each included page and lays out the fields as columns, with each row representing a different page. This pairing is specifically designed for building dashboards or inventories that pull metadata from multiple pages in a unified view. The other options don’t fit this pattern. Include Page pulls content from another page into the current page, but doesn’t aggregate and display a table of metadata from multiple pages. Content by label can list content based on labels, but it isn’t built around standardized Page Properties fields to form a cross-page table. The remaining combinations concern navigation or label listing rather than creating a consolidated properties table across pages.

The idea being tested is how to collect structured metadata from many pages into a single table. This is achieved by placing a Page Properties macro on each page to define a small, consistent set of fields (like Status, Owner, Due Date, Priority), and then using a Page Properties Report macro on a summary or index page to gather those fields from all pages that match a scope (space, label, or other criteria) and render them as one table. The report macro reads the Page Properties data from each included page and lays out the fields as columns, with each row representing a different page. This pairing is specifically designed for building dashboards or inventories that pull metadata from multiple pages in a unified view.

The other options don’t fit this pattern. Include Page pulls content from another page into the current page, but doesn’t aggregate and display a table of metadata from multiple pages. Content by label can list content based on labels, but it isn’t built around standardized Page Properties fields to form a cross-page table. The remaining combinations concern navigation or label listing rather than creating a consolidated properties table across pages.

Subscribe

Get the latest from Examzify

You can unsubscribe at any time. Read our privacy policy