Tuesday, 2 August 2016

I want to take SFDC platform developer I exam

As many of you may be aware, Salesforce.com has announced changes to the Salesforce Developer Certification roadmap. Even though I am existing Salesforce Certified Force.com Developer(DEV401), it's time to take the Salesforce platform developer I.

Quick facts about the Exam (Platform Developer I):
1. 60 multiple-choice questions
2. 105 minutes allotted to complete the exam
3. 68% is the passing score
4. Registration fee is USD 200
5. Retake fee is USD 100
6. No hard-copy or online materials may be referenced during the exam
7. No prerequisites

To prepare this examination, I decided to spend 1 week my off-hours working through the suggested materials in the Salesforce Certified Platform Developer I study guide. Well, I admit that I am quite nervous.

So what topics that I plan to study?!

Standard Objects:
In past few years, I have participated in different Salesforce project, of course it included well-known Sales Cloud & Service Cloud, I believe that I have a good understanding of how the Standard Objects are used by actual users of Salesforce.

  • Accounts & Contacts Trailhead
  • Leads & Opportunity Trailhead
  • List of all Standard Objects
  • Sales Cloud Data Model
  • Service Cloud Data Model
Apex vs Salesforce built-in tools:
  • As a developer, we should know what we can do, what we can't do in below items.
  • Workflows
  • Trigger
  • Process Builder
  • Flow
Primitive Data Types:
Apex uses the same primitive data types as the SOAP API. All primitive data types are passed by value. All Apex variables, whether they’re class member variables or method variables, are initialized to null. Therefore, we have to make sure that we have initialized our variables to appropriate values before using them. For example, initialize a Boolean variable to false.

Developer Related Limits:
Know the most common Salesforce Limits, especially those relating to DML, Triggers, SOQL, and SOSL. Most likely you won’t be asked directly about them, but general Apex related questions will require you to know them. Always check for them in these questions.

Developer Console:
The developer Console provides a convenient sets of tools, but 

Changes Sets:
Using change sets, we don't have to be an experienced programmer, but we can still deploy changes with point-and-click tools. Use change sets to send customizations from one Salesforce org to another. For example, you can create and test a new object in a sandbox org, then send it to your production org using a change set. Change sets can only contain modifications you can make through the Setup menu. For example, you can’t use a change set to upload a list of contact records. Change sets contain information about the org. They don’t contain data, such as records.

Change sets allow you to validate changes before you send them to the target organization, providing another layer of safety. Because you can control which components are in a change set, you have fine-grained control over the deployment. Also, the target organization (in this scenario, the production organization) can choose when to deploy the change set it has received. For example, if you want to enable a change set during off-hours, you can do so no matter when the changes were sent.

Finally, change sets make the overall release process easier, because you can easily deploy the same change set to more than one environment.

I have another post and explained to that.

Apex Unit Test:
The Apex testing framework enables you to write and execute tests for your Apex classes and triggers on the Force.com platform. Apex unit tests ensure high quality for your Apex code and let you meet requirements for deploying Apex. In the meantime, before we can deploy we code or package it for the Force.com​ AppExchange, at least 75% of Apex code must be covered by tests, and all those tests must pass. So how to achieve it?

Why use Standard Set Controllers or Standard List Controllers?
  • Standard Controllers
  • Standard List Controllers
  • Custom Controllers 
  • Controller Extensions
  • StandardSetController Class 

Order of Executions:
To aviod infinite looping, we should know the ordering of Salesforce execution. 

All requests are delimited by the trigger, class method, Web Service, Visualforce page or anonymous block that executes the Apex code. If the entire request completes successfully, all changes are committed to the database. For example, suppose a Visualforce page called an Apex controller, which in turn called an additional Apex class. Only when all the Apex code has finished running and the Visualforce page has finished running, are the changes committed to the database. If the request does not complete successfully, all database changes are rolled back.


Good luck to me, I hope to tell you guys my good news!

No comments:

Post a Comment

Back to Top

What I Can Help



Do you wanna share posts

I am always looking for writers that have something interesting to say about Salesforce. Whether you have a post in mind or would like to collaborate on one, get in touch! - Click Contact Me