Exam Workday-Prism-Analytics Topic 1 Question 9 Discussion

Actual exam question for Workday's Workday-Prism-Analytics exam
Question #: 9
Topic #: 1
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?

Suggested Answer: B Vote an answer

Comprehensive and Detailed Explanation From Exact Extract:
In Workday Prism Analytics, restricting access to specific rows in a Prism data source (PDS) based on afield like Location Hierarchy for users such as Expense Partners requires implementing row-level security.
According to the official Workday Prism Analytics study path documents, to meet the requirement that Expense Partners only see expense reports for the locations they support, you should run the Edit Data Source Security task to update row-level security and then republish the PDS (option B).
The Location Hierarchy (instance) field in the dataset can be used to define row-level security rules, ensuring that each Expense Partner only sees data for their assigned locations. The Edit Data Source Security task allows you to configure row-level security by mapping the Location Hierarchy field to the user's security profile (e.g., their assigned locations). After updating the security settings, republishing the Prism data source is necessary to apply the changes, ensuring the updated security rules take effect in the reports that use the data source.
The other options are incorrect:
* A. Run the Edit Data Source Security task to update the Securing Entities and then republish the PDS:
Securing Entities are used to control overall access to the data source (e.g., via security domains), not to restrict data at the row level based on a field like Location Hierarchy.
* C. Run the Edit Data Source Security task to update row-level security: While updating row-level security is correct, the changes will not take effect in reports until the data source is republished, making this option incomplete.
* D. Run the Edit Data Source Security task to update the Securing Entities: As with option A, updating Securing Entities does not address row-level security for location-based restrictions.
Updating row-level security and republishing the PDS ensures that Expense Partners only see the relevant expense reports, meeting the requirement while maintaining security governance.
References:
Workday Prism Analytics Study Path Documents, Section: Security and Governance in Prism, Topic:
Implementing Row-Level Security in Prism Data Sources
Workday Prism Analytics Training Guide, Module: Security and Governance in Prism, Subtopic: Configuring Row-Level Security for Location-Based Access

by Vicky at Apr 18, 2026, 11:52 AM

Comments

Chosen Answer:
This is a voting comment (?) , you can switch to a simple comment.
Switch to a voting comment New
Nick name: Submit Cancel
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

0
0
0
10