Platform-App-Builder Sample Questions & Answers

Flow is the most efficient tool because it can handle all the required logic in a single, consolidated process. A record-triggered Flow can create the new Student record and then use a Decision element to route the logic based on the 'Program' field. Each path in the decision can then have a 'Create Records' element for the Task, assigning it to the specific coordinator for that program. This avoids having multiple Process Builders or a combination of tools, which is less maintainable.

While simply marking a field as an External ID doesn't change its data type, if you also intend for it to be a unique identifier (which is common practice), you must ensure all existing records have unique values in that field. Salesforce will prevent you from marking a field as both 'External ID' and 'Unique' if duplicate values exist. The other options are incorrect; you can change a text field to be an external ID, and references in reports or automation do not need to be removed first.

A criteria-based sharing rule can be configured to share records where the Project equals Project X with the consultant. This is a scalable and maintainable solution.

If the Project Task object's sharing is controlled by its parent Project, manually sharing the Project X record can grant the consultant access to all its child tasks. This is suitable for ad-hoc access needs.

Change sets deploy metadata, which includes the definition of the permission set and the user assignments if the users are included. However, it is best practice and often necessary to manage user assignments in the target org. The deployment itself only moves the permission set definition; the assignment to specific users (which is data) is typically handled post-deployment.

This formula correctly checks for the fiscal quarter logic. Since the fiscal year starts in February, we subtract 1 from the month before calculating the quarter. The formula checks if the stage is correct, and then compares the fiscal quarter of the CloseDate with the current fiscal quarter, along with the year, to prevent it from being moved to a prior fiscal quarter. The other options either check for a past date incorrectly or don't account for the custom fiscal year.

This scenario describes a many-to-many relationship: a property can have many interested buyers, and a buyer can be interested in many properties. The correct way to model this is with a junction object. This junction object, Interest, will hold the master-detail relationships to both parent objects and is the perfect place to store attributes of the relationship itself, such as the Interest Level.

A record-triggered Flow is the best declarative tool for this. It is bulk-safe and can handle large volume updates efficiently. A Flow triggered by the Account update can query for all related open Opportunities and update them. Process Builder could also achieve this, but Flow is the recommended and more performant tool for such operations, especially as Salesforce is moving away from Process Builder.

To automatically associate the new Survey record with the current Account record, the action must be an object-specific action created on the Account object. This provides the context of the Account record, allowing the lookup field on the new Survey to be automatically populated. A Global Action would not have the context of a specific Account record.

While change sets can work, they are prone to inconsistencies, especially when sandboxes are out of sync. The most reliable and modern best practice for ensuring consistent deployments across multiple environments is to use a version control system (VCS) as the single source of truth. The metadata is committed to the VCS and then deployed from the VCS to each environment, guaranteeing that the exact same components are being promoted.

Manual Sharing is designed for exceptional, case-by-case sharing scenarios where a user needs to grant access to a specific record to another user or group who wouldn't normally have access. While not available out-of-the-box, temporary access can be managed via Apex managed sharing, but for a declarative solution, manual sharing is the direct approach, and the expiration would be managed manually or with a simple scheduled flow to remove the share.