Examkin

Question

Difficulty: MediumStandard and Custom Object Management

A Salesforce administrator at a commercial real estate management firm is configuring schema management options for tracking properties. The administrator needs to evaluate the baseline architectural capabilities and limitations of standard objects compared to custom objects. Which TWO statements accurately describe the differences between standard and custom object management in Salesforce? (Select 2)

  1. Custom objects can be deleted from the organization if they have no active dependencies, whereas standard objects cannot be deleted.Answer
  2. Standard field labels can be renamed, but standard fields cannot be deleted from standard or custom objects.Answer
  3. C
    Roll-up summary fields can be created on standard objects to aggregate data from custom objects connected via a lookup relationship.
  4. D
    Deleting a master record in a lookup relationship automatically soft-deletes all associated child records on a custom object.

Answer

Custom objects can be deleted if free of dependencies whereas standard objects cannot be deleted, and standard fields cannot be deleted from any object although their labels can be edited.
Custom objects can be completely deleted from an org provided there are no dependent components referencing them, whereas standard objects built into Salesforce cannot be deleted. Additionally, while standard field labels can be edited, the standard fields themselves cannot be deleted from either standard or custom objects.

Step-by-Step Solution

1
Evaluate standard object lifecycle constraints.
Identify that standard objects cannot be removed from the Salesforce schema, while custom objects can be deleted.
Salesforce architecture locks core standard objects in place.
2
Analyze field deletion rules for standard fields across standard and custom objects.
Confirm that standard fields built into objects (such as CreatedBy or Name fields) can have their labels edited but cannot be deleted.
Standard fields are fundamental to system baseline operations.
3
Evaluate relationship aggregation rules.
Recognize that lookup relationships do not support native roll-up summary fields.
Native roll-up summary capability is strictly limited to the parent side of a Master-Detail relationship.

Key Concept

Standard vs Custom Object capabilities and schema limitations
Rate this question

Topics

Standard and Custom Object Management

More questions from this topic