Valid Sharing-and-Visibility-Architect Dumps shared by ExamDiscuss.com for Helping Passing Sharing-and-Visibility-Architect Exam! ExamDiscuss.com now offer the newest Sharing-and-Visibility-Architect exam dumps, the ExamDiscuss.com Sharing-and-Visibility-Architect exam questions have been updated and answers have been corrected get the newest ExamDiscuss.com Sharing-and-Visibility-Architect dumps with Test Engine here:
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
Correct Answer: A,B,E
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.
Recent Comments (The most recent comments are at the top.)
Sky - Apr 15, 2024
B, C, E
OWD to private (B) + with sharing (E) + own user that is owner of the records (C)
(A) dyanmic SOQL does not help with sharing and record access (D) fullfillment ID as an input does not help if any vendor can pass fullfillment ID that belongs to different vendor and therefore seeing their records.
Sky - Apr 15, 2024
B, C, E
OWD to private + with sharing + own user that is owner of the records dyanmic SOQL (A) does not help with sharing and record access fullfillment ID as an input (D) does not help if any vendor can pass fullfillment ID that belongs to different vendor (and therefore seeing their records)
test - Mar 28, 2024
B. Set the Orders object's sharing settings to Private in the Org-Wide Defaults Setting the Orders object to Private ensures that by default, access is restricted. Users can't see each other's order records unless explicit sharing rules are in place or access is granted through roles, permissions, or programmatic sharing. This is a foundational step in securing data access at the organization level, ensuring that access to order data is tightly controlled.
D. Develop a custom Apex web service with a fulfillment ID input attribute A custom Apex web service allows for the creation of a tailored API endpoint that business partners can use to query order statuses. By requiring the fulfillment ID as an input attribute, the web service can ensure that partners only query orders relevant to them. This approach allows for precise control over data access and ensures that the query logic respects business rules regarding data visibility.
E. Develop a custom Apex web service using the "With Sharing" keyword. Using the "With Sharing" keyword when developing the Apex web service enforces the sharing rules and security settings defined in Salesforce. This means that the code runs with the same access rights as the user who is making the call to the web service. It's crucial for maintaining the principle of least privilege, ensuring that the web service respects organizational security policies, and only exposes data that the calling user is authorized to access....
Recent Comments (The most recent comments are at the top.)
B, C, E
OWD to private (B) + with sharing (E) + own user that is owner of the records (C)
(A) dyanmic SOQL does not help with sharing and record access
(D) fullfillment ID as an input does not help if any vendor can pass fullfillment ID that belongs to different vendor and therefore seeing their records.
B, C, E
OWD to private + with sharing + own user that is owner of the records
dyanmic SOQL (A) does not help with sharing and record access
fullfillment ID as an input (D) does not help if any vendor can pass fullfillment ID that belongs to different vendor (and therefore seeing their records)
B. Set the Orders object's sharing settings to Private in the Org-Wide Defaults
Setting the Orders object to Private ensures that by default, access is restricted. Users can't see each other's order records unless explicit sharing rules are in place or access is granted through roles, permissions, or programmatic sharing. This is a foundational step in securing data access at the organization level, ensuring that access to order data is tightly controlled.
D. Develop a custom Apex web service with a fulfillment ID input attribute
A custom Apex web service allows for the creation of a tailored API endpoint that business partners can use to query order statuses. By requiring the fulfillment ID as an input attribute, the web service can ensure that partners only query orders relevant to them. This approach allows for precise control over data access and ensures that the query logic respects business rules regarding data visibility.
E. Develop a custom Apex web service using the "With Sharing" keyword.
Using the "With Sharing" keyword when developing the Apex web service enforces the sharing rules and security settings defined in Salesforce. This means that the code runs with the same access rights as the user who is making the call to the web service. It's crucial for maintaining the principle of least privilege, ensuring that the web service respects organizational security policies, and only exposes data that the calling user is authorized to access....