Examkin

Soru

Zorluk: OrtaObject Relationships (Lookup, Master-Detail, Many-to-Many)

An administrator at a global media distribution company needs to create a custom data model to link Media Content (Media_Content__c) records with Distribution Territory (Distribution_Territory__c) records. Each media content item can be released in multiple territories, and each territory can host multiple content items. The requirements specify that deleting a media content item or a territory record must automatically delete its corresponding relationship records. Additionally, executives want to view a real-time total count of associated territories directly on each Media Content record. Which two configuration steps should the administrator take to fulfill these requirements? Choose 2 answers.

  1. Create a custom junction object that includes a Master-Detail relationship field to Media Content and a Master-Detail relationship field to Distribution Territory.Cevap
  2. Create a Roll-Up Summary field of type COUNT on the Media Content object referencing the junction object records.Cevap
  3. C
    Create a custom junction object that includes two Lookup relationship fields and enable record-level cascading deletes on both relationships.
  4. D
    Create a Roll-Up Summary field on the Distribution Territory object that references a Lookup relationship on the junction object.

Cevap

The administrator should create a custom junction object with two Master-Detail relationship fields pointing to Media Content and Distribution Territory, and create a Roll-Up Summary field of type COUNT on the Media Content object referencing the junction object.
To fulfill a many-to-many requirement with cascading deletion behavior, an administrator must construct a junction object linked by two Master-Detail relationships. Because the Media Content object acts as a master in one of these Master-Detail relationships, the administrator can build a Roll-Up Summary field of type COUNT on Media Content to calculate the total number of associated records.

Adım Adım Çözüm

1
Analyze the relationship structure requirements.
Since both entities require a multi-directional link (many-to-many), a custom junction object is required.
Salesforce achieves many-to-many relationships using a junction object situated between two master objects.
2
Evaluate deletion cascade and security inheritance rules.
Select Master-Detail relationships for both sides of the junction object.
Master-Detail relationships ensure that deleting either parent record automatically cascade-deletes the junction record.
3
Determine how to calculate the total count of related territories on Media Content.
Create a Roll-Up Summary field with the COUNT aggregate function on the Media Content master object.
Roll-Up Summary fields are only natively supported on the parent/master side of a Master-Detail relationship.

Anahtar Kavram

Many-to-Many Relationships and Roll-Up Summary Requirements
Bu soruyu puanla

Konular

Object Relationships (Lookup, Master-Detail, Many-to-Many)

Bu konudan daha fazla soru