Q.1 Explain all steps for making Reports & Dashboards for Lightning Experience?

Create a Report

1. Click the App Launcher and select Battle Station Construction

2. Click the Reports tab and click the New Report... button.
3. Click the Other Reports folder, select Battle Station with Supplies and click
Continue. If you don't see the Battle Station with Supplies report type, go to Setup
and click Object Manager. Next to Supply click the drop-down, then click Edit.
Under Optional Features, check Allow Reports. Click Save. Then go back and
create the report.
4. Search for Quantity, Unit Cost, and Total Cost fields in the Add column search and
add them as columns one at a time.
5. In the Add group search, enter Battle Station Name and select Battle Station
Name. This will separate the report by individual Battle Station records.
6. Click the Update Preview Automatically toggle to view column menus.
7. Open the menu on the Quantity, Unit Cost columns and select Summarize, then
deselect Sum. Leave Sum as selected for Total Cost Column.
8. Click Save & Run, enter Supplies for the Report Name and click Save.

Create a Dashboard

1. Click the Dashboards tab.

2. Click New Dashboard... button.
3. Name the dashboard as Construction and click on Create.
4. Click the +Component button on the top of the page and select the Supplies
report.
5. Select the Vertical Bar Chart component and click Add
6. Click the Save button and then Done.
Q.2 Explain all steps in Automating Business Processes for a Recruiting App with example?

Q.3 Describe what you should do before you distribute a flow. List the various ways you can
distribute a flow. Build a simple screen flow.

How Do You Distribute Your Flow?

● Lightning pages
● Flow actions
● Utility bar
● Experience Builder page
● Custom Lightning components
● Visualforce pages
● Web tabs

Build a Simple Flow

1. Create a flow.
1. From Setup, enter Flows in the Quick Find box, then select Flows.
2. Click New Flow to open the Flow Builder canvas.
3. Select Screen Flow, click Next, then select Freeform.
2. Add a Screen element to your flow.
 1. From the Toolbox, click Screen and drag it onto the canvas near the Start
element.
2. For Label, enter My Screen.
3. Under Configure Footer, select Hide Previous and Hide Pause.
4. For Next or Finish Button, select Use the standard label.
3. Add a Display Text field to your screen.
1. From the Components tab under Display, click Display Text.
2. For API Name in the Display Text properties pane, enter myText.
3. In the textbox, enter Hello, World!
4. Click Done to save the screen.
4. Click the node at the bottom of Start and drag it to Screen.
5. Save the flow. Name it Sample Flow.
6. From the button bar in Flow Builder, click Activate. The flow is now active.

4. What is Apex? Explain Features of Apex as a Language?

Apex is a programming language that uses Java-like syntax and acts like database
stored procedures. Apex enables developers to add business logic to system events,
such as button clicks, updates of related records, and Visualforce pages.

As a language, Apex is:

● Hosted—Apex is saved, compiled, and executed on the server—the Lightning

Platform.
● Object oriented—Apex supports classes, interfaces, and inheritance.
● Strongly typed—Apex validates references to objects at compile time.
● Multitenant aware—Because Apex runs in a multitenant platform, it guards
closely against runaway code by enforcing limits, which prevent code from
monopolizing shared resources.
● Integrated with the database—It is straightforward to access and manipulate
records. Apex provides direct access to records and their fields, and provides
statements and query languages to manipulate those records.
● Data focused—Apex provides transactional access to the database, allowing you
to roll back operations.
● Easy to use—Apex is based on familiar Java idioms.
 ● Easy to test—Apex provides built-in support for unit test creation, execution, and
code coverage. Salesforce ensures that all custom Apex code works as expected
by executing all unit tests prior to any platform upgrades.
● Versioned—Custom Apex code can be saved against different versions of the
API.

5. What is the difference between SOQL and SOSL?

6. What is junction object and what purpose does it serve ?

Junction objects are used to build many-to-many relationships between objects. For
example, the user can take a recruiting application where a position for a job can be
linked to many candidates or can link a candidate to many other jobs. In order to
connect the data model, a third party object is referred to as a junction object. In the
given example, the junction object is “job application.”
7. What is the benefit of Salesforce CRM?

Here are some of the top benefits of Salesforce CRM:

● Ensuring faster and better sales opportunity

