Free Practice Questions for Salesforce Plat-Arch-205 Exam

Price Books have specialized organization-wide access levels. Use is the appropriate level when sales agents must not only view products and pricing but also select the Price Book and add its products to Opportunities. View Only supports inspection and reporting but does not represent the same ability to transact with the Price Book during the sales process. Salesforce therefore distinguishes Use, View Only, and No Access so organizations can separate catalog visibility from sales usability. If UC later needs to restrict specialized Price Books, it can establish a more restrictive baseline and explicitly share those Price Books with selected users, roles, or groups at the Use level. The Price Book security model must also be combined with normal Product, Opportunity, and object permissions because each layer controls a different part of the process. Study Guide reference: Access to Other Data - Price Book security, Use access, View Only, product pricing, and Opportunity product access.

An Opportunity Team is specifically designed for multiple internal users who collaborate on an individual sales deal. The owner can add specialists such as product, solution, legal, or finance participants, assign each member a team role, and grant the appropriate Read Only or Read/Write access to that Opportunity. This is more maintainable than ad hoc manual sharing because the collaboration relationship is explicitly modeled as part of the sales process. The expected Account or Opportunity ownership change is also important: Salesforce provides options to retain the team when ownership changes, allowing the collaboration structure to continue through reassignment. Manual sharing of the Account would be unnecessarily broad because the requirement is to collaborate on one Opportunity, not to expose all customer information. Opportunity Teams therefore provide the correct scope, governance, and business semantics for a private Opportunity model. Study Guide reference: Access to Records - Opportunity Teams, team access levels, ownership changes, Private OWD, and collaborative sales access.

Custom Apex that serves a Lightning component must not assume that the client-side component has already enforced the user ' s data access. Apex can execute in system context, so the development team must explicitly preserve record visibility and enforce the user ' s CRUD and Field-Level Security where appropriate. The record-level requirement can be handled with the correct sharing declaration or user-mode operations, while object and field authorization can be enforced through user mode, Security.stripInaccessible(), or valid Schema Describe checks. Creating runAs tests is valuable for verification but does not secure production execution. Likewise, method names such as isShareable are not valid substitutes for the platform ' s real security APIs. The architectural principle is to treat the LWC-to-Apex boundary as a server-side trust boundary: every Apex entry point should return only records and fields that the running user is entitled to access. Study Guide reference: Permissions to Standard Objects, Custom Objects, and Fields - system-mode Apex, record-sharing enforcement, CRUD/FLS, user-mode operations, and Lightning/Apex security boundaries.

Mary has no effective access because object-level Read permission is a prerequisite for every record-level access mechanism. Public Read-Only OWD and the role hierarchy can determine which Invoice records a user may see only after the user is authorized to read the Invoice object itself. Mary ' s profile does not grant that permission, so neither the public OWD nor her position above Joe can make Joe ' s Invoice records available. Record sharing never substitutes for object CRUD. This is a core Salesforce security-order concept: object permissions establish whether a user can use an object, Field-Level Security determines which fields are available, and OWD, hierarchy, sharing rules, teams, and manual sharing determine which records are visible. Granting Read through a profile or permission set would be required before Public Read-Only or hierarchy-derived access could take effect. Study Guide reference: Permissions to Standard Objects, Custom Objects, and Fields - object CRUD, profiles, permission sets, OWD interaction, role hierarchy, and layered security evaluation.

A Default Account Team is designed for sales representatives who repeatedly collaborate with the same internal specialists on customer Accounts. The representative can define recurring team members such as legal, engineering, or finance and specify the access each team member receives to the Account and, where applicable, related Opportunities and Cases. The default team can then be applied automatically to new or transferred Accounts or added to existing Accounts, eliminating the repetitive manual-sharing work described in the scenario. A criteria-based sharing rule is better suited to record access determined by stable record attributes and a fixed audience; it does not model a recurring collaboration team tied to a particular salesperson. View All Data would be dramatically overprivileged because it bypasses record-level controls across the organization. Default Account Teams therefore improve productivity while preserving least privilege and making the collaboration relationship explicit. Study Guide reference: Access to Records - Default Account Teams, team roles, related-record access, collaboration, and least-privilege sharing.

