Ace Salesforce Sharing-and-Visibility-Architect Certification with Actual Questions Mar 12, 2026 Updated
2026 The Most Effective Sharing-and-Visibility-Architect with 80 Questions Answers
Salesforce Certified Sharing and Visibility Architect certification validates your skills and knowledge in designing and implementing sharing and visibility solutions for Salesforce. Sharing-and-Visibility-Architect exam covers a wide range of topics, including data access, sharing rules, role hierarchy, manual sharing, sharing sets, and other advanced sharing features. Sharing-and-Visibility-Architect exam also covers topics such as data security, user permissions, and record locking.
NEW QUESTION # 46
Universal Containers uses Standard WorkOrder object to track various work orders sent to field agents. Currently, the WorkOrder object has more than 400 fields. There are eight different types of work order processes established. The Director of Customer Service wants to ensure that field agents gets to see only required information specific to the WorkOrder type they are addressing.
Which option is recommended to implement this requirement?
- A. Use Dynamic form to add different page sections and control visibility of sections by Work Order RecordType value,
- B. Use different page layouts per work order type with different sections representing key information about the specific work order type.
- C. Use a custom LWC to override the view action of WorkOrder with custom metadata type defining relevant fields per WorkOrder type
Answer: A
NEW QUESTION # 47
What should an architect recommend to make sure that users that gained access to a custom object record through Apex managed sharing do not lose access to it when its owner is changed?
- A. Use "With Sharing" keyword to make sure record visibility will be considered.
- B. Create a specific Apex Sharing Reason for the custom object.
- C. Create a new record in _Share object with RowCause "Manual".
Answer: B
Explanation:
When Apex-managed sharing is used to grant access to records, changes to the record owner do not affect the existing shared records if a custom Apex Sharing Reason is created. The sharing reason allows the sharing record to remain independent of the ownership changes, ensuring persistent access for users who were granted visibility through Apex.
* Option A: The "With Sharing" keyword only enforces the sharing rules when executing the Apex code but does not ensure persistence of shared access.
* Option B: Creating a new manual sharing record directly is not recommended because manual sharing is automatically deleted when ownership changes.
* Option C (Correct): A custom Apex Sharing Reason allows the architect to maintain explicit sharing logic, avoiding access loss during ownership changes.
:
Apex Sharing Reasons
NEW QUESTION # 48
Universal Containers is implementing Sales Cloud. During the final quarter of the financial year, sales managers help each other close deals. They requested a solution in Salesforce to allow them to share opportunities with other sales managers from different teams as needed. They also requested that sharing deals should expire automatically 2 weeks after the new fiscal year starts.
Which proposed solution meets the requirements?
- A. Apex sharing to share opportunities with sales managers
- B. Sharing rules to share opportunities with sales managers
- C. Scheduled Apex job to remove access
Answer: A,C
Explanation:
To meet the requirement of sharing opportunities for collaboration and automatically expiring access, the following approach is best:
* Apex Sharing (Answer A): Apex sharing allows sales managers to share opportunities with specific users. This is essential for ad-hoc and granular sharing that isn't feasible with criteria-based or owner- based sharing rules.
* Scheduled Apex Job (Answer B): Use a scheduled Apex job to remove sharing entries after a specific date, ensuring access expires two weeks after the new fiscal year begins. This provides automation and aligns with the requirement for access expiration.
Option C: Sharing rules cannot handle time-based expiration, making them unsuitable for this use case.
:
Apex Managed Sharing Overview
Scheduled Apex
NEW QUESTION # 49
What should a Salesforce architect recommend to make sure that users that gained access to a custom of sharing do not lose access to it when its owner is changed?
- A. Use ''runAS'' system method in Apex classes to enforce record visibility.
- B. Create a specific Sharing Reason for the custom object.
- C. Create a new record in_Share object with RowCause ''Manual''
- D. Use ''With Sharing'' keyword to make sure record visibility will be considered
Answer: B
NEW QUESTION # 50
Universal Containers has requirement to integrate Salesforce with an external system to control record access.
What option should the Architect consider when designing a solution?
- A. Use the SOAP API to maintain the related SObject_share records.
- B. Use the SOAP API to create new Criteria-Based Sharing Rules in Salesforce.
- C. Use the Metadata API to maintain the related SObject records.
- D. Use the Security API to modify the role hierarchy in Salesforce.
Answer: A
NEW QUESTION # 51
Universal Containers (UC) has a requirement to expose a web service to their business partners. The web service will be used to allow each business partner to query UC's Salesforce instance to retrieve the status of orders. The business partner should only be allowed access to orders for which the business partner is the fulfillment vendor. The Architect does not want the business partners to utilize the standard APIs and would prefer a custom API be developed. Which three design elements should the Architect consider in order to ensure the data security of the solution?
Choose 3 answers
- A. Set the Orders object's sharing settings to Private in the Org-Wide Defaults
- B. Develop a custom Apex web service with a fulfillment ID input attribute
- C. Query the Orders object with Dynamic SOQL based upon the fulfillment ID.
- D. Provide each partner with their own Salesforce login set to API Enabled on the profile.
- E. Develop a custom Apex web service using the "With Sharing" keyword.
Answer: A,C,E
Explanation:
Explanation
To ensure the data security of the custom web service, the Architect should consider the following design elements:
Query the Orders object with Dynamic SOQL based on the fulfillment ID: This will allow the web service to filter the orders based on the input parameter and return only the relevant records to the business partner.
Set the Orders object's sharing settings to Private in the Org-Wide Defaults: This will restrict access to the Orders object to only the owner and users above them in the role hierarchy by default, and prevent unauthorized access from other internal or external users.
Develop a custom Apex web service using the "With Sharing" keyword: This will enforce the sharing rules defined for the Orders object and respect the record-level access of the web service user.
NEW QUESTION # 52
Universal Containers has implemented a community for its customers using the Customer Community sense type. They have implemented a custom object to store service requests that has a look up to the account record.
The Organization Wide Default External Access for the service request object is set to Private. Universal Containers wants their customers to be able to see service requests for their account through the community Customers should not see service requests for other accounts. What Salesforce feature can the Architect use to implement this?
- A. Use a Sharing Set to share service requests related to the account based on the community user's profile.
- B. Use a Sharing Rule to share service requests to the community user based on their role.
- C. Use Apex Managed Sharing to share service requests related to the account to the appropriate community users.
- D. Use manual sharing to share the service requests manually when a new community user is added.
Answer: A
Explanation:
Explanation
A Sharing Set is a feature that allows you to grant access to records that are associated with the same account or contact as the community user1. This is the best option to implement the requirement of allowing customers to see service requests for their account through the community. Manual sharing, Sharing Rules, and Apex Managed Sharing are not suitable for this scenario because they are either too labor-intensive, not applicable to external users, or too complex
NEW QUESTION # 53
Universal Containers has junction object called "Job Production Facility", with 2 master-detail relationships to the Job and Production Facility custom objects. Both master records have a private sharing model.
What statement is true if a user's profile allows access (Create/Read) to the Job, but no access to the Production Facility Object?
- A. The user will not be able to see the junction object records or the field values.
- B. The user will see the junction object but not the link to the Production Facility.
- C. The user will see the junction object and the link to the Production Facility.
- D. The user will be granted read access to the Production Facility record
Answer: A
NEW QUESTION # 54
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. Replace opportunity owner.
- B. Add/remove members in the opportunity team.
- C. Update opportunity stage.
Answer: C
Explanation:
Explanation
A sales rep who is added to an opportunity team with Read/Write permissions can perform actions such as updating opportunity fields, adding products, creating tasks, and logging calls4. Therefore, updating opportunity stage is an action that she is allowed to perform in the opportunity. Adding or removing members in the opportunity team is an action that only the opportunity owner or users above the owner in the role hierarchy can perform. Replacing opportunity owner is an action that only the current owner or users above the owner in the role hierarchy can perform.
NEW QUESTION # 55
Universal Containers uses 75,000 distributors that have close to 1 million total users. Distributors need opportunities assigned to the distributor for delivery.
What license recommendation will meet distributor needs?
- A. Sales Cloud
- B. Customer Community Plus
- C. Partner Community
- D. Customer Community
Answer: C
Explanation:
Explanation
The license recommendation that will meet distributor needs is Partner Community. Partner Community licenses are designed for users who are not employees of UC, but are part of their partner ecosystem, such as distributors, resellers, or suppliers. Partner Community users can access standard CRM objects such as accounts, contacts, leads, opportunities, cases, and campaigns. They can also collaborate with other partners and UC employees using Chatter and Communities. Sales Cloud licenses are for internal sales users who need full access to standard CRM and custom objects. Customer Community Plus licenses are for high-volume customers who need access to standard CRM objects and custom objects, but not opportunities. Customer Community licenses are for low-volume customers who need access only to custom objects and a subset of standard CRM objects.
NEW QUESTION # 56
Universal Containers has a Private Sharing Model for the Opportunity object. Sales Rep A at Universal Containers created the Opportunity record and then transferred ownership of the Opportunity record to Sales Rep B. Both Sales Rep A and B have the same role in the Role Hierarchy.
What access will Sales Rep A have to the Opportunity after the transfer?
- A. Full Access
- B. Read/Write
- C. No Access
- D. Read Only
Answer: C
Explanation:
Explanation
When a user transfers ownership of a record to another user, the original owner loses access to the record unless they have access through other means, such as role hierarchy, sharing rules, teams, etc. In this case, since both Sales Rep A and B have the same role in the role hierarchy, and the sharing model for the Opportunity object is private, Sales Rep A will have no access to the Opportunity after the transfer
NEW QUESTION # 57
Which two are potential vulnerabilities in the following code snippet? <apex:page> <apex:form>
<apex:outputText value="Enter Name"/> <apex:inputText value="{!name}" /> <apex:commandButton value="Query" action="{!query}" /> </apex:form> </apex:page> public class SOQLController { public String name { get { return name;} set {name=value;} } public PageReference query() { String qryString='SELECT Id FROM Contact WHERE '+ '(IsDeleted = false and Name like \'%' + name + '%\'}'; queryResult = Database.query(qryString); retunr null; } } Choose 2 answers
- A. Data Access Control
- B. SOQL Injection
- C. Arbitrary Redirects
- D. FLS check
Answer: A,B
Explanation:
Explanation
The potential vulnerabilities in the code snippet are SOQL Injection and Data Access Control. SOQL Injection is a technique that exploits a security vulnerability in a database layer of an application. It occurs when user input is directly appended to a SOQL query string, which allows attackers to execute arbitrary SOQL commands2. Data Access Control is a mechanism that ensures that users have appropriate permissions to access data in Salesforce. It involves checking the object-level, field-level, and record-level access of the user before performing any data operation3. The code snippet does not perform any FLS check or data access control check, which could expose sensitive data to unauthorized users or allow them to modify data without proper permissions3. Arbitrary Redirects are not a vulnerability in this code snippet, as they occur when a web application accepts untrusted input that could cause the web browser to redirect the user to a malicious website
NEW QUESTION # 58
Universal Containers (UC) is looking to expand its delivery capabilities through a network of distributors that use a Partner Community license. UC employees currently can view all delivery records through the organization-wide default (OWD) setting of Public Read-Only.
Which approach should an architect recommend to limit the records a distributor can see?
- A. Create an ownership-based sharing rule to grant access to the distributor.
- B. Set the External OWD to Private for the Delivery object.
- C. Create a criteria-based sharing rule to grant access to the distributor.
Answer: B
Explanation:
In Salesforce, controlling access to records for external users starts with the External Organization-Wide Default (OWD) setting. Setting the Delivery object's External OWD to Private ensures that distributors can only see records explicitly shared with them.
* Option A: Ownership-based sharing rules are not applicable if the distributors do not own the records.
* Option B: Criteria-based sharing rules can grant access but rely on the External OWD being set to Private first.
* Option C (Correct): Setting the External OWD to Private is the foundation for implementing sharing logic, limiting distributors' access only to records explicitly shared with them.
References:
* External Organization-Wide Defaults
NEW QUESTION # 59
A dummy user at Universal Containers owns more that 10,000 lead records. The system assigned all these leads to a dummy user. This is causing performance issues whenever role hierarchy changes. Which two options should be recommended to improve performance?
Choose 2 answers.
- A. Assign ownership to a small number of users.
- B. Do not assign a role to the dummy user.
- C. Add the dummy user to the bottom of the role hierarchy.
- D. Add the dummy user into a public group.
Answer: A,B
NEW QUESTION # 60
Universal Containers has a Private Sharing Model for the Opportunity object. Sales Rep A at Universal Containers created the Opportunity record and then transferred ownership of the Opportunity record to Sales Rep B.
Both Sales Rep A and B have the same role in the Role Hierarchy.
What access will Sales Rep A have to the Opportunity after the transfer?
- A. Full Access
- B. Read/Write
- C. No Access
- D. Read Only
Answer: C
NEW QUESTION # 61
Which two options can help mitigate the risks of import failures associated with large-volume bulk data loads?
Choose 2 answers.
- A. Defer Sharing Calculation.
- B. Minimize user group hierarchy.
- C. Increase batch size.
- D. Group records by ParentID within a batch.
Answer: A,D
Explanation:
Explanation
To mitigate the risks of import failures associated with large-volume bulk data loads, two options that can help are deferring sharing calculation and grouping records by ParentID within a batch. Deferring sharing calculation allows the data load to complete without triggering any sharing recalculation, which can be done later when the system is less busy. Grouping records by ParentID within a batch ensures that all child records of the same parent are in the same batch, which reduces the chances of locking errors
NEW QUESTION # 62
Universal Containers (UC) is a non-profit organization and has over 20,000,000 members (donors). The company decided to assign those accounts to Donations Reps based on them regions. Donations Reps ended up owning over 50,000 donors each. The donation reps started to see significant degradation of the system performance. What could be the reason for this problem?
- A. There is an Account ownership data skew problem.
- B. Salesforce sharing recalculation kicked off.
- C. The Account (donor) object OWD is Private.
- D. The Donations Reps access to the assigned accounts.
Answer: A
NEW QUESTION # 63
Universal Containers is designing a new community using the Customer Community license type. They would like to have the users complete survey questions through the community interface and store the responses in a Custom Object that has a lookup to the account object. Any internal user who has access to the account should be able to see all survey responses. All Customer Community users should be able to see surveys filled in by other users for their company, but not surveys for other companies. What are the correct security settings to achieve this?
- A. Set all Organization-Wide Default security to be "Private" for both internal and external users and use Sharing Rules to grant the desired access
- B. Set all Organization-Wide Default security to be "Public Read/Write" for internal users and "Private" for external users.
- C. Set all Organization-Wide Default settings to be "Public Read/Write" for both internal and external users.
- D. Set the custom object to be master-detail to the Account and leave the Organization-Wide Default settings as their default values.
Answer: A
Explanation:
Explanation
The correct security settings to achieve this are to set all Organization-Wide Default security to be Private for both internal and external users and use Sharing Rules to grant the desired access. This way, internal users can access all survey responses through the account object, and external users can only access survey responses that belong to their own account through the custom object.
NEW QUESTION # 64
An architect from a previous project implemented Platform Shield Encryption for a company. However, based on a recent audit, the company's Privacy Team identified three additional fields in their Account Records (Billing Street, Billing City and Phone) that needs to be secure and protected.
How should an architect proceed with this new policy change?
- A. Use Classic Encryption to ensure all fields are protected and contact Salesforce for help with encryption verification.
- B. Use Encryption Policy and contact Salesforce to update the existing records so that their field values are encrypted.
- C. Use Encryption Policy and wait for an email from Salesforce indicating the field values are encrypted.
Answer: B
Explanation:
* Platform Encryption: Salesforce Platform Shield Encryption ensures that specific fields in records are encrypted at rest and during transit, aligning with privacy and security policies.
* Why Option C is Correct:
* Updating the encryption policy for new fields (Billing Street, Billing City, and Phone) ensures compliance with the privacy team's requirements.
* Contacting Salesforce to encrypt existing records ensures that legacy data is also encrypted. By default, only new or updated records are encrypted when encryption is applied.
* Why Others Are Incorrect:
* Option A: Classic Encryption is outdated and not designed for structured field-level encryption with Platform Shield.
* Option B: Waiting for an email notification does not ensure that existing records are encrypted.
For detailed reference, see Salesforce Platform Encryption documentation: https://help.salesforce.com/
NEW QUESTION # 65
Universal Containers (UC) would like to store an encryption key within Salesforce for use in Apex code, but it does not want users to be able to see this confidential key. Users require the view setup permission.
How can UC securely store the confidential key?
- A. Create a protected custom metadata type that stores the encryption key. Package the protected custom metadata type with its associated records in an unlocked package. Install the package in the production org.
- B. Create a custom metadata type that stores the encryption key. Make sure that only the admin profile has access to the custom metadata type so that end users cannot access the encryption key.
- C. Create a protected custom metadata type that stores the encryption key. Package the protected custom metadata type with its associated records in a managed package. Install the package in the production org.
Answer: C
Explanation:
Protected custom metadata types in managed packages provide a secure way to store sensitive information like encryption keys. When packaged as part of a managed package, the metadata records are shielded from access by users, even those with View Setup and Configuration permissions.
* Option A: Custom metadata types without protection do not secure the key from users with View Setup permission.
* Option B: Unlocked packages do not provide the same level of protection as managed packages.
* Option C (Correct): A protected custom metadata type in a managed package ensures the encryption key is securely stored and cannot be accessed by users.
:
Custom Metadata Types
NEW QUESTION # 66
Sales Operations at Universal Container (UC) wants to create the opens to fiber appropriates for center.
In which two ways can UC hide list that are not relevant to an individual use since there will be Choose 2 answers.
- A. Share the list views with the appropriate public group.
- B. Share the list views with the appropriate role in the role hierarchy
- C. Share the list views with the appropriate queue.
- D. Share the list views with the appropriate individual users.
Answer: A,B
Explanation:
Explanation
Sharing the list views with the appropriate public group and sharing the list views with the appropriate role in the role hierarchy are two ways that UC can hide lists that are not relevant to an individual user. List view sharing allows users to share list views with other users based on public groups, roles, subordinates, or individual users. This way, users can only see list views that are relevant to them and their work. Option A is incorrect, since sharing list views with a queue is not possible. Option B is incorrect, since sharing list views with individual users would be tedious and inefficient.
NEW QUESTION # 67
......
Salesforce Sharing-and-Visibility-Architect (Salesforce Certified Sharing and Visibility Architect) Exam is designed for professionals who specialize in designing and implementing complex sharing and visibility solutions in Salesforce. Salesforce Certified Sharing and Visibility Architect certification is recognized as the highest level of expertise in the field of Salesforce sharing and visibility, and it is specifically designed to validate the skills and knowledge required to design and implement enterprise-level sharing and visibility solutions.
Try Free and Start Using Realistic Verified Sharing-and-Visibility-Architect Dumps Instantly.: https://www.itexamsimulator.com/Sharing-and-Visibility-Architect-brain-dumps.html
Sharing-and-Visibility-Architect Actual Questions - Instant Download 80 Questions: https://drive.google.com/open?id=1u_E4A6Ej5K6s4qupk8Cpg7ucvRpPofWy
