Salesforce Fundamentals (7%)

Question 1

Key functionalities of Lightning App Builder

Answer 1

• Single-page apps (that drill down into standard pages)
• Custom record pages
• Custom Home pages
• Email application panes
• Dashboard-style apps (ex: track top sales prospects or key leads for the quarter)
• “Point” apps to solve a particular task (ex: expense app for users to enter expenses and monitor expenses they’ve submitted)
• Update the app’s branding, navigation, and app options

Question 2

Limitations of developing with Lightning App Builder

Answer 2

• Supports the same browsers as Lightning Experience
• Is not supported on mobile browsers
• Minimum recommended resolution for Lightning App Builder is 1280x1024

Question 3

Multitenancy

Answer 3

• The fundamental technology that clouds use to share IT resources cost-efficiently and securely
• A cloud uses multitenancy technology to share IT resources securely among multiple applications and tenants (businesses, organizations, etc.)
• Force.com (core Salesforce Platform technology) uses multitenant architecture
• Multitenant Data Model manages virtual database structures using a set of metadata, data, and pivot tables

Question 4

How is it possible to keep a multitenant environment secure, reliable, scalable, customizable by tenants, upgradeable without downtime, and fast?

Answer 4

• Clear separation of the compiled runtime database engine (kernel), tenant data, and the metadata that describes each application, making it possible to independently update the system kernel and tenant-specific applications and schemas, with virtually no risk of one affecting the others.

Question 5

Polyglot Persistence

Answer 5

• Using multiple data storage technologies for varying data storage needs across applications & devices
• Ex: Force.com employs a transaction database engine at its heart, and a separate search engine to optimize full-text indexing and searches. The separation of duties between the transaction engine and the search service lets applications efficiently process transactions without the overhead of text index updates and at the same time quickly provide users with accurate search results.

Question 6

Considerations for developing in a multitenant environment

Answer 6

• All customers share the same code base and database
• Governor limits monitor and limit various factors such as CPU time and DML statements to ensure that one org does not impact another
• Although many customers share the same instance, it is not possible for one customer query to return data from another customer. Each row in the table the stores application data includes identifying fields, such as the organization that owns the row (OrgID)
• Automatic upgrades are rolled out 3x/yr according to the Salesforce release schedule to all customers. Cannot be scheduled. Sandboxes are upgraded prior to production.
• All customizations are specified as metadata, allowing for easy upgrades
• Code cannot be deployed into production unless test code coverage is achieved

Question 7

Lightning Component Framework

Answer 7

• UI framework that allows building single-page web apps with dynamic and responsive user interfaces in Salesforce
• Event-driven architecture
• Utilizes a stateful client (JavaScript) and stateless server (Apex)
• Lightning components can be built using the Aura Components or Lightning Web Components model. They can coexist and interoperate on a page.
• Cross-browser compatibility & device awareness
• MyDomain must be deployed to use Lightning Components in an org
• Each Lightning Web Component that renders UI consists of an HTML file, a JavaScript file, and a metadata configuration file

Question 8

Aura Component Model

Answer 8

• Aura components are self-contained and reusable units of an app
• They represent a reusable section of the UI
• They can range in granularity from a single line of text to an entire app
• Supports the same browsers as Lightning Components
• Component Bundles can only be defined for Aura components (not Lightning components)

Question 9

MVC paradigm

Answer 9

• Model-View-Controller
• Model = Standard & Custom Objects, Object Fields, Object Relationships, Apex Classes (Data)
• View (presentation layer) = Visualforce Pages & Components, Standard Pages, Tabs, Page Layouts
• Controller (logic layer) = Standard controllers, Custom Controllers (Apex), Extensions (Apex), Declarative Rules

Question 10

Email Services

Answer 10

• Automated processes that use Apex classes to process the contents, headers, and attachments of inbound email.
• Ex: automatically create contact records based on contact information in messages.
• Each email service has one or more email service addresses that can receive messages for processing.
• Before creating email services, create Apex classes that implement the Messaging.InboundEmail Handler interface

Question 11

24-hour Total API call limitations per org type

Answer 11

• Developer = 15k
• Enterprise & Professional Ed. with API access enabled = 100k
• Unlimited & Performance Edition = 100k
• Sandbox = 5m

Question 12

Considerations for developing with Before Save Flows

Answer 12

• Before save updates in flows are executed immediately prior to Apex before triggers
• Recommended for updating fields on new or changed records
• The only supported elements are: Assignment, Decision, Get Records, and Loop
• Development requiring an Action element upon save must be performed in Apex instead of Before Save Flow