問題文
A field service company holds 80 million work order records. The compliance team requires that technicians see only their own region's work orders, so the organization wide default is private and access is granted by several dozen sharing rules. Report and list view response times are degrading month by month. Which effect should the architect anticipate as record volume keeps growing?
選択肢
- A restrictive model has no effect on read performance, because visibility is applied after the rows have been returned, so the growth in the work order volume is the whole explanation for the response times the team is seeing.
- Visibility has to be resolved for the rows a query considers, so the same query costs more under a restrictive model than under an open one, and the sharing data itself grows with users, groups, and rules.
- Making the model restrictive turns every query into a search of the text index rather than a database read, so the only way to recover performance is to set the object to public read only and then hide the sensitive fields with field level security on each profile.
- A restrictive model speeds reads up because each user sees fewer rows, so the slowness must come from something other than the sharing configuration, and the several dozen rules narrow each query before it reaches the 80 million rows.