How might a report output type of PDF be secured?

Question

Options

• Aby setting a password in the schedule PDF options
• Bby giving the PDF a name that starts with "confidential'
• Cby selecting the "Secure this Report" option in the report properties
• Dby specifying a PDF encryption code in the schedule settings

• A
  3% (1)
• B
  6% (2)
• C
  90% (28)

Explanation

Selecting "Secure this Report" in the report properties (C) is the correct approach because it applies security settings directly to the report itself as a built-in feature of the reporting tool, ensuring the PDF is protected regardless of how or when it's generated.

Why the distractors are wrong:

• A is incorrect because schedule PDF options control delivery timing and format, not security - password protection at the schedule level (if it even exists) is not the standard mechanism for securing report output.
• B is incorrect because file naming conventions have no effect on actual security; naming a file "confidential" is an informal label, not a technical control.
• D is incorrect because there is no standard "PDF encryption code" field in schedule settings - encryption is handled through the report's own security properties, not a code entered at scheduling time.

Memory tip: Think of it as "locking the door at the source" - security belongs in the report properties (where the report lives), not in the delivery schedule or the file name.

No community discussion yet for this question.