Sensitive salary information must be protected through data-level authorization , not merely hidden through visual formatting. The supplied source therefore correctly identifies security applied to the report's data access together with appropriate user or role permissions as the strongest approach.

Oracle Publisher security separates access to functionality, catalog objects, and data sources. Roles can be granted or denied access to particular data sources, while catalog permissions determine who may read or execute report objects. For more granular row-level protection, Publisher can also work with database-enforced mechanisms such as Virtual Private Database policies, as covered elsewhere in the source.

Conditional Formatting is only a presentation mechanism. Hiding a salary column visually doesn't constitute access control if the unauthorized data is still retrieved or otherwise available in report output. Personal Folders restrict catalog sharing but aren't a scalable data-security architecture, and disabling scheduling doesn't affect online access to salary information.

Accordingly, security should be applied at the data-access/data-model layer and reinforced with role-based permissions , making A the correct answer.

Reference Topic: Managing and Securing Oracle Analytics Publisher — Data Access Security and Report Authorization

===============