Pass Salesforce Developer Certification Exams in First Attempt Easily

Salesforce Developer Certification Practice Test Questions, Salesforce Developer Exam Practice Test Questions

Want to prepare by using Salesforce Developer certification exam practice test questions efficiently. 100% actual Salesforce Developer practice test questions and answers, study guide and training course from Exam-Labs provide a complete solution to pass. Salesforce Developer exam practice test questions and answers in VCE Format make it convenient to experience the actual test before you take the real exam. Pass with Salesforce Developer certification practice test questions and answers with Exam-Labs VCE files.

Salesforce Fundamentals - 7%

2. 1.2- The MVC Pattern

In this lecture, we will discuss what MVC is, what it stands for, what M, B, and C are. First of all, and to be frank with you, when I first heard about MVC, I thought, "Is that fancy thing out of this world?" But then, when I knew what it was exactly, I knew how simple it was. MVC stands for "Model View Controller." And it is a design pattern and model for software development that promote the separation of an application into three different components. First of all, into the application data storage component, and then into the application user interface component, and then into the application logic component. So, to make it simple, MVC is simply the separation of software development into three different components or layers. First and foremost, we have the model amp stand. And this is simply the database of the software—the database of the application. It's mainly the data that this application uses. And then we have the "V," which is mainly the interface that this application has: the different look and feel, the different colours on the page, and so on. And finally, we have the controller. This stands between the model and the view. And the job of the controller is simply to be a layer between the view and the model. So it will take data from the model and, depending on the permissions of the user and the view, get this data into the view. And also, it takes input from the view, and then it saves it in the database. This pattern is very popular. Why? Because it promotes the division of software development into three different layers. And in that case, it allows each component, each layer, to be developed independently from the others. As we have mentioned, "Model" is simply the underlying database of the application. In the case of Salesforce, it's simply the database of Salesforce, which is the collection of the different objects and fields, and so on, that we would represent and modify. An hour page view is simply the code that makes up our pages' user interface. So in the case of Salesforce, it's all the different standard pages that we have. So it's the opportunity page, the account page, and so on. And if you want to make extra pages or custom pages, we use VisualForce. We'll see Visual Force in detail in a later section. Visual Force is simply a nonstandard Salesforce page. It can use different components like HTML, like CSS, like JavaScript, and so on. And finally we have the controller, just the middle layer between the model and the view. It's the Apex code that interacts with the database according to the view's needs. Controllers typically retrieve the data to be displayed on a page from the model. from the database. They take this data, and they display it in the view and page layout. They take user input from the view, and they can save it to the database. And finally, they contain code that executes and responds to page actions such as a button click and so on. So, to make it simple, a controller is just the layer between the model and the view. as we have mentioned. It can take the data from the model and display it on the view according to the permissions. And it can also take the data from the view as input. It can also save it to the model. And also, it can respond to some actions on the page. So, if I click on a button on theview, the controller's code behind this button will execute. We have three different types of controllers. First of all, we have the standard ones. These come with the system. They come with every standard and custom object. We also have custom controllers. We have to code these. We have to create a new Apex class. And then we have to start this from scratch. And finally, we have controller extensions. As a conclusion, these are primarily extensions that can be added on top of the standard controller or the custom controller. The NVC pattern divides and delegates different jobs to different components. As we have seen, each one of these components has its own job. But why do we use it? Well, by separating our application into three different components, we get a more modular code base that's ultimately much easier to maintain and is much more scalable. So in that case, we'll have three different components to deal with. We'll have three different components that we have to code, each one independent from the other. And it's the same reason why we use objects in Salesforce and why we use classes and Apex. In that case, we can reuse the same class and different triggers. This is the same thing that we can do on the NBC pattern. We can use different controllers and different applications. So that's it for this lecture. In this lecture, we have learned about the MVC pattern: what it is exactly, why do we use it, and what are its advantages? What exactly as for model, what V, vis view and what C as the controller. And finally, as usual, thanks for watching. Bye.

