Salesforce Certified Force.com Developer – Winter ’17 Release

1. What must be shared between two objects to invoke one process from another using Process Builder?

A. Owner
B. Master-Detail
C. Junction Object
D. Unique ID

Explanation :

Build Reusable Processes 

Now you can create a process that another process can invoke. With invocable processes, you can reuse sections of your processes. Build one invocable process, call it from multiple processes or from multiple action groups in the same process. This ability to reuse can save you precious time, and who doesn’t love that? 

You can invoke processes with objects that share at least one unique ID. For example, in the Account and Case objects, the AccountId field is unique to Account and also used by Case. You can create an invocable process that updates a Case record. Then you can invoke it from: 

• A process that updates an Account record’s owner 
• A process that adds an Account shipping address or updates it 

When you create a process that invokes another process, each one counts toward your process and other applicable limits. DML limits in processes that invoke processes count as one transaction. When you create a process, have it start when another process invokes it by selecting It’s invoked by another process.

2. Which capability does the Lightning Mass Action feature allow beyond standard Actions?

A. Firing a single action on multiple objects at once.
B. Firing multiple actions on multiple objects at once.
C. Firing a single action on multiple records at once.
D. Firing multiple actions on multiple records at once.

3. What does the new ISCLONE function check when comparing two items?

A. If an item has the ability to be cloned.
B. If an item was cloned when created.
C. If one Item is a clone of another.
D. If an Item has ever been cloned.

Explanation

The new function ISCLONE checks whether an item is a clone of another item. 

• The ISCLONE function compares two items and returns TRUE if one item is a clone of the other. 

4. Where is the exported template saved in an Org when using Lightning Bolt for Communities?

A. Community Brand Manager
B. Community Creation wizard
C. Installed Packages
D. Personal App Exchange

5. Which two pieces of information should be recorded on the Work Type object?
Choose 2 answers

A. The estimated complexity of a Task.
B. The skills recommended to complete a Task.
C. The list of activities to complete a Task.
D. The estimated duration of a Task.
E. The needed equipment to complete a Task

Name two required steps for enabling debug logging for unauthenticated Guest Users accessing public Sites

Name two required steps for enabling debug logging for unauthenticated Guest Users accessing public Sites. Choose 2 answers

A.  Install the Sites Page Inspector plugin for Chrome
B.  Set a browser cookie with a name value of "debug_logs" and a domain value of ".force.com"
C.  Set the "Assigned Users" in the Site "Public Access Settings" to include the built-in Debug User
D.  Check the "Enable Guest Access Logging" checkbox option in Site Details
E.  Setup a new Trace Flag with a Traced Entity Type of 'User' that looks up to the Guest User for a Site

Answer :

B.  Set a browser cookie with a name value of "debug_logs" and a domain value of ".force.com"
E.  Setup a new Trace Flag with a Traced Entity Type of 'User' that looks up to the Guest User for a Site


Explanation

Set a Browser Cookie to Enable Debug Logging for Guest Users

Your public users generate a large volume of events, which can quickly fill up your debug logs. For this reason, logs are collected for site visitors who are using your Guest User license only when a public user’s browser has a special cookie. Logging of public users’ asynchronous activity isn’t available because asynchronous requests don’t include browser cookies. This feature is available in both Lightning Experience and Salesforce Classic. 

To enable logging for a guest user’s synchronous activity: 

1. Ask the user to set a browser cookie with a domain of .force.com, a name of debug_logs, and any value. (If you use a custom domain, ask your user to set the cookie for your domain rather than for .force.com.) Refer to the documentation for your user’s browser for information on adding cookies. To add cookies, your user probably needs a browser plug-in or extension for web development. 

• To set a cookie for API requests made with Java code, use the URLConnection class and set the cookie value as follows. 
– If you use a .force.com domain, use this code. 
URL url = new URL("http://yourSite.force.com/"); 
URLConnection con = url.openConnection(); 
con.setDoOutput(true); 
con.setRequestProperty("Cookie", "debug_logs=debug_logs,domain=.force.com"); con.setRequestProperty("Content-Type", "text/plain; charset=utf-8"); con.connect(); 

– If you use a custom domain (for example, yourCustomDomain.com), use this code. 
URL url = new URL("http://yourCustomDomain.com/"); 
URLConnection con = url.openConnection(); con.setDoOutput(true); con.setRequestProperty("Cookie", "debug_logs=debug_logs,domain=.force.com"); con.setRequestProperty("Content-Type", "text/plain; charset=utf-8"); 
con.connect(); 

• To set a browser cookie in Google Chrome™: 

a. Navigate to your site. 
b. Open the Chrome DevTools Console by pressing Ctrl+Shift+J (Cmd+Opt+J on macOS). 
c. Execute a command to set the cookie. 

– If you use a .force.com domain, use this command. document.cookie="debug_logs=debug_logs;domain=.force.com"; 

