PLAT-101 Practice Questions

The switches that the associate should toggle to only show the Record Count are Row Counts and

Grand Total. Row Counts is a switch that shows the number of rows in the report, which is the same

as the number of records. Grand Total is a switch that shows the sum, average, minimum, maximum,

or other aggregate functions of a numeric field in the report. By toggling these two switches on and

the other two switches off, the associate can see the Record Count and the Grand Total of the report,

without seeing the individual records or the subtotals. Subtotals and Detail Rows are switches that

show the breakdown and the details of the records in the report, which are not needed for the

Record Count.

Contacts to multiple accounts is a feature that allows a contact to be related to more than one

account. This is useful for scenarios where a contact works at multiple companies or has different

roles at different accounts. Creating two contact records would result in duplicate data and

confusion. Merging the two account records would not solve the problem of relating the contact to

two accounts.

Permission sets are what should be used to allow additional field-level access to individual

employees based on their job duties. Permission sets are a type of metadata that grant additional

access and permissions to users based on their functional or departmental needs. Permission sets

can include field-level security settings that allow read or edit access to specific fields on an object.

Permission sets can be assigned to multiple users, regardless of their profile. Individual profiles are a

type of metadata that define the baseline access and permissions for users based on their license

type and job function. Profiles include field-level security settings that allow read or edit access to

fields on an object. Profiles cannot be assigned to individual users, but to a group of users who share

the same license and job function. Role hierarchy is a type of metadata that define the level of access

and visibility of records for users based on their position in the organization. Role hierarchy allows

users to access records owned by or shared with users below them in the hierarchy. Role hierarchy

does not affect field-level access, but record-level access.

The Nonprofit Cloud is the cloud that is preconfigured to handle all of the requirements listed. The

Nonprofit Cloud is a set of products and solutions designed specifically for nonprofit organizations,

such as operations management, program management, grantmaking, fundraising, marketing, and

engagement. The Nonprofit Cloud includes the Nonprofit Success Pack (NPSP), which is a managed

package that adds pre-built objects, fields, workflows, and reports to the standard Salesforce

platform. The Analytics Cloud is a cloud that provides business intelligence and data visualization

tools, such as Einstein Analytics and Tableau. The Experience Cloud is a cloud that allows the creation

of digital experiences, such as websites, portals, and mobile apps, for customers, partners, and

employees.

A sandbox is the type of environment that GCC should use to onboard new hires as well as develop,

implement, and test new requirements. A sandbox is a copy of the production environment that

allows the user to create and test changes without affecting the live data and users. A sandbox can

have different types and sizes, depending on the purpose and scope of the changes. For example, a

developer sandbox can be used to create and test code, a partial copy sandbox can be used to test

large data sets, and a full sandbox can be used to perform performance testing and user acceptance

testing. A production environment is the live environment that contains the real data and users. A

production environment should not be used to onboard new hires or develop, implement, and test

new requirements, because it could compromise the data quality and security, and disrupt the user

experience. A Trailhead Playground is a type of environment that allows the user to learn and

practice Salesforce skills using Trailhead. A Trailhead Playground is not connected to the production

environment, and it does not have the same features and functionality as a sandbox.

Salesforce operates on a multi-tenant architecture, where a single instance of the platform serves

multiple customers (tenants). Each tenant’s data is securely isolated, but they share common

resources, such as server space, database instances, and updates. This approach ensures cost

efficiency and scalability.

A . Costs more than single-tenant architecture: Multi-tenancy reduces costs due to shared resources.

B . Reserves resources per tenant: Resources are shared rather than reserved individually.

Reference from Salesforce Documentation:

Salesforce Multi-Tenant Architecture Overview

Multi-Tenant vs. Single-Tenant

Converting the Region field to a picklist field is the recommended action to ensure there is correct

data for this field. A picklist field allows the user to select a value from a predefined list of values,

which ensures data consistency and accuracy. For example, the Region field could have values such as

North America, Europe, Asia, and so on. Creating a validation rule to enforce correct spelling would

not work, because it would not prevent the field from being blank, and it would not account for

different spellings or variations of the same region. Emailing users a list of region names with correct

spelling would not work, because it would rely on the users to manually enter the correct values,

which is prone to human error and inconsistency.

The Account and Contact objects have a lookup relationship. A lookup relationship is a type of

relationship that links two objects together, but does not affect security, ownership, or deletion. A

lookup relationship allows the user to select a record from another object and link it to the current

record. For example, the Account field on the Contact object allows the user to select an account that

the contact is related to. A self relationship is a type of lookup relationship that links an object to

itself, creating a hierarchy of records. For example, the Reports To field on the Contact object allows

the user to select another contact that the contact reports to. A master-detail relationship is a type of

lookup relationship that creates a parent-child relationship between two objects, where the child

records inherit the security and ownership of the parent record, and are deleted when the parent

record is deleted. For example, the Account field on the Opportunity object is a master-detail

relationship that links the opportunity to the account.

Updates are automatic; nothing needs to be downloaded or installed is the correct action for

Salesforce updates. Salesforce updates are a feature that allows the user to benefit from the latest

features and functionality of the Salesforce platform without any hassle or interruption. Salesforce

updates are delivered automatically to all orgs three times a year, in spring, summer, and winter. The

user does not need to download or install anything to receive the updates, and the user’s data and

customization are preserved and compatible with the updates. Updates do not require purchasing an

updated license, because the user’s existing license covers the updates. Updates do not need to be

downloaded with each release, because the updates are applied automatically to the user’s org.

Permission sets are used to grant additional access to users based on their functional or

departmental needs. A permission set can be assigned to multiple users, regardless of their profile. A

permission set can include field-level security settings that allow edit access to specific fields on an

object. Queues are used to group records and assign them to a team of users who can work on them.

Public groups are used to group users, roles, or other groups for the purpose of sharing records or

sending email.