3. 1.3- Core CRM Objects

In this lecture I will not onlytalk about the course, the other objects. I will also explain in detail the unique features of each one of these objects. With Salesforce, you will have the opportunity to sell to your customers by using different objects like leads, accounts, contacts, and opportunities. You can also use cases and communities to support your customers. You can use the Salesforce One application to use Salesforce on your mobile device or on your tablet. You can use chatter to collaborate with your peers and with customers. And finally, you can use the marketing cloud to manage your customer journey. So now let's talk about the core CRM object. First, we start with the lead object. What is a lead? It's mainly people and companies that you have identified as potential customers. They are not yet customers. They are mainly people that you have met through an event they shared with you or a business card, and they might do business with you in the future. So you have to be interested in them. You have to find a way to gather their information in Salesforce because, in the future, they might be your customers. Now, what are the unique lead features? First of all, there's something called Web to Lead. This is mainly a form used in Salesforce to generate HTML files. You can use this file on your website, and then using this file, you can create leads from the website. Then there's something called the lead autoresponder. This is mainly used to send autoresponder messages to new leads from your website. So let's say you received a lead from the website. This lead has a region equal to North America. You could say that any lead generated by the website in that region should be automatically responded to with this email template. Then finally, there is something called the lead assignment rules. This is mainly different rules that assign leads based on the field selected for different users and different queues. Now, what is a lead queue? What are queues and journals? Well, queues are composed of two different things. They are composed of from one side records likedifferent leads and from another side the users. It's records plus users. You can think of it like a bucket of lead records, and then it sits on a table, and then there are like five or six different chases around this table. These represent the different users. So now any user of this queue can take ownership of any record in that queue. One more thing I need to say When you create a queue automatically, a view is created for that queue. Now, the lead conversion. As I have mentioned before, ALEAD is not yet qualified. But what if this lead is now qualified? So there is something called lead conversion. This is mainly a tool used by Salesforce to convert a lead into an account opportunity and contact. How does this happen? Well, when you click on Convert Lead, the lead is now converted to an account contact. and opportunity, and the fields of the lead are mapped to the fields of account, contact, or opportunity. Then you can also create an optional follow-up task. The contract is mandatory. The lead should be converted to at least a contact. The account is optional. Let's say the account already exists in the system. You can choose not to convert the lead to an account, and the same thing happens for the opportunity. You can choose that I just want to convert the lead to a contact without an account and without opportunities. You can also map leadobject custom fields to fields, account contacts, or opportunities. Let's say you've made a new field. You can choose whether I want to map this new field to a field and an account. One more thing that I need to shedlight on validation rule should also pass. So you cannot convert a lead to an account, contact, or opportunity without the validation rule passing. And then when you convert the lead to an account contact opportunity, the lead is now closed and is now flagged as converted. Now let's move to the next object account. What's an account? An account is an organisation or a person that you do business with. It can be a customer, it can be a competitor, or it can be a partner. So it's any organisation or any person involved with your company. Now, some unique account features You can have something called a business account. This is the usual account type. This is mainly doing business with the company. So you have the fields that are related to the company. And then there's something called a personal account. Personal Account If you sell to individuals rather than organizations, you can request this feature from salesforce support. You enabled it. And there's one important thing: when you enable it, you cannot disable it again. When you do that, you will have twoaccount record type one of the business accountsand the second of the person account. The person account will only have fields related to a person. It does not have fields related to a company. Now let's talk about contacts for multiple accounts. By default, each contact belongs to only one account. But what if a contact belongs to more than one account? Let's take an example. A VP of one account can also bea member of work for another account. To solve this issue, we have the contacts for multiple accounts. This is a setting that you can set up in the account settings. You can allow it. And once you do that, a contact can belong to more than one account. The next thing that we talk about are the account hierarchies. An account can have a parent account. This is a standard field for the account object. So you can link account B to account A. In this case, I can click on "show hierarchy" and I can see that account B is the child of account A; we'll see that in the demo. After some time, the next thing we'll talk about is the Account Team. Both account and opportunity teams extend record-level privilege to team members. So let's say you want to share an account with another user. What you can do is click on "Manual Sharing," and you can share it. This is not a clean way. Another option is to contact the account team. Account teams provide a clear way to document the role of multi-producers and the management of a single account. What you can do is have different roles on the account. In this case, you can add any user to this role, and you can assign to him read-only access or read-and-write access instead of manually sharing the record with him. Account Team is not by default enabled. To enable it, you have to go to the account settings and check the box that says "Enable AccountTeams The next object we'll talk about is contact. Contacts are the people who work at your accounts. Each account has at least one contact, and each contact is related to one account by default. But he can also be related to more than one account. If we allow this, then there are two different types of contacts. There are the business contacts, the usual contacts; they belong to an account, and there is also the private contact. These are contacts without any accounts. These are often private contacts. These contacts are hidden from all users except their owners and the system administrator. It's always better to associate contacts with an account, but if you need to enable this feature, you can go ahead and do it. To enable private Contacts, remove the account and field requirements. So in this case, contacts can be created without an account. The next object is opportunity. Opportunities are mainly deals that have potential revenue that the sales representative tracks throughout the sale cycle. It tracks them from stage one until they are closed. They can either be won or lost. Using opportunities, we can have pipelines, we can have forecasts, and we can determine what's needed to keep the sales cycle moving. One of the most important features of Opportunity is the Opportunity Teams. This is mainly the same as the account teams. You can share your opportunities with any user. So mainly, instead of manually sharing the opportunity, you can do it through the Opportunity Teams. With Opportunity Teams, you can manually add and remove users to an opportunity without using the manual sharing tool. You can grant them read-only or read-and-write access, and you can have a default safety. So in this case, you don't need to add two or three users, each one configured differently. You can just click on one button to add your default team to your opportunities. Finally, this is the relationship among these four CRM objects. This is the flow diagram, and as you can see, there is a relationship between account and opportunity, between account and contact, and between account and lead. Let's now go to our Salesforce order and see the features that we have talked about.

