M.Sc Data Science Big Data Reference Architecture Taxonomy — practice questions

1. The summary list of the five central roles gives each one a single defining clause, and this is the System Orchestrator's. 2. It reads: "System Orchestrator: Defines and integrates the required data application activities into an operational vertical system." 3. The section on the role expands it: the System Orchestrator "provides the overarching requirements that the system must fulfill, including policy, governance, architecture, resources, and business requirements, as well as monitoring or auditing activities to ensure that the system complies with those requirements." 4. So it is the role that sets the terms everyone else works to, supplying "system requirements, high-level design, and monitoring for the data system". 5. The Data Provider "introduces new data or information feeds into the Big Data system", the Data Consumer uses the results, and the Big Data Framework Provider supplies the computing framework. None of them integrates activities into a system. 6. The volume adds a useful note: this role "predates Big Data systems", though some of its design activities have changed within the Big Data paradigm. _Source: NIST SP 1500-2r2 "NIST Big Data Interoperability Framework: Volume 2, Big Data Taxonomies" (Nov 2019), p.6 section 2.1 "Actors and Roles"_

1. The summary list is explicit: "Data Provider: Introduces new data or information feeds into the Big Data system." 2. The word feeds matters. A Data Provider is not only a one-off source of a dataset; it can be a continuing stream into the system. 3. The Data Consumer is the mirror image, defined as including "end users or other systems who use the results of the Big Data Application Provider". Data flows in through the Provider and out through the Consumer. 4. The System Orchestrator sets requirements rather than supplying data, though it does specify "Data Provider contracts and service-level agreements (SLAs)" as part of its business ownership duties. 5. The Big Data Framework Provider "establishes a computing framework in which to execute certain transformation applications while protecting the privacy and integrity of data", which is infrastructure rather than input. _Source: NIST SP 1500-2r2 "NIST Big Data Interoperability Framework: Volume 2, Big Data Taxonomies" (Nov 2019), p.6 section 2.1 "Actors and Roles"_

1. The volume names them in a short list of their own: "The two fabrics, which are discussed separately in Sections 3 and 4, are: Security and Privacy Fabric; Management Fabric." 2. So there are exactly two, and they are Security and Privacy, and Management. 3. They are separated from the five components because they cannot be confined to one place. Volume 1 defines a fabric as "the presence of activities and components throughout a computing system", and the volume describes these two as "interwoven in the five components". 4. Governance is the most tempting wrong answer because it is genuinely important here, but the volume places it inside the System Orchestrator's responsibilities rather than treating it as a fabric. 5. Data provenance and resource negotiation are both real terms in this framework, describing where data came from and the built-in management capabilities of a platform, but neither is one of the two fabrics. _Source: NIST SP 1500-2r2 "NIST Big Data Interoperability Framework: Volume 2, Big Data Taxonomies" (Nov 2019), p.6 section 2.1 "Actors and Roles"_