Universal Containers would like applicants to apply for multiple positions, tracking how many applicants have applied and how many positions each individual applicant has applied for. To do this, the administrator will create a Job Application junction object between the Applicant and Position objects.
How does this action meet the requirement?
The junction object allows a many-to-many relationship between the Applicant and Position objects, enabling the tracking of how many applicants have applied for each position and how many positions each individual applicant has applied for. Additionally, the junction object allows the use of roll-up summary fields, which can aggregate data such as the number of applications per position or per applicant. This meets the requirement to track the information without the need for custom code.
A…Duplicate records if junction object is not used B... Updating the applicant and position fields is unnecessary for the requirement to track numbers C…It is not necessary to refer to the summary field of the parent object in the junction object D…Aggregate the number of records of the junction object with the parent object
I am sorry, I made a mistake. Correct the answer to C because the junction object is a child, not a master.
B. Territory hierarchy replaces the role hierarchy for sharing and D. Support for complex and frequently changed sales organization structures are the two capabilities of Territory Management.
Can’t be D because A junction object is not a master to either the Position or Applicant objects. It's a child object in a master-detail relationship with both.