Question: In Mission Critical (MC) service groups, when sharing group configuration between a primary MC system and an interconnected partner MC system, what can the group management server in each system modify before providing/storing the configuration?
Option 1: Only the communication protocol used for group messaging
Option 2: The list of members within their own system, priority of the group, or permitted locations for service
Option 3: Both the primary and partner MC systems' group management servers can modify configuration parameters (e.g., member lists, group priority, permitted locations) based on their respective policies and requirements.
Option 4: Neither system's group management server can modify the configuration; it must be accepted as is.
Explanation: This is correct because, according to the specifications, both the primary MC system's group management server (which may modify configurations like member lists before sharing) and the partner MC system's group management server (which can adjust settings such as priority or permitted locations for service within its domain) have the capability to make changes based on their internal policies and requirements. This flexibility is crucial for maintaining control over how mission-critical services are managed across interconnected systems while ensuring security and compliance with varying operational needs.