A Prism data writer has to create an intermediary Prism calculated field A, used only to achieve a final result in Prism calculated field B and they only need to publish out field B. What should they do?

• A. Add a Manage Fields stage to the DDS and hide field A.
• B. Add a Manage Fields stage to the DDS and hide field B.
• C. Mark field A as intermediate calculation.
• D. Delete field A from their DDS and just leave field B.

A report that uses a Prism data source that you created has a brand new requirement that Expense Partner by Location should only see expense reports for workers for the locations they support. Given that you have the Location Hierarchy (instance) field in your dataset used for publishing, how can you adjust to meet the requirement?

• A. Run the Edit Data Source Security task to update the Securing Entities.
• B. Run the Edit Data Source Security task to update row-level security.
• C. Run the Edit Data Source Security task to update row-level security and then republish the PDS.
• D. Run the Edit Data Source Security task to update the Securing Entities and then republish the PDS.

You are a new Prism customer and you want to ensure the correct set of fields is brought into a derived dataset. When should you apply a Manage Fields stage?

• A. After the dataset is published.
• B. At the beginning of the Primary Pipeline of the derived dataset.
• C. At the end of the Primary Pipeline of a published dataset.
• D. At the beginning of the primary pipeline of the Base Dataset.

You want to configure access to a published Prism data source to use it in reporting and discovery boards.
What action must you take?

• A. Edit the data source security and select a domain.
• B. Share the imported Workday report to provide users with access to the published Prism data source.
• C. Schedule the recurring publish process.
• D. Share the dataset with appropriate users.