Platform-App-Builder Exam Dumps - Salesforce App Builder Questions and Answers

To display a weather map component only when a house is scheduled for a listing, the app builder should use Component Visibility in the Lightning App Builder.

Component visibility allows setting filters so components appear conditionally based on field values or other conditions.

Salesforce documentation states that conditional visibility rules control when a component is displayed dynamically on a Lightning page. (Salesforce Help)

B. Field-level security controls access to fields, not component visibility.

C. Formula field only calculates values but does not control component display directly.

D. Sharing rules control record access, not UI components.

===========

In-App Guidance is Salesforce ' s native capability for contextual onboarding, feature adoption, prompts, and guided walkthroughs directly inside Lightning Experience. Salesforce documents that administrators can create prompts and walkthroughs, determine the target audience, and specify where and when that guidance appears. Targeted prompts can highlight a specific page element, while walkthroughs connect multiple prompts into a step-by-step guided experience. This aligns directly with Universal Containers ' goals of increasing adoption and guiding users through a newly launched application. A Screen Flow is appropriate when collecting information or executing an interactive business process, but it is not the dedicated adoption feature. Dynamic Actions control which actions appear, while Dynamic Forms controls field and section presentation. Neither provides structured onboarding walkthroughs.

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

The correct answer is C. Use Dynamic Forms to display the Years of Previous Experience field if Previous Experience is checked.

This is a conditional field-visibility requirement. Salesforce Dynamic Forms lets app builders manage fields and sections directly in Lightning App Builder and use visibility rules to show users only the fields they need, when they need them.

So the app builder can place the Years of Previous Experience field on the Dynamic Forms-enabled record page and set visibility so it displays only when Previous Experience = True.

A is unnecessary and overcomplicated.

B is incorrect because field dependencies apply to picklists, not checkbox-to-number visibility.

D is incorrect because Visualforce is unnecessary when Dynamic Forms provides a declarative solution.

===========

Schema Builder can create custom objects, relationship fields, formula fields, and normal fields, but a key limitation is that fields created through Schema Builder are not automatically added to the object’s page layout. The app builder must go to the page layout separately and place the fields where users need to see them. Salesforce Trailhead confirms Schema Builder supports relationship fields, formula fields, and normal fields, so option B is incorrect. Salesforce Help also notes that fields added through Schema Builder are not automatically added to the page layout.

A validation rule is the correct mechanism because the requirement is to prevent invalid ZIP-code formats from being saved. Salesforce supports the REGEX() function in validation rules specifically for enforcing structured input patterns. Salesforce ' s own validation examples include a five-digit American ZIP-code pattern using regular expressions, demonstrating this exact use case. The rule can evaluate the shipping postal-code field and return TRUE whenever the value does not consist of exactly five digits, causing Salesforce to block the save and display an error. Help text only advises users and cannot enforce the format. A Screen Flow would affect only records entered through that particular interface, while an approval process is excessive and does not provide immediate data-format validation. Therefore, B provides consistent enforcement at the record-validation layer.

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

The validation must happen when a Contact is saved because the missing field is Region on the Contact record. Salesforce validation rules evaluate data before a record is saved and return an error when the formula evaluates to True.

The app builder can create a validation rule on Contact that checks the related Account’s Customer Status field and requires Region only when the Account is marked High Priority.

Example logic:

AND(

ISPICKVAL(Account.Customer_Status__c, " High Priority " ),

ISBLANK(Region__c)

)

Why others are incorrect:

A is wrong because the missing field is on Contact, not Account.

B is wrong because Customer Status being required does not require Contact Region.

D is wrong because it would require Region for all Contacts, not only High Priority Account Contacts.

===========

Record type availability determines which record types a user can select when creating records. Salesforce allows record types to be assigned through profiles, permission sets, and permission set groups. Therefore, if the support team ' s profile currently provides access to Bronze, removing Bronze from that profile prevents users from selecting that record type, assuming it is not granted through another permission set. Organization-wide defaults and sharing rules regulate access to records after they exist; they do not control which record types a user can select during creation. A permission set group containing Platinum and Diamond could grant additional access but does not inherently revoke Bronze access already provided by the profile. The direct solution described by the options is therefore to remove the Bronze record type assignment from the support team ' s profile.

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

The correct answers are A. Create a master-detail relationship field on Application to Open_Position and B. Create a master-detail relationship field on Application to Job Candidate .

This requirement describes a many-to-many relationship : one Job Candidate can apply for multiple Open Positions, and one Open Position can have multiple Job Candidates. The correct Salesforce design is to use a junction object , which in this case is Application__c .

Salesforce documentation states that many-to-many relationships can be modeled using master-detail relationships between a junction object and the two related objects.

So Application__c should have:

A master-detail relationship to Job_Candidate__c

A master-detail relationship to Open_Position__c

This allows applications to appear on the Job Candidate record and also on the Open Position record.

C and D are incorrect because the relationship fields should be created on the junction object , Application__c , not from the parent objects back to Application.

===========

An indirect lookup relationship is used when an external object must relate to a standard or custom Salesforce object and the external data does not contain Salesforce record IDs. Salesforce requires the parent Salesforce object to contain a custom field marked External ID and Unique . Values from the external object ' s indirect lookup field are matched against this external ID field to establish the relationship. Salesforce specifically states that indirect lookups link a child external object to a parent standard or custom object using a custom unique External ID field. TEXT(Id) does not create such a relationship key, and CASESAFEID() merely converts Salesforce IDs to their 18-character representation. A normal Salesforce Record ID is used for standard lookup relationships, not indirect lookups.

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

The correct answer is D. Validation Rule.

A validation rule is used to stop users from saving a record when required business conditions are not met. Salesforce documentation explains that validation rules verify that record data meets defined standards before the record can be saved.

For this requirement, the validation rule would check that when the Opportunity stage is Qualified, the Expected_Close_Date__c field is not blank.

Example logic:

AND(ISPICKVAL(StageName, " Qualified " ), ISBLANK(Expected_Close_Date__c))

Why others are incorrect:

Record Type controls business process, picklist values, and layouts, but it does not enforce this conditional save requirement by itself. Activity History and page layout do not reliably stop record save based on stage logic.

===========