The correct answer is D. In FileNet Content Manager and CP4BA Content Services, document metadata is governed primarily through the document class model. A document class defines the properties of a document, organizes documents by type in an object store, and determines how metadata applies to documents created under that class. When a property is assigned to a document class, new documents and new versions based on that class inherit the property. A document may then hold a specific value for the inherited property, but the availability and structure of the property are class-driven. Object stores contain classes and repository configuration, but they do not by themselves determine every document property. Security controls access and permissions, not the metadata schema. Properties are not normally assigned ad hoc to every document as an isolated design practice; they are defined through property templates and assigned to classes, where they become available to document instances. References/topics: FileNet Content Manager, Content Services, document class, property templates, inherited properties, object store metadata model.

Business Automation Insights processes fixed-format events by first accepting them as raw events and then transforming them into analytical event structures suitable for monitoring, visualization, and aggregation. The two correct processed forms are time series and summaries. Time series events are flattened, simplified versions of raw events, designed to make operational data easier to query, index, and visualize in analytics tooling. Summaries are higher-level aggregations derived from time series, representing current or final state information for process, activity, case, or related business entities. BPMN is not the processed output type; it is a source event domain or event family. Variable and Static are not BAI processed event types. BAI uses processing jobs to convert emitted operational events into consumable structures that support dashboards, KPI inspection, and operational analytics. References/topics: Business Automation Insights, Fixed-format event emission, Event formats, Event types, Flink jobs for event types.

The correct answer is D. Automation Decision Services is designed around Git-based collaboration for decision automations and decision services. Each decision automation can be connected to a remote Git repository, allowing team members to work collaboratively, isolate changes in branches, and share decision-service artifacts through a governed repository model. This supports modern change management because decision services are versioned, branched, reviewed, shared, and synchronized through Git rather than through legacy source-control technologies. CVS and Subversion are not the repository integration model used by ADS in Cloud Pak for Business Automation. A local Git repository alone is also insufficient because the integration requirement is collaboration with a remote repository configured through the platform's Git provider mechanism. In architecture terms, the Git provider becomes the persistence and collaboration backbone for decision automation assets, while Decision Designer provides the authoring experience. The repository connection also supports team development, publication, backup, and controlled promotion of decision-service changes. References/topics: Automation Decision Services, Decision automations, Git provider configuration, Remote Git repository, Branching and sharing decision services.