Práctica de Administrador de Salesforce

A Salesforce org is the configured instance a company uses. It contains users, objects, apps, and settings. Report folders, layouts, and workflows are parts of the org, not the org itself.

An object is like a database table that stores records. Account and Contact are standard objects. Dashboards, templates, and profiles are different features.

A field is a column or attribute that stores a value for each record. A record is a row, and roles and filters are separate concepts.

A record is one row in an object, such as a single Account or Contact. Report types, dashboard components, and permission sets are not records.

Account is a standard object included in Salesforce. Custom Invoice and other custom objects are created by administrators to meet specific needs.

A custom object is created by an administrator to store data that standard objects do not cover. It can have custom fields, relationships, and page layouts.

An app groups tabs, objects, and tools for a specific job function. It organizes the user interface, while records and emails are different.

A tab provides navigation to an object, list view, or custom page. Tabs are not fields, filters, or sharing rules.

A list view is a saved set of filters and columns that shows selected records. Page layouts, charts, and approvals are different features.

A page layout controls which fields, buttons, and related lists appear on a record page. It is not a report type, rule, or hierarchy.

A record type lets different kinds of records on the same object use different picklist values and page layouts. It is not a row, object, or dashboard.

A lookup relationship connects records and allows the parent record to be optional. Master-detail makes the parent required and controls child behavior.

In a master-detail relationship, the master record controls the detail record, and the detail record cannot exist without the master. Lookup is the more flexible option.

A formula field computes a value from other fields and functions. It is read-only and recalculates when referenced data changes.

This statement is true. Administrators can create custom objects and custom fields to store data that standard objects do not cover.

A record is a single row in an object. Each record stores values in fields and can be displayed, edited, reported on, and shared.

Field-level security controls field visibility and editability for profiles. It does not control records, emails, or dashboard colors.

A picklist field lets users choose one value from a predefined list. Checkboxes, numbers, and lookups are different field types.

A checkbox field stores a true or false value. It is commonly used for flags and yes/no settings.

A validation rule uses a formula to reject records that do not meet business rules. It prevents bad data from being saved.

A profile defines a user type and includes permissions, settings, and access to objects, tabs, and fields. Each user is assigned one profile.

A permission set adds permissions and access settings on top of a profile. It lets admins grant specific capabilities without editing the profile.

Roles form a hierarchy that controls how much record data users can see through the sharing model. Roles are not fields, charts, or templates.

Organization-wide defaults set the baseline access for records on each object. Sharing rules can then extend access to specific users or groups.

Sharing rules open access to records for specific users, groups, or roles beyond the organization-wide default. They do not validate fields or filter dashboards.

A public group is a collection of users, roles, or other groups used in sharing rules, queues, and assignments. It is not a profile or role.

A queue holds records until a member of the queue claims or is assigned them. It helps teams share workload without a single owner.

Record ownership identifies the user or queue responsible for a record. Ownership affects access and reporting in Salesforce.

The sharing model combines organization-wide defaults, sharing rules, manual sharing, and role hierarchy to determine record access.

This statement is true. Permission sets add permissions to users without modifying their assigned profile, which is useful for granting limited extra access.

A validation rule blocks saving a record when its formula returns true. It enforces business requirements and prevents invalid data.

A workflow rule triggers actions such as email alerts, field updates, or tasks when record criteria are met. It is a classic declarative automation tool.

An approval process routes records through steps where designated approvers can approve or reject them. It is not a report or tab.

Process Builder lets admins create declarative automation that runs when records are created or edited. Flow is the newer recommended tool.

Flow is the current declarative automation tool that can create screens, update records, send emails, and run logic without code.

A scheduled flow runs at a specified time or interval. Record-triggered flows run when records are created or updated.

Assignment rules route leads or cases to users or queues based on criteria. They are not layouts, security settings, or filters.

An email alert sends a configured email when an automation action runs. Workflow rules, Process Builder, and flows can send email alerts.

A time trigger in workflow rules or flows runs actions before or after a date field. It is not a filter, field, or role.

A public group is a reusable collection of users, roles, or other groups. It simplifies sharing rules, queues, and assignments.

A report displays records from one or more objects with filters, groupings, and totals. Dashboards visualize report data.

A report type determines the primary object and related objects available in a report. It controls which records can be included.

Report folders store reports and control access through folder sharing. They do not define layouts, components, or validation.

A dashboard displays report data visually using charts and components. It summarizes key metrics for users.

A dashboard component is one visual element, such as a chart or table, placed on a dashboard. Multiple components make up a dashboard.

A report filter narrows the records shown based on field values. Filters are essential for meaningful reports.

A report subscription emails report results to users at a scheduled time. Dashboards have similar subscriptions.

A dashboard subscription sends a scheduled email with a snapshot of the dashboard. It helps users monitor metrics without logging in.

A custom report type lets admins build reports around custom objects and relationships. Standard report types cover common objects.

A joined report combines multiple report blocks, such as different objects, in one report. It is useful for comparing data side by side.

A summary report groups rows and can show totals and subtotals. It is more structured than a tabular report.

A matrix report groups data by rows and columns and can display totals in both directions. It is useful for comparing two dimensions.

A tabular report is a simple list of records with no grouping or totals. It is the basic report format.

This statement is true. Dashboards use charts and components to visualize data from reports, which makes key metrics easier to understand at a glance.

This statement is true. Report subscriptions send scheduled emails with report results to selected users.

This statement is true. Many users can share the same profile, which defines their baseline permissions and settings.

This statement is false. Roles affect visibility through the hierarchy, but organization-wide defaults and sharing rules also control record access.

The User object stores user accounts, including names, emails, profiles, roles, and settings. It is a standard Salesforce object.

An external user has limited access through communities or portals. External users typically see only the data their profile and sharing settings allow.

A sandbox is an isolated copy of a Salesforce org used for testing changes safely. It is not a folder, role, or dashboard.