4. 1.3- Core CRM Objects – Demo

So to start, I will show you the lead object and the feature that we have talked about. Firstly, I will talk about the Web to Lead feature. So to configure the Work to Lead form, I go to this link here and click on that button. Once I do that, I can select the fees that I want, and then I can click on Generate. I will have an HTML file. I can use this file within my website or within the website of my company. So visitors to this website can fill out this form, and then they can click on Submit. Once they do that, SalesForce will generate a lead for me. Once this lead is generated, it will be assigned to peers or users based on what criteria? on the lead. Assignment rules. Let me click on that. So here I can create a new assignment rule or I can modify the existing one. Finally, there's the lead auto response rule. This is mainly the email that I want to be sent to the person who submitted this form. like a thank-you email. I can do that from here. Let me talk now about queues. Queues are not in the same place as leads. Because queues are different, they are not directly related to leads. Let me click on Queues, and here I can create a new queue. Let me call this the lead queue. And a queue, as we have mentioned, is composed of two different things. First, there is the object supported by this queue and the users, or group of users, supported by this queue. So it's basically objects plus users clicking on Save, and now we have a queue. Now let me talk about the Account object. So let me go to the Account object. Basically, we did talk about assigning one contact to multiple accounts. This can be done by visiting this link and enabling this checkbox. So this will mainly allow users to relate contacts to multiple accounts. And then we talk about account hierarchy. Basically, if I open any account, I can see that there's a field called parent account. I can fill this field with an account number. So in this case, this account and the parent account will be linked. And if I click on "View Hierarchy," I can see this hierarchy. Now let me talk about the Account Team. To access the account team, I need to go to setup and then click on account. I can see here. Account team. Account Team is not by default enabled. I need to enable it from here. Now, if I go to the opportunity team, let me go to the opportunity team, and let me click on the opportunity teams. As you can see, I can enable or disable it from here. So basically, I can disable it from here, and I can also enable it if it is not enabled. Now let me talk about the default opportunity and the Account Team. Basically, I can configure this by going to my settings or to my user and then clicking on personal, and then I can click on advanced user details so I can specify the default opportunity team. I can add I can say that users X and Y are my default opportunity team. So in this case, if I go to any opportunity and push one button, I can add this default team to this opportunity. This is it. Add the default team. Or I can add specific users by specifying the user, team, or role and then the user and then the access. Finally, we talked about personal accounts. This should be enabled by Salesforce support. You have to contact Salesforce Support to enable this. Finally, as a summary of this lecture, you have learned about the course CRM objects. You have learned about the LeadContact account and opportunity. And finally, as usual, thanks for watching.

