Given a Scenario, Design a Solution That Leverages Programmatic Sharing Functionalities to Achieve a Requirement That Cannot Be Met Using Declarative Functionality. SHARING-AND-VISIBILITY-ARCHITECT Practice Questions (Page 3)

Questions 11–15

1. 11foundation · easy

   When designing an Apex managed sharing solution, what is the primary reason to use a custom 'SharingReason' (e.g., 'SharingReason__c')?

   • ATo identify and manage a specific set of shares created by your Apex code.
   • BTo allow the share to be automatically recalculated by the system.
   • CTo increase the governor limit for sharing records in a transaction.
   • DTo grant a higher level of access than the default 'Edit' access.
   Reveal Solution Discussion Select an answer first
2. 12foundation · easy

   Which Apex class is used to create sharing records for a custom object in Apex managed sharing?

   • ACustomObject__Share
   • BCustomObject__Access
   • CCustomObject__SharingRule
   • DCustomObject__cShare
   Reveal Solution Discussion Select an answer first
4. 13application · medium

   A multinational company uses a custom object 'Project__c' with Private OWD. Project managers need read access to projects that are in the same region as their own 'Region__c' field, but the region is stored on the user record. The company has thousands of users and projects. Which solution should an architect recommend?

   • ACreate a sharing rule on Project__c that shares records with a public group of users based on the user's Region__c field.
   • BChange the OWD to Public Read Only and use field-level security to hide projects from users in other regions.
   • CUse Apex managed sharing with a trigger that creates a Project__Share record for each user whose Region__c matches the project's region.
   • DUse manual sharing to allow each project manager to share their projects with other managers in the same region.
   Reveal Solution Discussion Select an answer first
5. 14expert · hard

   A company uses Apex managed sharing on a custom object 'Order__c' to grant access to a 'SalesOps' group when the order's 'Priority__c' is 'High'. The sharing is implemented in a trigger. Recently, the company noticed that some orders with 'High' priority are not accessible to the SalesOps group, and some orders with 'Low' priority are still accessible. The trigger logic appears correct. What is the most likely cause of this inconsistency?

   • AThe trigger deletes all shares and recreates them, but the recalc job runs too frequently.
   • BThe trigger uses a sharing reason that is not active.
   • CThe trigger uses the wrong object for the share record, such as OrderItem__Share instead of Order__Share.
   • DThe trigger only runs on insert, not on update, so priority changes are not handled.
   Reveal Solution Discussion Select an answer first
6. 15expert · hard

   A company uses Apex managed sharing on a custom object 'Application__c' to grant access to a 'Reviewer' group when the application's 'Score__c' is above 80. The sharing is implemented in a trigger. The company also has a batch job that updates the Score__c field for many applications at once. After the batch job runs, some applications with a score above 80 are not accessible to the Reviewer group. What is the most likely cause?

   • AThe batch job runs in a different context that bypasses triggers.
   • BThe trigger does not handle the 'after update' event, so score changes are not processed.
   • CThe trigger deletes all shares and recreates them, but the batch job runs too quickly.
   • DThe trigger uses a sharing reason that is not active.
   Reveal Solution Discussion Select an answer first