Salesforce Updated Platform-App-Builder Exam Questions and Answers by faris

Use a Component visibility filter. The issue is not object access or field access. The Contact Lightning record page is shared, but one component should be hidden for users with the Marketing profile. Salesforce Lightning App Builder supports visibility filters on Lightning page components, so the app builder can conditionally show or hide that component based on user/profile criteria.

Why not the others? AppExchange is unrelated. Detail page layouts control field layout, not visibility of a Lightning page component. Field-level security controls field access, not whether a large component appears on a Lightning record page.

===========

The correct answers are B. Each object can have up to 25 custom external ID fields and D. An external ID field can be an auto-number field.

Salesforce documentation states that each object can have up to 25 custom external ID fields. It also confirms that supported external ID field types include custom auto-number, email, number, and text fields.

A is incorrect because the limit is per object, not per org.

C is incorrect because a URL field is not one of the supported external ID field types.

===========

The correct answer is D. Create an Apex Trigger on the Account object.

The requirement is conditional: allow Account deletion generally, but block deletion when the Account has open Opportunities. A validation rule is not the correct tool because validation rules evaluate record data during save operations, while this requirement is specifically about preventing a delete operation.

An Apex before delete trigger can query related open Opportunities and call addError() on the Account record to stop the delete. Salesforce Apex documentation confirms that triggers can run before or after delete events, and trigger errors can prevent DML operations from completing.

A is incorrect because removing Delete permission blocks all Account deletion.

B is incorrect because removing the Delete button is not security and does not stop deletion through other channels.

C is incorrect because validation rules are not the right mechanism to block conditional deletes.

===========

The correct answers are C. Use Data Loader to update leads using the CSV file and D. Select Insert Null Values in Settings.

Universal Containers wants to delete values from fields on 5,000 Lead records. The correct method is to use Data Loader Update with the record IDs in the CSV file, leave the target field cells blank, and enable Insert Null Values so Data Loader treats the blank CSV values as null up dates. Salesforce Help explains that to change field values to blank/null with Data Loader, export IDs and fields, clear the values in the CSV, select Insert Null Values, and run an update.

Why others are incorrect:

A is unrelated because record type selection does not delete field values.

B is not the best choice because the Import Wizard is not the proper tool for mass clearing field values using null updates.