5. 1.4- Extending an Application's Capabilities using the AppExchange

In this lecture, we'll mainly talk about the App Exchange. We'll also talk about manage versus unmanaged packages. First of all, what is the App Exchange? The Business App Store is called App Exchange. App Exchange is the official Salesforce App Store. You can think of the App Exchange just like you think of Apple's App Store or Google Play Store. So if you have a requirement for an application, you can search for it on the App Exchange and you might find some examples there. If you are short on time and you don't want to build a solution from scratch, you better start by searching for this application or this solution. and the app exchange. The App Exchange, as we have mentioned, is the official Salesforce App Store. which means that the applications that it has are secure and trustworthy. What can you find on the App Exchange? You can find three things on the App Exchange. First of all, you can find applications. This is a group of tabs, a group of objects that work together. Second, you can find components. These are lightning components. For now, you can think of components as widgets. As a result, they can be added to any Lightning page. For now, think of them just as widgets for now.And finally, if you need any consulting services, you can go to the AppExchange and search for consultants. What is the strategy that you can use when searching for applications, components, consulting services, and the App Exchange? First of all, the offering type So are you looking for app components or consulting? Then there is the functionality. So are you seeking an app or a component? What does it need to do? So you need an application that can print as a PDF. You need an application that is being used to do maps. So you have to know what you actually need. What is the functionality of the application or of the component? What is the budget? Are you looking for a free application or for a paid application? What are the stakeholder needs? So who will be using this application? It will be used by you as an administrator as well as by end users. Does this application need testing? If so, do you have the right sandbox? And finally, technically, will this application integrate with your Salesforce environment? Is there anything technically wrong that you have to take care of? Now, this is the page of an application in the App Exchange. It has different components. First of all, we'll talk about the summary banner. The summary banner mainly summarises the key offering of the application for apps and components. It includes the technical information on what additions are supported for consulting services. This includes metrics like the customer satisfaction scores and the rating of the consultant. Second. There's the Overview Tab. This is the first tab, and it mainly has a description of the offering, like a brief description of the offering. What this application what it does. It can also have a small demo video that shows you this application in action. Then there's the detail. Tab. This mainly provides a full description of the application. Then there's the review tab. This displays the ratings and feedback from the Salesforce community members. Finally, there's the Provider tab. This mainly tells you who built this application or this component and how you can contact them if you need to ask them any questions. Then, on the right side, there's the Save button. This primarily adds this app to your favourites list. And then on the right, there's the green button. This button will begin the process of downloading this application into your organization. Some applications, as we have mentioned, are free. Some are paid. In the case of a paid application, we have two options to test the application. First, there's the free trial. This is used by most paid applications. Free trials will let you experience the offering. And a writer will develop an edition for a limited time, usually for 30 days. Then there's the test drive. The test drive will let you experience the application and read only the Developer Edition. Remember, it's up to the provider to either allow the test drive or the free trial. This is very important when you have to goto the app Exchange to search for applications. The rule of Thump is that you always need to go to the app exchange when you have requirements for an application implementation. So let's say your boss told you that he needs an application that will do this and that. So you could spend weeks developing the application, or you could go to the appExchange, search for it, and find the exact same application for free. Now, the second part of this lecture is packages. What are packages? A package is a bundle of metadata components that make up an application. So let's say you have an application. You have built an application that has three different tabs, and each tab is an object. These are mainly metadata. You can package these different tabs, these objects, and the fields within these objects into something called a package. A package can also contain page layouts. It can also contain reports, email, and templates. Everything that can be done by metadata can also be included in a package. It can also include Apex classes. Packages are primarily used to distribute metadata throughout the Salesforce organization. Packages are private, but they can be shared via a URL. To make it available, you can publish it on the App Exchange. So now you have an idea about the app exchange, and then you know about packages. So you can conclude that the applications and the app exchange are mainly packages. packages that can be made by partners, by salesforce, or by you. Packages can be installed, and they can be uninstalled at any point. So when you want to uninstall a package, uninstalling will remove all the components that were installed by this package. There are two different types of packages. First, there is the Manage packagesand there is the Unmanaged packages. Let's start with the unmanaged ones. Unmanaged ones. You can think of them as if you wanted to distribute an open-source programme that could be used for a one-time distribution of your metadata. They can be used for code migration between unrelated environments. They can be used to distribute to other companies via the App Exchange. The installer gets a copy of the components and then can further customise as required. So if you receive an Unmanaged package, the person orthe company who sent you this package, once they sendit, they don't have any control over this package. On the other side, what is a managed package? A managed package is a closed package. So if I receive a Manage package, I don'thave access to the source code of this package. And then the creator of the package can upgrade this package. I cannot do that. I don't have access to the code; I cannot edit the Manage package, but the creator can do that. Manage packages are typically for sale on the App Exchange, and they can be licensed. The only requirement to create a Manage package is that you create it using a Developer Edition organization. Now, this is the difference between "unmanaged" and "managed." Unmanaged is on the left, first of all, as we have mentioned, and Manage is mainly used to distribute open-source projects and to sell applications. Once the package components are distributed and the unmanaged package is created, you don't have any control over them. They can also be edited. In the case of managed packages, the creator always has control over the package. He can upgrade them. In the case of an unmanaged package, the component of the package will count towards the organisation limit. There's a limit to how many, let's say, objects you can use. If you had an object in an unmanaged package, this will count against the organisation limit. But if you have, let's say, objects through ManagePackage, this will not count toward this limit. There's something called namespace. We'll talk about it later on. Namespaces are not used in unmanaged packages, but they are used and managed. One unmanaged package can be distributed via a link, but once the link is sent, as we have mentioned, you don't have any control over it. The person who receives this link can always send this thing to another person, and so on. Manage packages; they don't do that. There is control over them. Now let me go to the live environment to show you a little bit about App Exchange. So let me first go to the App Exchange. So let me Google it. So this is the hyperlink. As we have mentioned, there are three different things that you can look for in the App Exchange application components or consultants. Let me first go to the Applications tab. This is the filter. You can say that I want a free application or a paid application. I want this application to work on the group edition and the professional edition. I want the rating to be five, four, three, or more for language. and then I can apply the filters. After that, I can look for different applications. I can also search on the top right for an application. Let me click on an application to show you the detail page of the application. This is the first step that we have talked about. It says that the characteristic of the application Then we have an overview. This is mainly an overview of the application. You can watch a video of the application here, like a demo. and then there's the Detail tab. This is a detailed description of the application. Then there is the Review tab with the score of the application and the ratings of the users. And then there's the Provider tab. This is mainly the contact information of the company or of the person who has made this application. And finally, you can save this application to your favourites list. The green button here will start the download process of this application on your computer. org, so let me go to the Components tab. This is the exact same thing. But now we are looking for Lightning components. You always have this tab to use to filter. And then you can click on a lighting component, and you have the same thing: an overview, detail reviews, provider save, and a get it now button. So, briefly, this is the app exchange. Finally, as a summary in this chapter, we first shed light on the App Exchange. We said that the App Exchange is the official Salesforce App Store. You can compare it to the Apple Appstore or the Google Play Store. You can find applications, components, or consulting services on the App Exchange. A good best practise is to always check for an application on the App Exchange. because there's a big chance that you can find the application that you are looking for. And in this case, you will save tonnes of time. You have to always plan before searching the App Store. You have to check what kind of application is needed. Are you looking for a fee-based or paid application? You can try an application before purchasing it. There are two different options to try. And finally, we talked about packages that are not managed or unmanaged packages.And we have stated the difference between these two. Finally, as always, thanks for watching. Bye.

