Free Salesforce Platform-App-Builder Practice Exam with Questions & Answers | Set: 11

The correct answers are B. Cross-object field updates between Training and Student records are not supported and C. On Training record, the Student Lookup field can be made optional.

This question is about creating a Student lookup field on the Training object. A lookup relationship is a looser relationship than master-detail. Salesforce documentation explains that lookup relationships do not support roll-up summary fields, unlike master-detail relationships.

Because this is a lookup relationship, the Student lookup field on Training can be optional unless the app builder marks it required. Cross-object field updates are also not supported in this lookup relationship scenario; Salesforce documents that cross-object field updates work for master-detail relationship scenarios, not normal lookup relationships.

A is incorrect because roll-up summary fields require a master-detail relationship.

D is incorrect because deleting Student records is controlled by object permissions and relationship delete behavior, not simply by access from the Training record.

===========

A criteria-based sharing rule can identify Project records according to the Department field and share matching records with the appropriate public group. Salesforce documents that criteria-based sharing rules determine which records are shared based on field values and can grant access to public groups. Administrators can therefore maintain departmental public-group membership as employees change roles. When an employee leaves one department, removing that user from its public group removes the sharing path to those departmental Projects after sharing recalculation. Permission sets and profiles control object and field permissions but are not targets for criteria-based record-sharing rules. Account Teams apply specifically to Account collaboration and are unrelated to a custom Project object. With Project OWD set to Private, public groups plus criteria-based sharing provide the required controlled departmental visibility.

================

To display Component records as children in a related list on Product, the relationship field must be created on the Component object and point to Product. A lookup relationship provides exactly this parent-child association while allowing the records to remain independently managed. Salesforce explains that a lookup field on a child object relates it to a parent record and that users viewing the parent can then see the child records through a related list. After creating the lookup from Component to Product, the app builder adds the Component related list to the Product page layout. A junction object is unnecessary because the requirement does not describe a many-to-many relationship. Option C places the relationship in the wrong direction, while a roll-up field does not create a relationship or related list. Salesforce

================

A Screen Flow is required because the process must interact directly with a user and collect input. Salesforce defines screen flows as interactive automation that uses Screen elements and screen components to gather information from running users. After the required information is captured, an Update Records element can locate the related Account and write the supplied values to that existing record. Salesforce ' s Screen Flow documentation specifically describes adding an Update Records element and identifying an Account by its record ID when existing data must be changed. An autolaunched flow cannot contain normal interactive Screen elements. Record-triggered and schedule-triggered flows execute from record or time-based events rather than interactive user input. Create Records is also incorrect because the requirement is to update an existing related Account, not create a new one.

================