Explanation:
There is no need to establish a custom profile because the additional delete permission is just for one user. It would
be more efficient to build a permission set and apply it to Josh that includes the ability to delete Application entries.
Josh will obtain visibility and access to records that Carlos owns if he is assigned a role higher than Carlos. Josh will
not be able to delete records because of the role hierarchy.
Explanation:
Custom objects and field auto-mapping are supported by both the Data Import Wizard and the Data Loader.
The Data Import Wizard allows you to load up to 50,000 records, while the Data Loader allows you to import up to 5,000,000.
When you need deduplication, you should use the Data Import Wizard instead of the Data Loader, because the Data Loader does
not have this feature. You can opt to dedupe data using the Data Import Wizard by selecting matching criteria such as Email or ID.
Explanation:
This requirement can be met by creating two record types, two sales processes and two page layouts.
A sales process should be defined with the relevant Opportunity stages selected
A page layout should be defined with the relevant fields included
A record type should be created and a sales process and page layout associated with it
Explanation:
Validation rules are triggered upon saving a record. Validation rules verify that the data a user enters in a record meets
the requirements (rules) you specify before they can save the record. If a record meets the requirements it will be saved.
If a record does not meet the requirements, an error message will be displayed.
Explanation:
Although a default record type can be established at the profile level by a Salesforce Administrator, if more than one record
type is active, the default will simply be picked, but the user will still be presented with the record type selection screen.
By skipping the record type selection box, we can shorten the navigation (fewer clicks = happier users!). We may accomplish
this by informing users that their default record type can be changed in Settings. When they create a record, they will no longer
see the record type selection screen because they have chosen their default record type.
Explanation:
Through Network Access, an Administrator can specify a list of Trusted IP addresses that applies to all users in the company.
A login challenge will not be sent to a person who logs in from a trusted IP address.
If a user attempts to log in from an IP address outside of the trusted range, they will receive a verification code. They may access
Salesforce after entering the code.
Explanation:
Users can aggregate rows of data, check subtotals, and build charts with summary reports. This report type can be used to
display subtotals based on the value of a specific field.
Explanation:
There is no macro called “Invokable Macro”. The 3 types of macros are:
Regular Macro – these macros perform actions that can be undone, for example, the macro selects the correct email
template but does not send it
Irreversible Macro – these macros perform actions such as sending an email to a customer and cannot be undone
Bulk Macro – these macros can run on multiple records at the same time
Explanation:
There is no need to create a new profile because there are only a few users that want additional access. While the Administrator
might assign each Super User to one of the existing Permission Sets, this would take a long time. Combining the three existing
Permission Sets into a Permission Set Group and assigning the Group to each Super User would be a preferable solution.
If more Super Users are needed in the future, adding the Permission Set Group will be simple.
Explanation:
Outbound Message actions are NOT available in Process Builder. An Outbound Message sends information to a designated
endpoint, like an external service.
Explanation:
The default language for an org is set on the Company Information page. An Administrator can set a different default
language when creating or editing a User record. Users can change their default language via the Language and Time
Zone settings in their Personal Settings.
In this example, only a small number of users require a different language so the company default should remain English.
Whilst the Administrator could manually update the language settings for each French user, it would be best practice to
show the users how they can change their own language settings in Personal Settings.
From Setup > Company Settings > Company Information
Explanation:
An Administrator can control field access such as visibility and read-only based on Profile. This can be done by navigating
to the field in ‘Fields & Relationships’ and choosing ‘Set Field-Level Security’.
Explanation:
The five types of AppExchange solutions are Apps, Bolt Solutions, Flow Solutions, Lightning Data, Components
There is no such thing as Industry Solutions or Community Solutions. Bolt Solutions are ready made community templates
based on industry specific criteria.
There is no such thing as Classic Solutions.
Explanation:
A Salesforce Administrator can enable the native Quotes functionality in Salesforce.
Quotes can be generated from an Opportunity and it’s related products. A Quote can be configured to display certain
fields, including Account, Amount and Discount. Each Opportunity can have multiple associated Quotes, but only one
can be synced with an Opportunity at any time. When a Quote and an Opportunity are synced, any change to line items
in the quote syncs with Products on the Opportunity, and vice versa. Quotes can be generated as PDFs and emailed
directly to customers from Salesforce.
Explanation:
The standard values for forecast categories are Pipeline, Best Case, Commit, Omitted, and Closed.
Explanation:
A Screen Flow should be used to achieve this scenario. Screen Flows can be used to guide users through a business
process, displaying the fields you determine and can also include additional guidance.
Explanation:
Email alerts use email templates and these must be configured prior to creating the email alert. The email template
controls the body and subject of the email that is sent. You can also create letterheads but this is not required.
Explanation:
Administrators can enable ‘Administrators Can Log In As Any User’ in Setup > Security > Login Access Policies. When
this feature is enabled, an Administrator can login as any user without requesting permission.
Explanation:
An Approval Process should be created on the Opportunity object with entry criteria stating that the Discount %
value must be greater than 30%.
Explanation:
Multi-select picklists can be dependent picklists but not controlling fields.
Explanation:
You can delete up to 250 Accounts, Leads, Activities, Contacts, Cases, Solutions, Products and Reports at one time using
the Mass Delete Records function in Salesforce. Data Loader could also be used, however for 100 Cases, Mass Delete Records
would be the better option.
Explanation:
A global value set can be used to share and restrict values across objects and custom picklist fields. Any custom
picklist using the global value set will be restricted to values listed in the global value set by default.
Explanation:
Case hierarchies can be used to link Cases together. A user can complete the “Parent Case” field on the child case to create
a Case hierarchy and relationship between Cases.
Explanation:
A Roll-up Summary field is a field that aggregates child record information into the parent record. For example, if you
implemented a Discount field at the Product level, you could roll that field value up to Opportunity level, giving you the
total discount.
Explanation:
Text Area (Rich) fields support the formatting of text including:
Colour
Formatting Font (Bold, Italic, Underline, Strikethrough)
Format Body (Bulleted List, Numbered List, Indent, and Outdent)
Align Text (Left, Right, Center)
Insert Link
Insert Image