● Deploying an analytical approach to customer acquisition
● Reducing cost and improving customer satisfaction
● Automation of repetitive and less important tasks
● Improved efficiency and enhanced communication on all fronts

8. Differentiate between Triggers and Workflows?

Trigger takes a programmatic approach but the workflow does not require coding.When
you want to take some actions say for an email, outbound message, task or field
update, then a point in click workflow is required.

The workflow rules can be used for the same object or the child to parent objects.
However, a trigger can be applied to any type of object.

9. Explain the four levels at which you can control data access in salesforce.

Levels of Data Access

You can control which users have access to which data in your whole org, a specific
object, a specific field, or an individual record.

Organization: For your whole org, you can maintain a list of authorized users, set
password policies, and limit logins to certain hours and locations.
Objects: Access to object-level data is the simplest thing to control. By setting
permissions on a particular type of object, you can prevent a group of users from
creating, viewing, editing, or deleting any records of that object. For example, you can
use object permissions to ensure that interviewers can view positions and job
applications but not edit or delete them. You can use profiles to manage the objects that
users can access and the permissions they have for each object. You can also use
permission sets and permission set groups to extend access and permissions without
modifying users' profiles.

Fields: You can restrict access to certain fields, even if a user has access to the object.
For example, you can make the salary field in a position object invisible to interviewers
but visible to hiring managers and recruiters.

Records: You can allow particular users to view an object, but then restrict the individual
object records they're allowed to see. For example, an interviewer can see and edit her
own reviews, but not the reviews of other interviewers. You can manage record-level
access in these four ways.

● Organization-wide defaults specify the default level of access users have to

each others’ records. You use org-wide sharing settings to lock down your data to
the most restrictive level, and then use the other record-level security and sharing
tools to selectively give access to other users.
● Role hierarchies give access for users higher in the hierarchy to all records
owned by users below them in the hierarchy. Role hierarchies don’t have to match
your organization chart exactly. Instead, each role in the hierarchy should
represent a level of data access that a user or group of users needs.
● Sharing rules are automatic exceptions to organization-wide defaults for
particular groups of users, so they can get to records they don’t own or can’t
normally see. Sharing rules, like role hierarchies, are only used to give additional
users access to records. They can’t be stricter than your organization-wide
default settings.
● Manual sharing allows owners of particular records to share them with other
users. Although manual sharing isn’t automated like org-wide sharing settings,
role hierarchies, or sharing rules, it can be useful in some situations, such as
when a recruiter going on vacation needs to temporarily assign ownership of a
job application to someone else.
10. Difference between public and global class in Apex?

Global class is accessible across the Salesforce instance irrespective of namespaces.

Whereas, public classes are accessible only in the corresponding namespaces.

11.What is the use of writing sharing rules? Can you use sharing rules to restrict data
access?

Sharing rules are written to give edit access (public read and write) or public read only
access to certain individuals in Salesforce org. A classic example is when:- only your
managers or superiors need to be given extra credentials to your records in objects as
compared to your peers.

By default, all users in your organization will have organization-wide-default sharing

settings of either Public Read Only or Private. To give access to more records, which
users do not own, we write sharing rules. Example: Sharing rules are used to extend
sharing access to users in public groups or roles. Hence, sharing rules are not as strict
as organization-wide default settings. They allow greater access for those users.

As far as the second part of the question is concerned, the answer is no. We cannot use
sharing rules to restrict data access. It is only used for allowing greater access to
records.
12. What Is the Salesforce Architecture? Define key terms related to the Salesforce
architecture.

Salesforce Architecture is the multilayer architecture; it contains a series of layers

situated on the top of each other.

● In the multilayer salesforce architecture, the users are at the topmost layer.

● The user can access a layer below the user layer, which means various clouds
offered by the salesforce, such as sales cloud, service cloud, AppExchange, etc.

● The third layer is the salesforce1 App, which allows the user to access the
salesforce on mobile device.

● The last layer contains various other salesforce platforms, such as Force.com,
Heroku, Exact TargetFuel, etc.

Key terms related to the Salesforce architecture.

● App: An app in architecture allows us to collect various things visually. The

metadata elements, such as classes, objects, visual force, etc., are different from
the App and independent.

● Instance: An instance of the salesforce architecture is the software configuration

that appears in front of the user when he login to the salesforce system. It shows
the server details of the particular salesforce organization on which it works.
Many salesforce instances can live on a single server. However, it is based on the
location of the user and changes according to user location.

