Last Attempt Platform-App-Builder Questions

A validation rule is the correct solution because Reason Lost should be required only when the Opportunity reaches Closed Lost. Salesforce explicitly recommends validation rules for conditionally required fields. The rule can evaluate whether StageName equals " Closed Lost " and whether Reason_Lost__c is blank; when both conditions are true, Salesforce blocks the save and displays an error. A page-layout required field would make Reason Lost mandatory at all stages, which does not meet the conditional requirement. A general field-level required setting has the same limitation. Dynamic Forms can control visibility and some UI behavior, but a validation rule provides reliable save-time enforcement across supported record-entry paths. Salesforce ' s Opportunity validation examples use the same pattern for stage-dependent required fields. Salesforce

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

A standard custom Picklist field is the correct data model because each Loyalty Member must have exactly one value from a controlled set: Standard, Plus, or Elite. Salesforce defines a Picklist as a field that lets users select a single value from a predefined list. The value set can be restricted so users cannot introduce inconsistent values outside the administrator-approved choices. Picklists also work naturally with Salesforce reporting, including filtering and grouping by the selected value. A multi-select picklist would incorrectly allow one member to belong to multiple tiers simultaneously. A free-form Text field would permit spelling and capitalization variations that undermine data consistency and reporting. A formula field derives its value from other data rather than allowing users to select one of the defined tier classifications.

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

A custom link or button that passes the current Account ID into a report filter provides direct access to a report showing only records associated with the Account being viewed. Salesforce ' s official documentation specifically describes creating an Account custom link that opens a report and automatically filters the results by the current Account ' s record ID. This precisely satisfies the requirement for Account owners to access the relevant Asset report from the Account record page. A dashboard filter requires dashboard-level filtering and does not inherently pass the current record context. Scheduled Reports deliver reports at scheduled times, while a Custom Report Type merely defines the objects and fields available for reporting.

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

Inspection__c must be the detail object and Building__c the master. Salesforce master-detail relationships create strong dependency between parent and child records: when a master record is deleted, its related detail records are cascade-deleted. Detail records also inherit record access from the master through the Controlled by Parent sharing model. Salesforce additionally specifies that the master-detail relationship field is created on the detail object. Therefore, the relationship field belongs on Inspection__c and references Building__c . A lookup relationship would leave Inspection records independently owned and would not provide the required cascade-delete and inherited-sharing behavior. Option B reverses the relationship direction and would incorrectly make Building the detail. Thus, D satisfies both lifecycle dependency and security inheritance requirements with the standard declarative Salesforce data model.

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