Why should you restrict exporting in Confluence?

• A. Because exports can degrade system performance
• B. Because it increases security risks
• C. Because it does not affect performance
• D. Because it is mandatory to export only by admins

Answer: (A)

Exporting content in Confluence is resource-intensive. When you generate exports—especially for large spaces or many pages—Confluence has to render pages, process macros, gather attachments, and build the output file. That consumes CPU, memory, and disk I/O. On a busy instance, a big export can compete with regular user activity, slowing page loads, searches, and other operations, and in worst cases can cause timeouts. Limiting who can trigger exports helps keep the system responsive for everyone, so restricting exporting is mainly about maintaining good performance across the instance.

The other ideas aren’t as fitting here. Exporting does impact performance, so saying it doesn’t is inaccurate. Security concerns exist around exporting sensitive content, but the question focuses on performance impacts. And exporting isn’t inherently mandatory to be admin-only by default—the policy being discussed is about performance, not a strict admin-only rule.