A Prism administrator wants to hide a field that contains employee salary information but still...

Comprehensive and Detailed Explanation From Exact Extract:

In Workday Prism Analytics, hiding a field is a common practice to control access to sensitive information while still allowing necessary analytics to be performed. According to the official Workday Prism Analytics study path documents, the primary reason for hiding a field like employee salary information is to protect sensitive data. Employee salary is considered personally identifiable information (PII) or sensitive data, and hiding the field ensures that individual salary details are not exposed to unauthorized users or in published data sources. However, by hiding the field, Prism data writers can still use it in calculations—such as computing the average salary by cost center—because hidden fields remain accessible for transformation and aggregation purposes within the dataset but are not visible in the final output or to end users of the published data source.

The other options do not align with the scenario:

B. To hide Prism-calculated fields used for interim processing: The salary field is a base field, not a calculated field used for interim processing, so this reason does not apply.

C. To hide unpopulated or sparse data fields: There is no indication that the salary field is unpopulated or sparse; the concern is about its sensitivity, not its data quality.

D. To use computed values instead of base values: Hiding the field does not inherently involve replacing it with computed values; the goal is to restrict visibility while still allowing computations like averages.

Hiding the salary field protects sensitive data while enabling aggregated analytics, aligning with Prism’s security and governance capabilities.