6. 1.5- Common Use Cases for Declarative Customization

In this lecture, we will talk about the different descriptive customizations that don't require any coding and can be achieved by Salesforce. Note that in this chapter we'll just talk briefly about each one of these. In the next few chapters, we'll talk more in detail about them. Let's start with Formula Field. What's a formula? A formula is a field type that is similar to an equation that is executed at page read time. Depending on the context of the formula, it can make use of various data and operations to perform the calculation. So mainly, a formula is a field type that you can put on a page. This field type will use the data from different fields from the same page or from the parent page. A formula field is read only.It cannot be edited. You can think of a formula field just like you can think of an Excel field. In an Excel field you can put a formula, and this formula will calculate values based on fields from the same Excel sheet or from a different Excel sheet. So this is the same thing. A formula field can return a checkbox, currency, date, date, time, number, percentage, and text. an example of a percent formula calculating the margin based on the cost and the selling price. The cost and the selling price are two different fields of the same object. So if I want to calculate itargument, I can use these two fields. A formula will calculate fields from within the same object, but it can also calculate fields that are present in parent objects. This is called a cross-object formula. A cross-object formula is all about getting the information of the parent object into the child object. Fetching child object information and parent records is not done by formula. You cannot do that. This is done by the roll-up summary field, and the relationship between these two should be a master detail. A formula field and an object can fetch data from their parent object. But a formula feed and a parent object cannot fetch data from a child object's records. This is critical to remember because it is an example of a formula feed on the opportunity object that uses fields from the account object account as the parent of opportunity. So we can do that. Another example of cross-object formulas is this page's example. You can follow this example and apply it to your Salesforce.org instance. The next feed we'll talk about is the roll-up summary field. This is a type of field that is only available on the master object and master detail relationships. It is used to summarise the value of a particular field and charge object records. What it can do with this value is count. So it can count the number of records. It has the ability to do some, dominion, and maximum. To make it clear, let me give you an example. Let's say that you have two objects. Object one is the movie object. And object two is the review object. The movie is the parent of the review, and the relationship between these two objects is a master detail. Now, let's say on the review object there is a field called rating. This field has a numeric value. What we can do on the movie objects is make a roll-up summary field. This field will be linked to the rating field on the review object. What it can do first is count how many records there are. This is the end of the count. Second, it can do summation. It can summarise the feed that we have chosen for the child object, in this case the rating. So it can sum the rating, it can do the minimum rating and the reviews, and it can do the maximum. One important thing to shed light on is that this type of fee is calculated when you write to the children as opposed to when you read. Now, another example involving standard objects Object one is the account object, and object two is the opportunity object. Opportunity is the child of Account. So from within my account, I can create a roll-up summary field. This field will link to the Opportunity object. Wait, the relationship between these two is a lookup relationship. How can we create a roll-up summary feed on the account object? This is right. This is why I picked this example. Well, the relationship is really a lookup relationship, but Salesforce treats this relationship as a master detail. Finally, when creating the Master Detail field, you can use filters to only pull values from specific records. Let's get an example and an Opportunity Rollup summary For a field example, we can state that please only pull the data from the opportunities that are close to one. So in this case, the roll-up summary field on the Account object will only read about the opportunities that are closed and unopened. The next thing we'll talk about is our validation rules. Validation rules are used to enforce field requirements based on business logic before saving. So this is before the creation or before the update of a record. Validation rules are used to create conditional requirements on fields to ensure clean and accurate data entry. Let's say that you have a field. This field will only accept a number between one and ten. So how can you do that? How can you enforce this requirement? You can enforce it through the validation rule. You can say that anything other than between one and ten should not be accepted, the user entering this value should receive an error message, and the record cannot be saved. Validation rules are not used to replace the required field options in field-level security or in page layout. It's only used to enforce the type of data you want to capture in some fields. Now, how can you implement the validation rules? Validation rules can be implemented using a formula. The formula can return either true or false. If this formula returns true, the error message is displayed and the record cannot be saved. The formula can reference more than one field at one time, and the error message should clearly indicate the error type. So in our example, you should mention that the data entered is not between one and ten. This message can be displayed on the field itself or it can be displayed at the top of the page. Very important. Note that validation rules are case-sensitive, and validation rules will impact API usage. So let's say you are entering data through the data loader and the data will not be compliant with the validation rule. In this case, the data will not be entered. The same is true for the web to lead and the web to create submissions. This is why you need to make sure that you structure your validation rules so that they will not unintentionally interfere with these operations. And in some scenarios, you may need to disable these validation rules when importing or updating data and reinstate them afterwards. One important document to check is the example Salesforce validation rules document. I urge you to go check out this document. Finally, we'll talk about declarative automation tools. These tools are tools in Salesforce that are used to perform some requirements automatically without the need for any coding. There are four different declarative automation tools in Salesforce. First we'll talk about the workflow rules, then the approval process, and finally the process builder. And finally we'll talk about the visual workflow. Workflow rules can start when the record is created or when the record is updated. It can run immediately or after some time. And it can do four things It can update the feed on the record itself or on the parent object record in the master data relationship. It can create a task. It can send an email, and it can send an outbound message. An approval process can be started by clicking on a button or by clicking on a link. They can be called from a process, from a flow, or from Apex. They could only start immediately. They cannot be delayed. And they can do four things—the same thing that can be done by a workflow rule called the Process Builder. This is the new workflow rule. If you prefer, it can begin with record creation or record update. And it can start when it gets invoked by another product builder. It can run immediately or after some time. And it can do the same thing that a workflow rule can without the outbound message. On top of that, it can create a record. It can submit for approval, it can call a flow, and it can call another process. On top of that, it can call Apex, and it can post to chatter. Finally, flows can start when you click on a button or when you click on a link. They can also be triggered by another process. And finally, they can be called from Apex. They can run immediately and they can be paused. They can do a lot of stuff. Mainly they can delete records, they can createrecords and they can interact with the user. Finally, as a summary of this lecture, you have learned the different automation tools that can be configured declaratively without any lines of code. First, we started with the formula field. This is a read-only field that is used to calculate other fields from the same record or from parent records. And then we did the roll-up summary field. This is a very important field. It's only available on a master object in a master detail relationship. And it's used to calculate child object records from count to sum to minimum or maximum. Finally, we applied the validation rules. This is a way to enforce conditional requirements on fields to ensure clean and accurate data entry. Then we talked about the four automation tools. We talked about the workflow rules, the approval process, the process builder, and the visual workflow. We'll talk about each one of these in later chapters. And also, we'll show you examples of how these work. But for now, this is just an introduction. And finally, as usual, thanks for watching.

So when looking for preparing, you need Salesforce Developer certification practice test questions and answers, study guide and complete training course to study. Open in Avanset VCE Player & study in real exam environment. However, Salesforce Developer exam practice test questions in VCE format are updated and checked by experts so that you can download Salesforce Developer certification exam practice test questions and answers files in VCE format.