Valid Workday-Prism-Analytics Dumps shared by ExamDiscuss.com for Helping Passing Workday-Prism-Analytics Exam! ExamDiscuss.com now offer the newest Workday-Prism-Analytics exam dumps, the ExamDiscuss.com Workday-Prism-Analytics exam questions have been updated and answers have been corrected get the newest ExamDiscuss.com Workday-Prism-Analytics dumps with Test Engine here:
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?
Correct Answer: B
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