[2026年09月] 最新のSalesforce Sharing-and-Visibility-Architect認定練習テスト問題
確認済みSharing-and-Visibility-Architect問題集と解答で一年間無料最速更新
Salesforce Sharing-and-Visibility-Architect 認定は、Salesforce のセキュリティと共有に特化したアーキテクトにとって貴重な資格です。この認定は、Salesforce のセキュリティと共有モデルにおける専門知識を示し、雇用主に高く評価されます。認定を取得するには、データセキュリティ、データ共有、ユーザーアクセス、レコードレベルのセキュリティなどのトピックをカバーする Salesforce Certified Sharing and Visibility Architect 試験に合格する必要があります。候補者は、Salesforce Sharing-and-Visibility-Architect 認定コースを受講し、練習問題や学習ガイドなどのオンラインリソースにアクセスすることで、試験に備えることができます。
質問 # 22
Universal Container is a global Telco that has recently implemented enterprise territory management to better align their sales teams and sales processes. They are in Q4 of the FY and they have completely revamped their territory structure and created a plan for a new structure that would support the new FY. Their current territory model has 8k territories. Their new model would be a new set of 8,5K territories, and their org limit is 10k. What enterprise territory management feature can US take advantage of in order to help them stay within their org limits?
- A. Territory Type
- B. Territory Model State
- C. Territory type priority
- D. Territory Hierarchy
正解：B
質問 # 23
Universal Containers has developed Apex code to manually create AccountShare records to grant specific users access to individual Accounts. What must the Architect do to ensure the AccountShare records are not deleted when the owner of the Account is changed?
- A. Create the share records and set the RowCause to a custom Apex Sharing Reason
- B. Create the share records and set the RowCause to Manual
- C. Create the share records in a class with the "Without Sharing" keyword
- D. Create the share records with the Delete on Owner Change field set to false
正解：A
解説：
Explanation
According to this source, creating the share records and setting the RowCause to a custom Apex Sharing Reason will prevent them from being deleted when the owner of the account is changed. The other options will not have this effect.
質問 # 24
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
正解：D
質問 # 25
Sales managers want their team members to help each other close Opportunities. The Opportunity and Account organization-wide defaults are private. To grant Opportunity access to sales reps on the same team, owner ship-based sharing rules were created for each team.
What is the side effect of this approach?
- A. Sales reps on the same team will have Read access to the Accounts for Opportunities owned by their team members.
- B. All sales reps will have Read access to all Accounts.
- C. Sales Reps on the same team will have Edit access to the Accounts for Opportunities owned by then team members.
- D. All sales reps will have Read access to Accounts for all Opportunities.
正解：A
解説：
Explanation
The side effect of this approach is that sales reps on the same team will have read access to the accounts for opportunities owned by their team members. This is because owner-based sharing rules grant access to both the parent and child records of the same object. For example, if a sharing rule grants access to opportunities owned by a certain role, it also grants access to the accounts associated with those opportunities. All sales reps will not have read access to accounts for all opportunities, as the sharing rules are based on ownership. Sales reps on the same team will not have edit access to the accounts for opportunities owned by their team members, as owner-based sharing rules only grant read or read/write access to child records, not parent records. All sales reps will not have read access to all accounts, as the account organization-wide default is private.
質問 # 26
Universal Containers would like to control access to records and objects according to the following business requirements: Sales users can view all account records but only edit their own records. Sales managers can view all account records but only edit records of their team. Service users can view all account records that are not marked with a RecordType of Prospect.
Which organization-wide default configuration should an architect recommend to fulfill these requirements?
- A. Private
- B. Public Read Write
- C. Public Read/Transfer
正解：A
解説：
* Private Organization-Wide Defaults (OWD):
* Setting OWD to Private ensures that users only have access to records they own unless additional sharing mechanisms are implemented (e.g., Role Hierarchy, Sharing Rules).
* Why Option C is Correct:
* Sales Users: Can view all accounts via a sharing rule but only edit their own records (ownership- based access).
* Sales Managers: Use the Role Hierarchy to view and edit records owned by their team.
* Service Users: Add criteria-based sharing rules to exclude access to "Prospect" record types.
* Why Others Are Incorrect:
* Option A (Public Read/Write): Grants all users full edit access, which violates the "edit only their own records" requirement for Sales Users.
* Option B (Public Read/Transfer): This is typically used for cases, not for granular access control as described.
For more information, see Salesforce OWD and Sharing Rules documentation: https://help.salesforce.com/
質問 # 27
Universal Containers (UC) provides shipment tracking for its customers on a custom Shipment object. The ..
yearly by the customers should be available on the Account record to the Marketing team, but the Marketing Shipment records.
What recommend should an Architect provide to accomplish this?
- A. Private organization-wide default on Shipment, trigger, and Lookup relationship to Account,
- B. Controlled by Parent (Account) on Shipment, trigger, and trigger, and Master-Detail relationship to Account.
- C. Private organization-Wide default on Shipment, rollup summary, and Master-Detail relationship to Account.
- D. Public organization-wide default on Shipment, process builder, and lookup relationship to Account.
正解：A
解説：
Explanation
Setting the organization-wide default on Shipment to Private, creating a trigger to update the Account record with the shipment information, and using a lookup relationship to Account are the best recommendations to accomplish this requirement. This way, the Marketing team can see the shipment information on the Account record, but not the Shipment records themselves. Option A is incorrect, since setting the organization-wide default on Shipment to Public would give access to all Shipment records to all users. Option B is incorrect, since using a master-detail relationship to Account would inherit the sharing settings from Account, which may not be Private. Option C is incorrect, since using a master-detail relationship to Account and setting the organization-wide default on Shipment to Controlled by Parent would have the same effect as option B.
質問 # 28
Universal Containers would like to store an encryption key within Salesforce for use in Apex Code, but does not want users to be able to see this confidential key. Users require the view setup permission.
How can Universal Containers securely store the confidential key?
- A. Create 4 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 6 custom metadata type that stores the encryption key. Make sure that only the admin profile has access to the custom metadata type $0 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.
正解：C
解説：
Explanation
Creating a protected custom metadata type that stores the encryption key and packaging it with its associated records in a managed package is the best way to securely store the confidential key, as protected custom metadata types are only accessible within the package namespace and cannot be viewed or modified by subscribers2. Creating a protected custom metadata type and packaging it in an unlocked package will not work, as unlocked packages do not support protected custom metadata types3. Creating a custom metadata type and restricting access to the admin profile will not work, as users with View Setup permission can still view the custom metadata type and its records.
質問 # 29
The System Administrator at Universal Containers has created two list views called ListV1 and ListV2. One group of users should only see ListV1 and the second group of users should only see ListV2. Two public groups were created to restrict visibility to the respective list views. However, users in both groups are able to see both list views. What system permission in their profile enabled the users to see all list views?
- A. Manage Private List Views
- B. Manage Custom Permissions
- C. Manage Custom List Views
- D. Manage Public List Views
正解：D
質問 # 30
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.
正解：D
質問 # 31
Universal Containers (UC) service reps are assigned to a profile which has "View All" in Case object (Private OWD). To make sure service reps have access to all relevant information to attend to customer requests, which two details should a salesforce Architects consider?
Choose 2 answers:
- A. Service reps will be able to access all the UC Account records due to Implicit Sharing.
- B. Service reps will be able to access all UC contact records if they are controlled by parent.
- C. Service reps will not be able to access all the UC Accounts records because Account OWD is private.
- D. Service reps will not be able to access all UC contact records if they are controlled by parent.
正解：C
解説：
How can an architect achieve this?
https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_classes_perms_enforcing.htm
Example: To check the field-level read permission of the contact's email field before querying for this field:
if (Schema.sObjectType.Contact.fields.Email.isAccessible()) {
Contact c = [SELECT Email FROM Contact WHERE Id= :Id];
}
Answer for B -
https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_classes_keywords_sharing.htm
The "with sharing" keyword allows you to specify that the sharing rules for the current user are considered for the class. You have to explicitly set this keyword for the class because Apex code runs in system context. In system context, Apex code has access to all objects and fields- object permissions, field-level security, sharing rules aren't applied for the current user. This strategy ensures that code doesn't fail to run because of hidden fields or objects for a user.
質問 # 32
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
- C. Partner Community
- D. Customer Community Plus
正解：C
質問 # 33
Universal Containers (UC) requested that branch managers and UC branch staff should only see customers and related information in their geographic location.
Which options should be used together to achieve the requirements?
- A. Configure Role Hierarchy and create sharing rules.
- B. Create the Account Team and add branch manager team members, and configure organization-wide defaults of the Account object.
- C. Configure organization-wide defaults of the Account object and create sharing rules.
正解：C
解説：
Explanation
Configuring organization-wide defaults of the Account object and creating sharing rules are two options that should be used together to achieve the requirements, as they allow admins to set the baseline level of access for accounts and then grant additional access based on criteria such as geographic location2. Creating the Account Team and adding branch manager team members will not work, as it will require manual maintenance and will not grant access to UC branch staff. Configuring Role Hierarchy will not work, as it will grant access based on the user's position in the organization, not their geographic location
質問 # 34
Universal Containers has selected a small and diverse group of users to review inactive accounts. Given the Private sharing model, a public group was created and made available to this group of users. A sharing rule was created to make inactive Accounts visible to the public group. However some of these users are reporting they don't see any of the Accounts that were shared with the public group.
What is the underlying issue for these users?
- A. The page layout assigned to these users is different than the Account owner.
- B. The users are in profiles that have no access to the Account object.
- C. The Accounts are owned by users higher in the role hierarchy.
- D. The users have a permission set that only allow Accounts in "Active" status.
正解：B
質問 # 35
What is the security vulnerability in the following code snippet? <apex:form> <apex:commandButtonrerender="outputIt" value="Update It"/> <apex:inputText value="{!myTextField}"/> <apex:form> <apex:outputPanel id="outputIt"> Value of my Textfield is <apex:outputText Value="{!myTextField}" escape="false"/> <apex:outputPanel>
- A. Access Control
- B. SOQL Injection
- C. Arbitrary Redirects
- D. Cross-Site Scripting
正解：D
質問 # 36
Ursa Major Solar is writing test methods.
Which functionality does the system method "runAs()" Verify?
- A. Enforcement of a user's record sharing
- B. Enforcement of a user's public group assignments.
- C. Enforcement of a user's field-level security.
- D. Enforcement of user's permissions.
正解：A
質問 # 37
Universal Containers (UC) has 200 distributors that use Partner Community licenses.
Partners cannot see each other's data, but UC is also trying to give more visibility to data for certain individuals at a distributor.
HOW can an Architect give users in the partner user role access to all Case and Container records owned by any user, regardless of role, at the same distributor?
- A. Create an ownership-based sharing rule.
- B. Create sharing sets.
- C. Create a Permission Set granting "View All" permission to Case and Container records.
- D. Give super user permission to the individual partner users.
正解：A
質問 # 38
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.
正解：D
解説：
Explanation
Removing the "Opportunity Delete" permission from the sales team's user profile in the object permissions is the best way to prevent a certain set of users from deleting opportunities, as it controls whether they can delete any opportunity record in Salesforce. Removing the delete button from the opportunity page layout and record type settings is not effective, as it only removes the button from the user interface, not from other access points such as API or reports. Creating a validation rule that checks the user's profile before allowing the Is Deleted flag to be set to True is not possible, as validation rules cannot reference system fields such as Is Deleted. Overriding the standard button with a Visualforce page that warns them that they do not have permission to delete is not advisable, as it requires custom code and does not prevent deletion from other access points
質問 # 39
Sales reps at Universal Containers sometimes create large files as a part of the sales process that are too large to share over email. They would like users to be able to share files with customers, but the CISO has requested that any file links shared must be password-protected.
How can this be accomplished?
- A. Set up an Experience Cloud site for customers to access files and share the file with customers via Chatter. Customers can then log in ta the site to access the content.
- B. Utilize an AppExchange product for delivering password protected files to customers
- C. Create a content delivery; during creation, the user should select the option to require 3 password to access content.
正解：C
解説：
Content Delivery is a Salesforce feature designed for secure file sharing. When creating a content delivery, users can require a password for access, ensuring compliance with the CISO's requirement.
* Option A: While AppExchange products could provide similar functionality, Salesforce's native Content Delivery feature already meets the requirement without additional cost or complexity.
* Option B (Correct): Content Delivery allows the sharing of files via secure, password-protected links.
* Option C: Setting up an Experience Cloud site is an excessive and unnecessary solution for this simple file-sharing requirement.
:
Content Deliveries and Password Protection
質問 # 40
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. Add the dummy user to the bottom of the role hierarchy.
- B. Add the dummy user into a public group.
- C. Do not assign a role to the dummy user.
- D. Assign ownership to a small number of users.
正解：C、D
解説：
Explanation
To improve performance when a dummy user owns more than 10,000 lead records, it is recommended to assign ownership to a small number of users and do not assign a role to the dummy user. Assigning ownership to a small number of users reduces the number of sharing calculations and recalculations that occur when role hierarchy changes. Not assigning a role to the dummy user prevents the dummy user from granting access to other users in the role hierarchy
質問 # 41
......
最新の2026年最新の実際に出ると確認されたSharing-and-Visibility-Architect問題集で100%無料Sharing-and-Visibility-Architect試験問題集：https://www.jpntest.com/shiken/Sharing-and-Visibility-Architect-mondaishu
無料提供中2026年最新の無料更新されたSalesforce Sharing-and-Visibility-Architect試験問題と解答：https://drive.google.com/open?id=1W83JSHS3eGcIL1gsEGSCUTIQ94vptXQI