Admin Cert Prep: Setup and Objects
These are technical notes I compiled while studying using Trailhead, Salesforce's free self-learning portal.
Get Started with Administrator Certification Prep
Describe the key topic areas of the Salesforce Administrator Certification. Access resources to prepare yourself for the Salesforce Administrator Certification.- Exam covers:
- Organizational setup: 3%
- User setup: 7%
- Security and access: 13%
- Standard and custom objects: 14%
- Sales and marketing applications: 14%
- Service and support applications: 13%
- Activity management and collaboration: 3%
- Data management: 10%
- Analytics—reports and dashboards: 10%
- Workflow/process automation: 8%
- Desktop and mobile administration: 3%
- AppExchange: 2%
- All certified professionals must successfully complete release maintenance exams specific to their credential.
- Three releases each year for the Administrator Certification (Spring, Summer, Winter)
- If these are not completed, the credential expires.
- This module focuses on:
- Organizational setup: 3%
- User setup: 7%
- Standard and custom objects: 14%
Study Up on Org Setup
Describe the content found in the company information area of Setup. Identify various UI features that an administrator controls. Practice common scenarios related to each UI feature. Practice common scenarios related to company information.- Topics:
- UI features
- Locale settings
- Company information
- Search results
- List views
- Currency management
- Fiscal year
- Default settings
- Homepage layouts
- What set of info can an admin specify in the Company Info page?
- Org Name, Default Time Zone, Default Language
- What two sets of parameters are configured using Locale settings? *
- Business Hours and Holidays
- Time and Number Display Format
- Not Business Hours, Holidays, Currency
- What user interface settings should be used to allow users, with all required permissions, to edit records in List Views? *
- Enable Inline Editing
- Enable Enhanced Lists
- If global search returns too many records, what two configurations should an administrator perform to help users manage search results? *
- Specify the Search Filter Fields for the object’s search layout
- Reduce the number of records displayed for each object in the Search Results page
- List View:
- A list of fields on records that meet specific filter criteria
Practice User Setup
Identify steps to set up and maintain users. Identify various user setup features that an administrator controls. Understand the implications of activating/deactivating/freezing a user. Practice common scenarios related to user setup.- Topics:
- Create and maintain users
- Assign and manage licenses
- Resolve locked accounts
- Activate, freeze, and deactivate users
- Reset passwords
- What should an admin do to assign a Service Cloud user license to a new user?
- Enable Service Cloud User on the user record detail page.
- Which two requirements should an admin consider when creating a new user in a production Salesforce org?
- Usernames must be unique across all production Salesforce orgs.
- Usernames must be in the form of an email address.
- What should an admin do first to troubleshoot login error messages?
- Check the user’s login history related list on the user record.
- What should an admin do to prevent a user from logging into Salesforce temporarily?
- Freeze the user’s account.
- Keeps the license in use, but stops the user from logging in.
- Freeze the user’s account.
- When a user account is deactivated, what happens to the associated license?
- The license becomes available for reassignment.
- What are two reasons a user cannot be deactivated? *
- User is the recipient of workflow email alerts.
- User is a customer community administrator.
- User License:
- A user license determines the baseline of features the user can access. Every user must have exactly one user license. User permissions for data access are assigned through a profile and optionally one or more permission sets.
- Permission Set:
- A collection of settings and permissions that give users access to various tools and functions. The settings and permissions in permission sets are also found in profiles, but permission sets extend users' functional access without changing their profiles.
- Profile:
- Define how users access objects and data, and what they can do within the application. Each user has one profile assigned.
Review Standard and Custom Objects
Describe the standard object architecture and relationship. Explain how to edit, delete, and customize fields and page layouts on standard and custom objects. Determine how to create and assign page layouts, record types, and business processes for standard and custom objects. Practice common scenarios related to standard and custom objects.- Topics:
- Object architecture
- Object relationships
- Creating, editing, and deleting fields
- Creating and assigning page layouts
- Creating and assigning record types
- Creating and assigning business processes
- Creating custom objects
- What standard object stores info about sales deals?
- Opportunities
- Which two standard objects are related to account records? *
- Cases
- Opportunities
- Which three objects have a relationship with Campaign? *
- Lead
- Contact
- Opportunity
- Which formula function should an admin use to evaluate different results based on a specific condition with multiple outcomes?
- IF
- How could an admin configure to automatically flag opportunities that have not been updated in the past 30 days?
- Create a formula field to calculate the time since last update and display an image of a red flag if it meets the defined criteria.
- How could an admin configure such that a user does not see a list of contacts when viewing an account page, but can still access contact records?
- Create an account page layout without the Contacts related list.
- How could an admin ensure that a picklist field’s values display in consistent colors in all reports? *
- Update the Picklist field and set the color for each value
- Create a Formula field that defines the color for each value
- How could an admin configure such that only a specific team can see a related list of invoice payments on an Opportunity related list, but all users are able to view Invoice Payment reports?
- Create a new page layout and profile for the finance team.
- Why couldn’t a delegated admin edit the Created Date field for an account record? *
- This is a System Audit field and it’s Read Only for existing records.
- A company wants to create a field to store credit card numbers and needs to ensure the info is protected. What two actions would allow an admin to provide enhanced security for a field? *
- Create an encrypted text field
- Update field-level security settings
- What feature allows an admin to maintain different options on the same field for two different teams? *
- Record Types
- A team uses many of the same Opportunity fields as other teams, but needs different stage values. What should the admin update to support this? *
- Stage Selected Values in the Sales Processes
- What method could an admin use if a team wants to use a different Page Layout when closing a Case? *
- Case Close Page Layout
- Formula Field:
- A read-only field whose value is evaluated based on a formula or expression. Can be defined on both standard and custom objects. Any change in expression or formula value auto-updates the value of the formula field. Can be defined for 7 types: Number, Currency, Percent, Date, Date/Time, Checkbox, Text.
- Custom Object:
- Objects created by users according to their need. Each comes with five standard fields.
- Roll-Up Summary Field: *
- A custom object fields that calculates values from related records or records in a related list. Roll-up summary field is created to display a value in a master record based on the values of fields in a detail record. Can be defined on Master-Detail relationships only.
- Lookup Field:
- Lookup is a one-to-many relationship that has no effect on deletion or security. The related objects are independent.
- If the parent object is deleted, the child remains in the system. A child may or may not have a parent.
- Master-Detail:
- Closely links objects together such that the master record controls certain behaviors of the detail and subdetail record.
- Its possible to define a two-object master-detail relationship, such as Account-Expense Report, that extends the relationship to subdetail records, such as Account-Expense Report-Expense Line Item. It is then possible to perform operations across the master-detail-subdetail relationship.
- One-to-Many:
- Relationship with many child objects by one Parent object. For example, metro cities are associated to one country.
- This kind of relationship is represented in four forms: Master-Detail, Lookup (loosely-coupled), Self, Hierarchical