ADVANCED-ADMINISTRATOR practice question 8 of 30
AW Computers has enabled the feature for Contact to multiple Accounts. A rep is trying to remove the primary Account from a Contact but Is unable to do so. The administrator has already updated the page layout to no longer require an Account. What could be the issue?
Full set: 222 questionsThe AccountId field on the Contact object, which represents the primary account relationship, is a system-required field at the database level. Even when the "Contacts to Multiple Accounts" feature is enabled, every contact must have a direct relationship with one primary account. Modifying the page layout to make the Account Name field not required only changes the user interface presentation; it does not alter the underlying data model rule that mandates a value for this field upon saving the record. Therefore, the user is prevented from removing the primary account because it is a fundamental system requirement.
B. The Contact has Indirect relationships to other Accounts. The existence of indirect relationships does not prevent the removal or modification of the primary account; the system's requirement for a primary account is the actual constraint.
C. The Account Contact relationship record needs to be deleted first In order to disassociate Contact from the Account. This applies to removing indirect relationships, which are stored in the AccountContactRelation object. The primary relationship is a direct lookup on the Contact record itself.
D. Private Contacts need to be enabled in Setup. While enabling "Allow users to create contacts without an account" would permit a contact to exist without an account, it is a separate setting. The default behavior, even with "Contacts to Multiple Accounts," requires a primary account.
1. Salesforce Help Documentation, "Set Up Contacts to Multiple Accounts": This document states, "Every contact needs to be associated with a primary account. The primary account is the one in the Account Name field on the contact record." This confirms the mandatory nature of the primary relationship. (Salesforce Help, Article 000384489, "Set Up Contacts to Multiple Accounts", Section: "How Contacts to Multiple Accounts Works").
2. Salesforce Help Documentation, "Considerations for Using Contacts to Multiple Accounts": This guide clarifies the distinction and permanence of the primary relationship: "The relationship between a contact and the account in the Account Name field is a direct relationship... Even with Contacts to Multiple Accounts, accounts and contacts still have a one-to-many relationship." This reinforces that the original, required lookup relationship remains intact. (Salesforce Help, Article 000384490, "Considerations for Using Contacts to Multiple Accounts", Section: "Relationships and Deletion").
3. Salesforce Object Reference Guide, Contact Object: The documentation for the Contact standard object specifies the properties of the AccountId field. It is a required Lookup(Account) field, meaning the database schema enforces that it cannot be null, except when the specific "Private Contacts" feature is enabled. (Salesforce Developer Documentation, Standard Objects, Contact, Field: AccountId).
Keep practicing
Take the free ADVANCED-ADMINISTRATOR practice test
Ten exam-style questions with answers and explanations, plus the exam facts and study guides.
More questions
Other ADVANCED-ADMINISTRATOR practice questions
- Question 1An administrator is using the Dev Console Log Inspector to troubleshoot a Process Builder…
- Question 2The sales agents at DreamHouse Realty have a profile that allows them to import records f…
- Question 3An administrator needs to Import a large amount of historical data (more than 100,000 rec…
- Question 4Administrator has been tasked with creating a new custom field on the Account object call…
- Question 5Cloud Kicks (CK) wants the forecast numbers to be shown by territory regardless of who ow…
- Question 6The administrator at Cloud Kicks created a flow in a sandbox that walks service agents th…
