Latihan Salesforce Platform App Builder

Custom objects are user-defined tables that store business data. Standard objects are built in, and reports or dashboards are different features.

Picklist fields restrict values to a predefined list. Currency stores money, formula calculates values, and roll-up summary aggregates children.

Master-detail is a parent-child relationship with cascade delete and roll-up summary support. A lookup is a looser link, and external lookups connect external data.

A lookup creates a link between records without the strict cascade behavior of master-detail. Reports and dashboards are not relationships.

Formula fields compute values from other fields and are read-only. Text fields store input, and validation rules control saves.

Roll-up summaries calculate values such as count, sum, min, or max from child records in master-detail relationships. Picklists and dashboards are not child record sources.

Schema Builder is a visual tool for managing the data model. Reports, users, and flows are managed elsewhere.

Record types control which fields, picklist values, and page layouts are available for a business process. They are not rows, layouts, or profiles.

Compact layouts display important fields in small cards on record pages and in the mobile app. Report, search, and form layouts are different.

Custom objects store business data, lookups link records, master-detail is a parent-child relationship, and roll-up summaries aggregate child values.

Lightning App Builder is a drag-and-drop tool for Lightning pages. Apex, user management, and reports are separate features.

Lightning App Builder supports Home, Record, App, and utility pages. It is not limited to records, reports, or dashboards.

A Lightning app bundles navigation, tabs, and pages for users. Reports, dashboards, and flows are different artifacts.

Lightning components are reusable UI elements. Tables, security settings, and profiles are not UI components.

Tabs provide navigation to objects, apps, and pages. Reports, dashboards, and records are content, not navigation entries.

A utility bar gives users persistent tools such as notes or chat in Lightning apps. It is not a report, dashboard, or form.

Lightning App Builder arranges record page components. Schema Builder manages data, Process Builder automates, and Report Builder creates reports.

Quick actions are buttons that perform tasks such as logging a call or creating a record. Reports, dashboards, and profiles are not actions.

Responsive layouts let components rearrange and scale for desktop and mobile. Fixed layouts, CSS files, and themes are different.

Lightning apps bundle navigation, tabs provide entries, quick actions perform tasks, and utility bars offer persistent tools.

Object permissions control record-level operations such as read, create, edit, and delete. Field permissions control fields, and layouts or dashboards are different.

Field-level security controls who can see and edit a field. Formulas, validation rules, and reports are different features.

Profiles define base settings and permissions for users. Records, tabs, and reports are not permission collections.

Permission sets extend user access without modifying profiles. They are not profiles, report folders, or dashboards.

Org-wide defaults set the baseline access level for records of an object. Layouts, validation rules, and flows are different.

Sharing rules extend access to selected groups using ownership or criteria rules. They do not remove access, change fields, or create reports.

Roles form a hierarchy used by record access and reporting. They are not permission sets, layouts, or dashboards.

View All bypasses sharing rules for records of an object. It does not by itself grant report creation or field editing.

Record types can restrict picklist values per business process. Profiles control permissions, and flows or dashboards are different.

Profiles set base permissions, permission sets add extras, field-level security controls fields, and org-wide defaults set baseline record access.

Validation rules use formulas to block saves that fail the condition. Flows automate, and reports or dashboards display data.

Flows automate business processes by collecting data and performing actions. Reports, dashboards, and fields are different.

Validation rule formulas return true when the record should be blocked. They do not return record IDs, reports, or dashboards.

Quick actions can create records, log activities, or launch flows. They do not display reports, change permissions, or delete fields.

Approval processes route records to approvers and record decisions. Reports, dashboards, and validation rules are different.

Picklists restrict data entry to allowed values. Rich text stores large text, formulas calculate, and email actions send messages.

Screen components let flows display and collect information. Reports, dashboards, and profiles are not flow UI elements.

Formula fields compute values from fields and functions. Input fields store data, relationships link records, and notifications are actions.

Screen flows guide users through steps with screens. Reports and dashboards display data, and validation rules block bad saves.

Validation rules block bad saves, flows automate steps, approval processes route decisions, and quick actions launch tasks.

Change sets move selected metadata between connected orgs. Reports, dashboards, and flows are content, not deployment containers.

Sandboxes are isolated copies for development and testing. Production orgs are live environments, and reports or dashboards are content.

Managed packages are versioned and upgradeable for distribution. Custom objects, flows, and reports are package components, not packages themselves.

Unmanaged packages are simpler to share but do not support versioning or upgrades. They differ from managed packages, sandboxes, and dashboards.

AppExchange is Salesforce marketplace where users install apps and components. It is not a report, dashboard, or sandbox.

Package versions are snapshots of package metadata that can be distributed and installed. Profiles, tabs, and reports are metadata within the package.

An install key protects package installation. It is not a field type, dashboard, or report.

Change sets and packages move metadata to production. Reports, dashboards, and validation rules are components that can be moved, not deployment tools.

Release tags identify package versions that are ready for release. Flows, tabs, and reports are metadata, not version labels.

Change sets move metadata, sandboxes provide test environments, managed packages are versioned, and AppExchange is the marketplace.

The Salesforce mobile app gives users access to records and features on phones and tablets. It is not desktop-only, a reports app, or a flow app.

Mobile smart actions are quick actions placed on mobile record pages. Reports, dashboards, and flows are different features.

Mobile navigation items are tabs and actions available in the mobile app navigation. Reports, dashboards, and fields are content.

Lightning App Builder configures app and mobile navigation. Schema Builder manages data, Report Builder builds reports, and Data Import Wizard imports records.

Offline access lets users work with selected records without a live connection. It is not deletion, reporting, or full data sync.

Compact layouts display important fields in small cards that fit mobile screens. Showing every field, storing files, or sending emails are different.

Push notifications deliver messages to mobile devices. Reports, dashboards, and validation rules are not device messages.

Mobile page optimization arranges components so pages work well on small screens. Adding fields, disabling navigation, or creating reports are not optimization.

Quick actions and global actions give users shortcuts to create records from mobile home screens. Reports and dashboards display data, and flows automate.

Mobile smart actions place tasks on record pages, compact layouts show key fields, offline access works without a connection, and push notifications alert devices.