Exam Certified Tableau CRM and Einstein Discovery Consultant topic 1 question 51 discussion

Sharing works on row level, there is no field level security in CRM Analytics.

B because they don't talk about field access in sharing inheritance only rows

Both B and C are possible solutions. We would have to understand better the criteria to hide/show that specific field to tell more precisely what is the correct solution. But... considering that both are servicable, the best option is C, in my opinion.

Option C: Tableau CRM consultant can add the new field to the existing dataset and apply "Security Predicates" to it. This way, the new field will only be visible to users who have the necessary permissions to access it. Option A is incorrect because XMD file parameters are used to define how Tableau CRM interprets data from a dataset, not to restrict access to specific fields. Option B is not an optimal solution because it involves creating a new dataset which could lead to data redundancy and maintenance issues. Option D is also incorrect because activating "Sharing inheritance" in the Account object will not restrict access to specific fields within a dataset.

I think the answer is B ... that's because in CRM Analytics you can't control field level security even if you enable "Sharing Inheritance", Hence, you have to create a new dataset and restrict access to only users who are able to view that field.

"Sharing inheritance" will restrict more than just the "CardBalance" field, because it acts on the row level.

B, I believe. You can prove me wrong. A : XMD is not meant for security access B : It would work that there are 2 datasets with/without the new field C : using security predicate acts on the row-level security. It would indeed restrict access but the restriction would be too broad. D : same for C : the restriction would be too broad on row-level, and not only column. Also I believe sharing inheritance acts on record-sharing, not on field-sharing (it is written : [...] only users who have access to the field [...], which is wrong)

Ignore my previous answer. I think option D is correct based on that we should NOT hide the field, only "limit the users who are able to VIEW that field's data". So the field can still be visible in the dataset.

Correct!