Sharing-and-Visibility-Architect Practice Exams and Training Solutions for Certifications
Dumps Free Test Engine Player Verified Answers
NEW QUESTION # 48
Dreamforce presenters need to be able to edit their presention details (summary, presenter biographies, etc) on a private custom object in Salesforce (Presentation). All presenters for a presentation are captured on a Presenters junction object between Presenter and User.
How can this be accomplished?
- A. Give Edit rights to the Presentation record via a Permission set that is given to the Presenters for a record.
- B. Trigger on Presenter junction object that uses Apex Managed sharing to add or remove access to the related Presentation record.
- C. Trigger on Presenter junction object that adds the user to the Sales Team for the Presentation record.
Answer: B
NEW QUESTION # 49
Universal Containers (UC) has a team that analyzes customer orders looking for fraud. This team needs access to Invoice records (Custom object, Private OWD). UC \as complex rules to control users' access. The Salesforce Architect recommended using Apex managed sharing to meet these requirements.
Which two recommendations should a Salesforce Developer consider when implementing the changes7 Choose 2 answers
- A. Use runAs system method to test different users accessing these records.
- B. Use "With Sharing" keyword to enforce field-level security.
- C. Use "Without Sharing" keyword to make sure record visibility will be considered.
- D. Use "With Sharing" keyword to make sure record visibility will always be considered.
Answer: A,D
Explanation:
Explanation
To implement Apex managed sharing, a Salesforce Developer should consider using the with Sharing keyword and the runAs system method. The with Sharing keyword ensures that the Apex class respects the record visibility rules of the current user context, which can help prevent unauthorized access to records that are not shared with the user1. The runAs system method allows testing the code as different users with different profiles and permissions, which can help verify that the sharing logic is working as expected2.
NEW QUESTION # 50
Universal Containers (UC) uses a custom Lightning component with an Apex class to display shipment information (custom object, Private organization-wide default). UC sales managers are complaining about two important points: Shipment records that belong to their teams can be seen by other users. Shipment amount should be visible only by managers, but sales reps are able to view it.
Which feature did the development team miss that is causing the problems?
- A. Use isShareable keyword in Apex classes to assure record visibility.
- B. Use isAccesible() method in Apex classes to check field accessibility.
- C. Use runAs in test class to enforce user permissions and field level permissions.
Answer: B
NEW QUESTION # 51
Partner users can access records belonging to users in their account at their same role or lower in the role hierarchy, for Cases, Leads, Opportunities and Custom Objects.
Which of the following access has to be given?
Answer:
Explanation:
Super user permission
Explanation
The access that has to be given to partner users to access records belonging to users in their account at their same role or lower in the role hierarchy, for Cases, Leads, Opportunities and Custom Objects is Super User Permission2. Super User Permission is a profile permission that enables partner users to act as super users for their accounts2. Super users can view, edit, and delete records that they do not own within their account.
NEW QUESTION # 52
By default, how many roles are created when the first external user is created on a partner account?
- A. 0
- B. 1
- C. 2
- D. 3
Answer: D
NEW QUESTION # 53
Universal Containers has expanded to sell virtual containers for data storage. Virtual container work orders are provisioned immediately by the system and therefore cannot be changed by a sales representative. What is an optimal approach to implement these requirements?
- A. Change the record type/page layout assignment for Work Order to be Read Only.
- B. Remove the Work Order Edit permission from the sales representative Profile.
- C. Implement a sharing rule that changes access for all Work Order to Read.
- D. Remove the edit button from the work order page layout.
Answer: B
Explanation:
Explanation
Removing the Work Order Edit permission from the sales representative profile is the optimal approach to implement these requirements, as it will prevent sales representatives from changing virtual container work orders that are provisioned immediately by the system. Option B is incorrect, since removing the edit button from the work order page layout would not prevent sales representatives from editing work orders using other methods, such as inline editing or data loader. Option C is incorrect, since changing the record type/page layout assignment for Work Order to be Read Only would not affect the edit permission, but only the layout configuration. Option D is incorrect, since implementing a sharing rule that changes access for all Work Order to Read would not prevent sales representatives from editing work orders that they own.
NEW QUESTION # 54
A sales rep (John) at Universal Containers requested to update information in an account record where he has Read-Only access. John requested the Edit access permission from the owner of the record (Paul). Paul manually shared the record with John.
Assuming the organization-wide default of the Account object is Public Read-Only, what is the impact in the system?
- A. New AccountShare record is created. Row Cause is "Manual" and Access Level is "Read/Write".
- B. Existing AccountShare record is updated. Row Cause is "Manual" and Access Level is "Read/Write".
- C. New AccountShare record is created. Row Cause is "Owner" and Access Level is "Full".
Answer: A
NEW QUESTION # 55
Universal Containers does not want the Users in the Custom Sales Department Profile to be able to delete Opportunities. How would the Architect prevent a certain set of users from deleting Opportunities?
- A. Override the Standard button with a Visualforce Page that warns them that they do not have permission to delete.
- B. Remove the Delete button from the Opportunity Page Layout and Record Type settings.
- C. Create a Validation Rule that checks the User's Profile before allowing the Is Deleted flag to be set to True.
- D. Remove the "Opportunity Delete" Permission from the Sales Team's User Profile in the Object Permissions.
Answer: D
NEW QUESTION # 56
Which three advanced tools can Salesforce enable for large-scale role hierarchy realignments in organizations with large data volumes?
Choose 3 answers.
- A. Parallel Sharing Rule Recalculation
- B. Granular Locking
- C. Deferred Sharing Calculation
- D. Skinny Table Indexing
- E. Partitioning by Divisions
Answer: C,D,E
Explanation:
Explanation
Three advanced tools that Salesforce can enable for large-scale role hierarchy realignments in organizations with large data volumes are partitioning by divisions, deferred sharing calculation, and skinny table indexing.
Partitioning by divisions allows the organization to segment data into logical sections based on business criteria, which reduces the number of records that need to be recalculated when role hierarchy changes.
Deferred sharing calculation allows the organization to postpone the sharing recalculation until a scheduled time, which avoids impacting users during peak hours. Skinny table indexing allows the organization to create custom indexes on frequently used fields, which improves query performance and reduces locking contention
NEW QUESTION # 57
The sales managers at the Universal Containers (UC) requested their teams to define each user's role on their accounts in order to provide an easy way to establish accountability and collaboration. Sales managers also requested that sales associates should only get the following permissions:
* Read access to the accounts.
* Read access to cases related to the accounts
* No access to deals related to the accounts
The sales associates may be granted access to opportunities when needed.
Assuming the overall sharing model of the organization is private and no sharing rules are configured on the account object. How can an Architect achieve these requirements?
- A. Use Account teams and use Sharing rules to share cases with sales associates. No change required to the opportunity object
- B. Use Account Teams to define access to accounts as well as opportunities and cases related to accounts
- C. Use Account teams, Case teams. No configuration required for the opportunity object.
- D. Use Account teams, Opportunity teams, and Case teams.
Answer: B
NEW QUESTION # 58
After setting up Customer Community and enable collaboration, the architect realizes that customers are only Chatter posts from other customers in their account.
What should the architect do to allow viewing chatter posts from all customers?
- A. Enable Internal Users Visibility.
- B. Enable Chatter Super User.
- C. Set View All for Chatter posts.
- D. Enable Community User Visibility.
Answer: D
NEW QUESTION # 59
If OWD is Public Read Only, what are sharing access options
- A. Read, - Read/Write
Answer: A
NEW QUESTION # 60
How would you make sure Visualforce page is security proof? Choose 3 answers
- A. Use debug to check hijacked requests
- B. Submit to force security scanner
- C. Manually check for cross site
- D. Manually check for sql injection
- E. Use web application tool for security
Answer: A,B,E
NEW QUESTION # 61
Universal containers (UC) implemented a private organization-wide default for the Container and Case objects.
How can UC give support representatives access to Container and Case records owned by Customer Community users?
- A. Create a Share Group based on the sharing set created for the Customer Community User Profile.
- B. Create an ownership-based sharing rule that gives access to the head of support role and internal subordinates
- C. Support representatives nil automatically get access to these records via the role hierarchy
- D. Create a criteria-based sharing rule that gives access to the head of support role and internal subordinates
Answer: A
NEW QUESTION # 62
A sales rep at Universal Containers was added to an opportunity team with Read/Write permissions.
Which action is she allowed to perform in the opportunity?
- A. Update opportunity stage.
- B. Add/remove members in the opportunity team.
- C. Replace opportunity owner.
Answer: B
NEW QUESTION # 63
Sales manager want their team members to help each other close Opportunities. The Opportunity and .. private. To grant Opportunity access to sales reps on the same team, ownership-based sharing rules ..
What is the side effect of this approach?
- A. Sales reps on the same will have Read access to the Accounts for Opportunities owned by their.
- B. Sales Reps on the same team will have Edit access to the Accounts for Opportunity owned by their.
- C. All sales reps will have Read access to all Accounts.
- D. All sales reps will have Read access to Accounts for all Opportunities.
Answer: C
NEW QUESTION # 64
What is a workaround to ownership data skew?
- A. You can minimize possible performance impacts by not assigning the user(s) to a role.
Answer: A
NEW QUESTION # 65
Dreamforce presenters need to be able to edit their presentation details (summary, presenter biographies, etc) on a private custom object in Salesforce (Presentation). All presenters for a presentation are captured on a Presenters juction object between Presenter and User.
How can this be accomplished?
- A. Give Edit rights to the Presentation record via a Permission set that is given to the Presenters for a record.
- B. Trigger on Presenter junction object that uses Apex Managed sharing to add or remove access to the related Presentation record.
- C. Trigger on Presenter junction object that adds the user to the Sales Team for the Presentation record.
Answer: B
Explanation:
Explanation
Adding the user to the Sales Team for the Presentation record will not work, as Sales Teams are only available for standard objects, not custom objects. Giving Edit rights to the Presentation record via a Permission set will not work, as Permission sets are assigned to users, not records. The best option is to use a trigger on Presenter junction object that uses Apex Managed sharing to add or remove access to the related Presentation record based on the junction object records.
NEW QUESTION # 66
Universal Containers has implemented Customer Community with Customer Community Plus licenses for its distributors. Some distributors requested granting specific community users (agents) to view cases submitted by other agents of the same distributor.
Which feature only supports these requirements?
- A. Partner super user
- B. Permission set to grant community admin permission
- C. Delegate external user
Answer: A
Explanation:
The Partner Super User feature allows certain community users to access records owned by other users within the same account. This feature is ideal for distributors needing some agents to view cases submitted by others within their organization. It provides broader access to records that are normally restricted by default sharing rules while ensuring the access scope remains confined to users linked by the same account.
* Option A: Granting community admin permission through permission sets is not supported for community users; this is an admin-level feature.
* Option B: Delegating external users allows managing other users, but it doesn't meet the requirement to share case visibility among users of the same account.
* Option C (Correct): Partner Super User enables the required sharing while adhering to the community's sharing model.
:
Partner Super User Access
NEW QUESTION # 67
......
Q&As with Explanations Verified & Correct Answers: https://freepdf.passtorrent.com/Sharing-and-Visibility-Architect-latest-torrent.html