– If you use a custom domain (for example, yourCustomDomain.com), 

use this command. document.cookie="debug_logs=debug_logs;domain=yourCustomDomain.com"; 

• To set a browser cookie in other browsers, install a plug-in or extension. 

2. Find the name of your site’s guest user. 

a. From Setup, enter Sites in the Quick Find box, then select Sites. 
b. Select your site from the Site Label column.
c. Select Public Access Settings > View Users. 

3. Set a user-based trace flag on the guest user. 

a. From Setup, enter Debug Logs in the Quick Find box, then click Debug Logs. 
b. Click New. 
c. Set the traced entity type to User. 
d. Open the lookup for the Traced Entity Name field, and then find and select your guest user. 
e. Assign a debug level to your trace flag. 
f. Click Save

In Process Builder, how can you make a process reusable and invoke it from other processes or action groups in the same process?

In Process Builder, how can you make a process reusable and invoke it from other processes or action groups in the same process?

A.  Check the Invocable Process checkbox option
B.  No configuration is required because all processes become invocable in Winter '17
C.  Reference the process from an Apex method annotated with @InvocableMethod
D.  Select "It's invoked by another process" from the "The process starts when" picklist

Answer

C.  Reference the process from an Apex method annotated with @InvocableMethod

Explanation

Now you can create a process that another process can invoke. With invocable processes, you can reuse sections of your processes. Build one invocable process, call it from multiple processes or from multiple action groups in the same process. This ability to reuse can save you precious time, and who doesn’t love that? You can invoke processes with objects that share at least one unique ID. For example, in the Account and Case objects, the AccountId field is unique to Account and also used by Case. You can create an invocable process that updates a Case record. Then you can invoke it from: • A process that updates an Account record’s owner • A process that adds an Account shipping address or updates it When you create a process that invokes another process, each one counts toward your process and other applicable limits. DML limits in processes that invoke processes count as one transaction. When you create a process, have it start when another process invokes it by selecting It’s invoked by another process.

What are two ways to use the Lightning Design System in Lightning Apps?

What are two ways to use the Lightning Design System in Lightning Apps? Choose 2 answers

A. Reference a Static Resource using "Itng:require"
B. Copy and paste CSS classes from Lightning Design System to the CSS resource in the Application Bundle
C. Include an attribute with a name of "SLDS" of type "Boolean" that has a default value of true
D. Extend "force:slds" in the < aura:application > tag

Answer

A.  Reference a Static Resource using "Itng:require"
D.  Extend "force:slds" in the < aura:application > tag

Explanation

Use the Lightning Design System to style your Lightning apps by extending force:slds or using a static resource. The Salesforce Lightning Design System provides a look and feel that’s consistent with Lightning Experience. Use Lightning Design System styles to give your custom applications a UI that is consistent with Salesforce, without having to reverse-engineer our styles. Your application automatically gets Lightning Design System styles and design tokens if it extends force:slds. This method is the easiest way to stay up to date and consistent with Lightning Design System enhancements. To extend force:slds: When you extend force:slds, the version of Lightning Design System styles are automatically updated whenever the CSS changes. If you want to use a specific Lightning Design System version, download the version and add it to your org as a static resource

Which new option in Winter '17 improves sandbox creation by reducing the data in a Full sandbox?

Which new option in Winter '17 improves sandbox creation by reducing the data in a Full sandbox?

A. Data Compression
B. Template Optimizer
C. Content Version History
D. Login History

Answer

C. Content Version History

Explanation

Minimizing the amount of version history you include from your production org speeds up your sandbox copy. You can configure the new Content Version History option when you create or refresh a Full sandbox. You can copy from 0 to 180 days of history, in 30-day increments. The default is 0 days

For how many days will the "Quick Deploy" option appear after a Change Set is successfully validated?

For how many days will the "Quick Deploy" option appear after a Change Set is successfully validated?

• 15
• 10
• 30
• 4

Answer 

• 10

Explanation

The time window to quick-deploy your validations has expanded from 4 days to 10 days. This larger time window provides you more flexibility for scheduling your quick deployment and helps minimize the impact on your org. For example, if you successfully validated metadata components during off-peak hours on a weekend, you can wait until the following weekend to schedule your quick deployment of the validation. This change applies to change sets, Metadata API, and Metadata API–based tools, such as the Force.com Migration Tool.

Which two interfaces can be implemented to enable a lightening component for custom action

Which two interfaces can be implemented to enable a lightening component for custom action ?

• Force:lightningQuickActionWithoutHeader

• Force:lightiningQuickActionWithHeader

• Force:LightningQuickAction

• Aura:enableQuickAction

• Lightning:QuickActionEnabled

Answer 

• Force:lightningQuickActionWithoutHeader
• Force:lightiningQuickActionWithHeader