Alfresco Subsystems are self-contained, configurable modules that operate within their own isolated Spring Application Context. This context is a child of the main Alfresco application context. Because each subsystem instance has its own private container for its beans, bean names do not need to be globally unique across the entire application. They only need to be unique within the scope of that specific subsystem instance. This architectural design is what prevents bean name collisions and allows for multiple, independent instances of the same subsystem type (e.g., multiple LDAP configurations) to coexist.

A. Subsystems are specifically designed to be manageable via Java Management Extensions (JMX), allowing for dynamic, runtime server configuration and monitoring.

B. A primary feature of subsystems is the ability to use a single template Spring configuration to create multiple instances, each with its own distinct parameters.

D. The use of a private container for beans serves to encapsulate and hide implementation specifics from the global context, not make them visible.

1. Alfresco Content Services 7.4 Documentation, "Subsystems": This official documentation describes the core architecture. It states, "Each subsystem has its own isolated Spring application context... This means that you can have multiple instances of a subsystem, each with its own configuration." This directly supports the correctness of option C and refutes option B.

Reference Section: "Subsystems" overview.

2. Alfresco Content Services 7.4 Documentation, "Managing subsystems": This section details the JMX-based management capabilities. It explicitly states, "Subsystems are manageable via JMX... You can view and change the settings for a subsystem while the Alfresco Content Services server is running." This directly refutes option A.

Reference Section: "Managing subsystems".

3. Alfresco Content Services 7.4 Documentation, "Subsystem configuration files": This page explains how subsystem instances are created from categories (templates). It notes, "A subsystem category is a type of subsystem. It is a template for creating one or more subsystem instances with the same or different settings." This further reinforces why option B is incorrect.

Reference Section: "Subsystem configuration files".