Salesforce Maintenance Exams - Platform Developer 1

Salesforce Certified Platform Developer–1 Spring ’17 Release Exam Q & A

1. Which component type will display the details of the parent Account from a custom Lightning record page for the Contact object?

Answer:C

• A.Filter list component

• B.Parent object component

• C.Hierarchy component

• D.Related record component

2. Which three types of content can shortcuts be created for using Favorites?
Choose 3 

Answers:A,C,E

• A.Dashboards
• B.Custom tabs
• C.Chatter groups
• D.Global actions
• E.Record home pages

3. A Platform Developer wants to reference an image included in the Salesforce Lightning Design System from a Visualforce page.
Which two references should be included in the page markup?
Choose 2 

Answers: B,C

• A.$SLDS
• B.<apex:slds>
• C.$Asset
• D.<force:slds>

Explanation:

Use the Lightning Design System in Visualforce Pages

Use the element to incorporate the Lightning Design System in your Visualforce pages and align them with the styling of Lightning Experience. This component is a streamlined alternative to uploading the Lightning Design System as a static resource and using it in your Visualforce pages. Because you don’t have to upload the Lightning Design System as a static resource, you can keep the syntax of your page simple and stay under the 250-MB static resource limit. To use Lightning Design System stylesheets in your Visualforce page, add anywhere in your page markup. In general, the Lightning Design System is already scoped. However, if you set applyBodyTag or applyHtmlTag to false, you must include the scoping class slds-scope. Within the scoping class, your markup can reference Lightning Design System styles and assets. To reference assets in the Lightning Design System, such as SVG icons and images, use the URLFOR() formula function and the $Asset global variable.

Reference Lightning Design System Assets with the $Asset Global Variable Use the $Asset global variable to access images, sprites, and other assets that are part of the Lightning Design System. Use it in Visualforce pages that also use the component. Use $Asset instead of $Resource. The variable takes dot notation and SLDS. For example, this markup references a JPG avatar in the Lightning Design System.

4. Which feature enables creating, updating and deleting records in other Salesforce orgs?

Answers:D

• A.Lightning-to-Lightning Connector
• B.Database.WriteableObject Interface
• C.Apex Triggers for Writeable External Objects
• D.Salesforce Connect Cross-Org Adapter 

Explanation:

Work Seamlessly Across All Your Salesforce Orgs
—Cross-Org Connector with Write Support USER PERMISSIONS
To create and edit external data sources:
“Customize Application” To edit permission sets and user profiles:
“Manage Profiles and Permission Sets” Writable external objects are available with the cross-org adapter for Salesforce Connect.
Now your users and developers can create, update, and delete records that are stored in connected Salesforce orgs. In addition, lookup search is available for external lookup relationship fields whose parent external objects are associated with the cross-org adapter for Salesforce Connect. These changes apply to Lightning Experience, Salesforce Classic, and all versions of the Salesforce1 mobile app.

To enable writable external objects: When you define the external data source, select Writable External Objects.
When you enable user access to external objects, select the following object permissions as needed.
Read—Always required.
Create—Required to create external object records
Edit—Required to create or edit external object records
Delete—Required to delete external object records
Enable user access to the fields on the external objects

5. Which three actions can be taken from the Global Actions Menu?
Choose 3 

Answers: C,D,E

• A.Execute anonymous blocks of Apex code.
• B.Post to a Chatter feed.
• C.Launch a custom Canvas App.
• D.Launch a custom Lightning Component.
• E.Launch a custom Visualforce Page.

Explanation:

Create records, log calls, take notes, and launch canvas, Visualforce, and Lightning component actions from anywhere in Lightning Experience. The Global Actions menu ( ) now displays nearly all global actions from the Salesforce1 and Lightning Experience Actions section of the global publisher layout. This change applies to Lightning Experience only.
You might have noticed that we said “nearly all.” The Global Actions menu doesn’t support the standard Chatter actions Post, File, Poll, Link, Question, and Thanks.

6. Which two options are available to display detailed information about the status of an Apex batch job? Choose 2 

Answers: B,D

• A.Submitted by user
• B.Submitted date
• C.Heap size
• D.Elapsed time

Explanation:

Monitor the Status of Apex Batch Jobs:

Get more information about the status of Apex batch jobs. For a particular batch class, you can get information about parent jobs, such as submitted and completion dates and the number of batches processed or failed. This change applies to both Lightning Experience and Salesforce Classic.
From Setup, enter Apex in the Quick Find box, and select Apex Jobs to view all Apex jobs for your org.
Click the link at the top of the page to go to the new batch jobs page and see all Apex batch classes.
Click More Info on a particular batch class to show the parent jobs of the batch class, including information about:

Status
Submitted and completion dates
Elapsed time for each batch
Number of processed batches
Number of failed batches

7. Custom Lightning Record Pages can be assigned to which three items?
Choose 3 

Answers:A,C,E

• A.Profiles
• B.Public groups
• C.Apps
• D.Roles
• E.Record types

Explanation:

Now we can customize your users’ experience even more granular by creating custom record pages and assigning them by app, record type, and user profile. Give your sales managers a different view of opportunities than your sales reps. Configure nonprofit account pages differently than standard business account pages. We also revamped the activation process. You can now activate a page as the org default, app default, or for the most granularity, assign it to a combination of apps, record types, and profiles all in one place