To answer this question, let's go through each option to understand why it is correct or incorrect:
Option A) It requires dedicated space for each child record on a view - This option is incorrect. Multi-value groups (MVGs) do not require dedicated space for each child record on a view. MVGs are used to display and manage related child records within a parent record, but they do not require additional space on the view.
Option B) Multi-value field is required for an MVG - This option is correct. To create an MVG, a multi-value field is required. A multi-value field allows multiple values to be selected or associated with a single record. MVGs are used to display and manage related child records within a parent record using a multi-value field.
Option C) It is an alternative to a detail view for managing parent and related child records - This option is correct. MVGs are an alternative to detail views for managing parent and related child records. They allow users to view and interact with related child records directly within the parent record, without having to navigate to a separate detail view.
Option D) It cannot be built on M:M relationships - This option is incorrect. MVGs can be built on M:M (many-to-many) relationships. MVGs provide a way to display and manage related child records for any type of relationship, including M:M relationships.
The correct answers are B) Multi-value field is required for an MVG and C) It is an alternative to a detail view for managing parent and related child records. These options are correct because a multi-value field is required to create an MVG, and MVGs provide an alternative way to manage related child records within a parent record.