Because Invoice is the detail side of a master-detail relationship to Account, its record-level access is controlled by the master. In Salesforce this is effectively a Controlled by Parent model: users can reach the detail record only to the extent that they can reach the associated master record, assuming they also have the necessary object permission on the detail object. The AR users have no access to the relevant Accounts, so they cannot discover or open the dependent Invoice records in list views, reports, or Global Search. Creating a sharing rule directly on the master-detail child does not solve the underlying access problem because the child does not maintain an independent sharing model in the same way as an independently owned record. The required access must therefore be established at the Account level; once the relevant Accounts are shared to AR, the dependent Invoice records become available according to the parent relationship. Study Guide reference: Access to Records - master-detail relationships, Controlled by Parent, OWD, inherited record access, and sharing at the master record.

The Presenters junction object expresses a dynamic user-to-record relationship: each Presentation has a different set of users who must be able to edit it, and that set can change over time. Apex-managed sharing is appropriate because a trigger on the junction object can create a share when a presenter is added and remove that access when the relationship is deleted or changed. The Presentation object ' s OWD can remain Private while only the users represented by the junction records receive the necessary Edit access. A permission set cannot grant access to one specific Presentation record; it supplies object, field, or system permissions and must be combined with a record-level sharing mechanism. Standard Sales Team functionality also does not apply to an arbitrary Presentation custom object. For a robust custom-object design, the implementation should use a dedicated Apex Sharing Reason so the programmatic shares are easy to distinguish and manage throughout the record lifecycle. Study Guide reference: Access to Records - Apex-managed sharing, junction objects, dynamic user-to-record relationships, custom sharing reasons, and Private OWD.

The custom Apex layer is responsible for enforcing Salesforce security; the Lightning component does not automatically make server-side data access safe. The valid runtime control among the choices is the Apex security mechanism that checks or enforces the user ' s access before data is returned or changed. Field-Level Security must be respected for sensitive values such as Shipment Amount, and the record-sharing model must also be enforced so a Private OWD is not bypassed. Schema Describe checks such as isAccessible(), isCreateable(), and isUpdateable() can be used for explicit field and object permission checks. Current secure-Apex patterns also include user-mode database operations and Security.stripInaccessible(), which can enforce or sanitize CRUD/FLS more comprehensively. Record visibility is a separate layer and should be preserved with the appropriate sharing context. System.runAs() is a testing facility, not a production authorization mechanism, and isShareable is not a valid Apex security keyword. Study Guide reference: Permissions to Standard Objects, Custom Objects, and Fields - secure Apex, CRUD/FLS, record-sharing enforcement, user-mode operations, and Lightning/Apex security boundaries.

Apex-managed sharing gives the development team substantial control over who receives record access, so it must be tested from the perspective of different users. System.runAs() is the appropriate test technique among the choices because it allows the test to execute sharing-sensitive behavior under representative user contexts and verify both positive and negative access outcomes. The test suite should include users who are supposed to receive access and users who must remain restricted, then confirm that the managed share entries produce exactly the intended visibility. A keyword such as without sharing would weaken record enforcement rather than validate it, and with sharing does not enforce Field-Level Security. In production code, record sharing, object CRUD, and FLS still have to be handled as separate concerns; runAs() simply provides a reliable way to exercise user-context behavior in tests. Study Guide reference: Access to Records - Apex-managed sharing, System.runAs(), Private OWD, user-context testing, and validation of least-privilege access.

Partner Community is the appropriate external license model because the distributors participate in a B2B sales process and require Opportunity visibility. Partner-oriented licenses support the external role hierarchy and the sales-object collaboration model needed for channel users such as distributors and resellers. Customer Community is primarily aimed at high-volume customer self-service and does not provide the same Opportunity-oriented partner model. Customer Community Plus adds more advanced sharing than basic Customer Community, but it is not the primary licensing model for external channel sales collaboration. At the scale described, the architect must also design the partner role hierarchy and external sharing model carefully so that one distributor cannot see another distributor ' s records and so that role/group proliferation does not create unnecessary sharing complexity. The license defines the ceiling of what the external user can do; UC must still configure object permissions and record-level sharing to expose only the Opportunities relevant to each distributor. Study Guide reference: Access to Records - Experience Cloud licensing, Partner Community, Opportunity access, partner roles, external sales collaboration, and scalable partner sharing.