● Superpod: Superpod is the set of frameworks and stack balancers. It includes

outbound intermediary servers, system and capacity foundations, mail servers,
SAN texture, and various other frameworks that support multiple instances. It
 provides the service isolation within a data center, so that if an issue occurs in
one shared component, it may not affect every instance.

● Org: Org or Organization is a particular customer of a salesforce application.

When a new user starts a trial on saleforce.com or developer.force.com, it
generates a new org in the system. The org has customizable security and
sharing settings that can be customized as per the requirement. Single org can
provide support anywhere to any user whether it is multiple licensed individual
user accounts, portal user accounts, or Force.com Sites user accounts.

● Sandbox: Sandbox is the instance of the production. It contains the sample data
instead of the original data. The sandbox allows the developer to test the various
conditions for the development to accomplish the client's expectations for the
applications. With the sandbox, developers can create multiple copies of the
production organization in different environment.

13. Describe what business accounts and contacts are, and explain how they’re
related. What are Best Practices for Managing Accounts and Contacts?

In Salesforce, you store information about your customers using accounts and
contacts. Accounts are companies that you're doing business with, and contacts are the
people who work for them.

Accounts and contacts are related to many other standard objects, which makes them
some of the most important objects in Salesforce.

Best Practices for Managing Accounts and Contacts

Know your company’s naming conventions for accounts.

Using established naming conventions helps everyone in the company. Names not only
help you find companies in your records, but they can be used to denote relationships
between accounts and help you decide if a company or individual already exists in your
records. For example, if you work with multiple franchises, you might need to use names
that make sense in a hierarchy but also help you differentiate between two stores with
the same name in a similar geographic area.

Always associate contacts with an account.

Contacts without accounts—private contacts—are like a forgotten boat adrift at sea.

They’re hidden from all users except you and your system administrators, which makes
them easy to forget, hard to find, and useless to colleagues.

Don’t let inactive accounts and contacts get lost in the shuffle.

Keep an eye out for, or create a report to find, accounts and contacts without activities
listed within the last 30, 60, or 90 days. Depending on your business, these inactive
customers may be ripe for a new product, or it may be time to exclude them from list
views, reports, and campaigns so you can focus on active customers.

Maintain active ownership.

It’s hard to actively manage an account if it’s assigned to someone who isn’t using
Salesforce. If you run across an account or contact that’s owned by someone who
moved to a different position or left your company, help find the account and its
contacts a new owner.

Keep your records updated.

Whenever you locate new information about an account, contact, or lead, enter it into
Salesforce. Your Salesforce data is only as good as you make it.
14. How will you build Data Model for a recruiting App?

Create a Custom Object for Reviews

Create a Custom Object for Job Posting Sites

Create a Custom Junction Object for Job Postings

Create a Self Relationship with the Position Object

Create Custom Recruiting Fields

15. Explain different types of picklists and Compare standard picklist ,custom
picklist,custom multi-select picklist.

Types of Picklist

1. Standard – Standard Picklists are included in your Salesforce org before making any
customizations like Opportunity Stage picklist on Opportunity object, Lead Source picklist
on the Lead object, and more.
2. Custom – Custom Picklists are the ones that you create based on your organization’s
processes.
3. Restricted – Restricted picklists limit users from adding new values (either through the
API or other apps).
4. Dependent – Dependent picklist filters values for one picklist based on a selection from
another picklist or a checkbox on the same record.
Standard Picklists

Standard picklists are the ones that are included in your Salesforce org before any
customization. Examples include the Lead Source picklist on the Lead object, the
Opportunity Stage picklist on the Opportunity object, and others.

Custom Picklists

Custom picklists are the ones you create. You can add your own values and configure a
custom picklist’s behavior.

Custom Multi-Select Picklists

Pick this option if you want your users to select more than one value from the picklist.
When a user picks more than one value, the selected values show in the field, separated
by a semicolon.
16. Explain various types of Reports available in Salesforce.

Salesforce Report Types

1. Tabular reports Simple Excel type tables which provide a list of items with the grand
total

2. Summary reports Similar to Tabular reports, but also have functionality of grouping
rows,viewing subtotals & creating charts

3. Matrix reports Two-dimensional reports which allow you to group records both by
row and column

4. Joined reports Multiple blocks showing data from different reports based on same or
different report types