Salesforce Platform-App-Builder - Salesforce Certified Platform App Builder (Plat-Admn-202)

The correct answer is C.

The Lightning record page already supports both mobile and desktop, but the downloaded custom component is not visible on mobile. That points to the component itself, not the page activation. Lightning components must be configured to support the required form factors. Salesforce developer documentation explains that components can be configured for desktop form factor Large, phone form factor Small, or both.

So, if the AppExchange component was built only for desktop pages or only supports the large form factor, users cannot view it in the Salesforce mobile app.

A and D are incorrect because the issue is not page activation if the page already supports mobile and desktop. B is incorrect because the scenario states the record page supports both mobile app and desktop.

===========

The correct answer is B. The Allow reparenting checkbox, Child records can be reparented to other parent records after they are created, is unchecked.

A service plan must be associated with one Contact, and users cannot change the Contact after the service plan is created. Since field access and validation rules are not the issue, the likely cause is a master-detail relationship where Allow reparenting is not enabled.

Salesforce documentation states that in master-detail relationships on custom objects, administrators can allow child records to be reparented by selecting Allow reparenting. If that option is not selected, users cannot change the parent record after the child record is created.

A and C relate to master-detail sharing settings, not changing the parent record. D is the opposite of the problem; if Allow reparenting were checked, users could change the parent Contact.

===========

The correct answer is A. Allow Salesforce to import Contacts from mobile device Contact lists.

Salesforce supports importing contacts from a mobile device contact list into Salesforce from the Salesforce mobile app using Import from Device. Salesforce also notes that users need the permission Allow Salesforce to import Contacts from mobile device Contact lists to use this feature.

Why others are incorrect:

B only notifies users; it does not move phone contacts into Salesforce.

C helps users create/edit records offline in Salesforce, but it does not import contacts already entered in the phone’s contact list.

D is for account-contact relationship modeling, not mobile contact capture.

===========

The correct answer is D.

Validation rules are the right declarative tool to enforce data compliance before a record is saved. They can prevent a Case from moving backward to an earlier Status and can require specific fields when Case criteria are met. Salesforce formula functions such as ISCHANGED() compare whether a field value changed, and validation rules can use formula logic to stop invalid saves.

Why others are incorrect:

Approval Process is for routing records for approval.

Dependent picklists control picklist value availability, not status regression.

Case Flow can automate case processes, but validation rules are the best tool for enforcing save-time compliance.

===========

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.

===========

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.

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

The correct answer is C. Dynamic action.

Dynamic Actions allow an app builder to control which actions appear on a Lightning record page and apply filters to control action visibility. Salesforce documentation states that Dynamic Actions can be assigned in Lightning App Builder and visibility filters can control when actions are shown.

For this requirement, the custom Sync action can be shown only when the Account custom Status field equals Ready to Sync. A custom link alone does not provide the same Lightning App Builder visibility control, a formula field cannot call the Lightning Web Component action, and an AppExchange product is unnecessary.

===========

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.

===========

A Screen Flow is the best declarative tool when the user must answer questions through a guided UI and use those answers to update record fields. Salesforce documents that screen flows provide a UI that guides users through a business process, and they can be launched from quick actions or Lightning pages.

A custom button or action can launch the flow, collect the extra approval-related information, update the Account fields, and then continue the approval submission logic.

Why not others:

A. Custom object only stores data; it does not provide the popup/question flow.

B. Visualforce could be custom-coded, but Flow is the declarative App Builder solution.

D. Custom Lightning component requires development and is not the best declarative answer.

===========

The correct answer is A. Roll-up summary field.

Cloud Kicks wants to count how many Subscription records are related to each Shoe record. Because a master-detail relationship already exists between Subscription and Shoe__c , the app builder should create a Roll-Up Summary field on the master object.

Salesforce documentation confirms that roll-up summary fields can count the number of detail records related to a master record. Trailhead also explains that roll-up summaries display values on the master record based on directly related detail records in a master-detail relationship.

B. Lookup field and C. Master-detail field define relationships, but the relationship already exists. D. Sum field is not a Salesforce field type.

===========