Chapter 3: 3. Data Management, Quality and Research Governance1. IntroductionContemporary information technology research depends on data that are diverse, abundant, and continually generated. Doctoral researchers may work with relational databases, sensor streams, transaction records, interview transcripts, images, social-media content, software repositories, or administrative datasets. Although analytical methods receive substantial attention, the validity of research findings is often determined earlier: by how data are collected, documented, protected, cleaned, transformed, and governed. Data management is therefore not an administrative activity that begins after data collection. It is a research-design responsibility. Poorly specified variables, inconsistent identifiers, undocumented transformations, insecure storage, and uncontrolled access can undermine a study even when sophisticated statistical or machine-learning techniques are used. Conversely, a well-governed dataset supports reproducibility, defensible interpretation, efficient collaboration, and responsible reuse. This chapter examines the management of structured and unstructured data across the research lifecycle. It addresses data quality, missingness, bias, metadata, provenance, privacy, security, regulatory compliance, and research governance. Particular attention is given to the relationship between technical controls and scholarly judgment. Governance frameworks cannot eliminate uncertainty; they provide structures through which uncertainty, risk, accountability, and ethical obligations can be managed transparently. 2. Learning ObjectivesBy the end of this chapter, doctoral researchers should be able to: 1. Explain the concepts of data management, data quality, metadata, provenance, and research governance. 2. Design a lifecycle for collecting, storing, cleaning, transforming, sharing, archiving, and disposing of research data. 3. Distinguish structured, semi-structured, and unstructured data and select appropriate management strategies. 4. Diagnose missingness, measurement error, bias, duplication, inconsistency, and other quality problems. 5. Apply principles of privacy, information security, consent, anonymisation, and regulatory compliance. 6. Evaluate the methodological and managerial consequences of data-management decisions. 7. Develop a defensible data-management plan for a doctoral research project. 3. Meaning and ConceptData managementData management is the systematic planning, organisation, documentation, storage, protection, processing, sharing, preservation, and disposal of data. It includes both technical operations and institutional arrangements. A data-management plan normally specifies what data will be created or obtained, who will control them, how quality will be assessed, where they will be stored, how access will be managed, and how long they will be retained. Data qualityData quality is the fitness of data for a defined purpose. Quality is not an absolute property. A dataset can be sufficiently accurate for exploratory analysis but unsuitable for regulatory reporting. Common dimensions include accuracy, completeness, consistency, timeliness, validity, uniqueness, and relevance. These dimensions may conflict. For example, rapidly collected data may be timely but less complete, while extensive validation may improve accuracy at the cost of delay. Structured and unstructured dataStructured data conform to a predefined schema, such as rows and columns in a relational table. Unstructured data lack a fixed tabular structure and include natural-language documents, audio, video, images, and open-ended web content. Semi-structured data, such as JSON, XML, and application logs, contain tags or hierarchical fields but may vary across records. Effective management requires recognising that different forms of data need different schemas, quality checks, storage systems, and interpretive procedures. Research governanceResearch governance is the system of policies, roles, procedures, controls, and oversight mechanisms through which research is conducted responsibly. It covers ethical review, legal compliance, participant protection, accountability, security, data access, conflicts of interest, authorship, records management, and institutional risk. Governance is broader than ethics approval: it continues throughout collection, analysis, dissemination, and archiving. 4. Fundamental PrinciplesSeveral principles provide a foundation for responsible data management. Fitness for purpose. Data should be evaluated against the research question and intended use. Researchers should define acceptable error, completeness, and timeliness before analysis rather than changing standards after seeing results. Provenance and traceability. Every important dataset should have an identifiable origin and a record of how it was acquired, modified, merged, sampled, and analysed. A reader should be able to understand the path from source data to reported findings. Documentation by design. Metadata, codebooks, processing logs, and decision records should be created during the project. Reconstructing decisions months later is unreliable and often impossible. Security and proportionality. Controls should reflect the sensitivity and potential harm associated with the data. Sensitive personal data require stronger safeguards than genuinely public, non-identifiable information. Minimum necessary access. Individuals should receive only the access required for their role. This reduces accidental disclosure and limits the consequences of compromised accounts. Reproducibility and transparency. Data-management decisions, analytical code, software versions, and limitations should be documented sufficiently for qualified researchers to inspect or reproduce the work, subject to privacy and confidentiality restrictions. Respect for persons and communities. Data subjects should not be treated merely as data points. Consent, dignity, cultural expectations, group interests, and the possibility of downstream harm must be considered. Lifecycle responsibility. Data require governance from planning through destruction or preservation. Retention should be justified, and disposal should be secure and verifiable. 5. Major Components / ElementsData planning and classificationA data-management plan identifies data types, sources, expected volume, formats, owners, sensitivity, retention requirements, and access conditions. Classification schemes commonly distinguish public, internal, confidential, and highly restricted information. Classification should consider direct identifiers, quasi-identifiers, commercial sensitivity, intellectual property, security implications, and the possibility of re-identification when datasets are linked. Collection and acquisitionCollection procedures should define sampling, instruments, recruitment, consent, inclusion and exclusion criteria, timestamps, file naming, and quality checks. Acquired datasets require assessment of licensing, representativeness, documentation, known limitations, and the legality of secondary use. Web-scraped or platform-generated data may appear public while still involving privacy, contractual, or ethical concerns. MetadataMetadata are data about data. Descriptive metadata explain subject, creator, date, and purpose. Structural metadata describe relationships among files, tables, fields, and records. Administrative and technical metadata describe access rights, file formats, software, preservation actions, and retention. A variable called “status” is inadequate without a definition, permitted values, coding rules, unit of measurement, source, and collection date. ProvenanceProvenance records the history of an object or dataset. It may include the original source, responsible agent, acquisition time, software used, transformation sequence, and links to derived outputs. Provenance is especially important in computational research, where a final table may result from many scripts, filters, joins, and manually corrected records. Storage and backupPrimary storage should be reliable, access-controlled, and appropriate to the data classification. Backups should be automated, tested, geographically or logically separated from primary storage, and protected against ransomware. The familiar 3-2-1 principle recommends maintaining at least three copies, on two different media or systems, with one copy stored separately. Backup is not the same as archiving: backups support recovery from loss, whereas archives support long-term preservation and future interpretation. Cleaning and transformationCleaning detects and corrects errors, while transformation changes data representation for analysis. Activities may include standardising dates, resolving duplicate entities, validating ranges, correcting inconsistent categories, tokenising text, scaling numerical variables, or converting file formats. Every intervention should be recorded. Silent correction is dangerous because it conceals researcher judgment and prevents auditing. Access and sharingAccess policies should specify who may use data, for which purposes, under what conditions, and for how long. Sharing may involve open publication, controlled-access repositories, data-use agreements, secure analysis environments, or sharing only aggregate results. The most open option is not always the most responsible option. Retention and disposalRetention schedules should reflect legal obligations, funder requirements, scholarly value, contractual conditions, and participant expectations. When data are no longer required, disposal should include secure deletion, destruction of physical media, removal of replicated copies where feasible, and documentation of the action. Some records may need preservation even after working files are deleted. 6. Process / Framework / MethodologyA practical lifecycle framework consists of eight connected stages. Stage 1: Define requirements. Translate research questions into data requirements. Identify units of analysis, variables, temporal coverage, acceptable quality thresholds, sensitivity, and anticipated outputs. Stage 2: Design collection. Establish instruments, sampling procedures, consent language, identifiers, validation rules, and procedures for recording refusals or missing observations. Pilot testing often detects ambiguous questions and technical failures before large-scale collection. Stage 3: Register and ingest. Assign persistent identifiers, record acquisition details, preserve original files as read-only objects, and create an inventory. Original data should not be overwritten by cleaned versions. Stage 4: Assess quality. Profile data for missing values, duplicates, invalid formats, outliers, impossible values, inconsistent coding, and unexpected distributions. Quality assessment should combine automated rules with subject-matter review. Stage 5: Clean and transform. Create controlled working copies, apply documented rules, and distinguish correction from imputation. Maintain a change log and, where possible, use scripts rather than undocumented manual edits. Stage 6: Analyse and monitor. Track versions of datasets, code, packages, models, and outputs. Monitor drift when data arrive continuously. A model developed on historical data may become unreliable when populations, systems, or behaviours change. Stage 7: Share or preserve. Prepare a suitable data package containing documentation, code, metadata, licences, and a statement of limitations. De-identify or restrict sensitive material before deposit. Stage 8: Review and dispose. Conduct periodic access and retention reviews. Revoke unnecessary permissions, confirm archival integrity, and securely dispose of data that no longer have a justified purpose. A governance matrix can assign responsibilities for each stage. For example, a principal investigator may be accountable for lawful purpose and scientific use, a data steward for quality and documentation, an information-security officer for technical controls, and analysts for following approved procedures. 7. Important Theories and ModelsTotal Data Quality ManagementTotal Data Quality Management treats quality as an organisational process rather than a one-time cleansing exercise. It links quality requirements to users, processes, systems, and continuous improvement. The model encourages researchers to identify critical data elements, define quality metrics, locate root causes, and improve collection processes rather than repeatedly repairing downstream errors. The data-information-knowledge distinctionData are recorded observations; information is organised data interpreted in context; knowledge involves justified understanding and action. This distinction explains why technically complete data may still be scientifically weak. A large dataset without meaningful definitions, context, or provenance does not automatically produce reliable knowledge. FAIR principlesThe FAIR principles state that research resources should be Findable, Accessible, Interoperable, and Reusable. Findability requires identifiers and rich metadata. Accessibility requires appropriate retrieval protocols, even when access is restricted. Interoperability requires shared formats, vocabularies, and standards. Reusability requires clear licences, provenance, and quality documentation. FAIR does not mean that every dataset must be openly downloadable. CIA security triadConfidentiality protects information from unauthorised disclosure. Integrity protects it from unauthorised or accidental alteration. Availability ensures that authorised users can access it when needed. Research systems require all three. For example, encryption may support confidentiality, checksums and audit logs support integrity, and tested backups support availability. Data life-cycle and records-continuum perspectivesThe lifecycle perspective emphasises sequential stages from creation to disposal. The records-continuum perspective views creation, management, access, and preservation as overlapping responsibilities rather than isolated phases. The latter is useful for digital research because metadata, ownership, and access decisions must often be made at the moment data are created. Missing-data mechanismsMissingness is commonly discussed through three mechanisms. Missing completely at random (MCAR) means missingness is unrelated to observed and unobserved values. Missing at random (MAR) means missingness is related to observed information after relevant variables are considered. Missing not at random (MNAR) means missingness depends on unobserved or missing values themselves. These are assumptions about a data-generating process, not labels that can be proven solely by inspecting a dataset. The choice among deletion, weighting, imputation, sensitivity analysis, or explicit modelling must be justified. 8. Practical ApplicationsIn quantitative research, quality management may involve range checks, referential integrity, duplicate detection, unit conversion, missingness analysis, and validation against authoritative sources. A financial amount recorded as negative may be valid for a refund, invalid for a quantity, or a sign error; context is essential. In qualitative research, management includes transcription conventions, pseudonyms, version control, coding frameworks, memoing, preservation of contextual notes, and secure handling of audio or video. Removing names from a transcript may not prevent identification if locations, occupations, or unusual events remain. In mixed-methods research, a linking strategy is required. Quantitative records and qualitative cases should be connected through carefully managed identifiers, while protecting confidentiality. Researchers must document whether integration occurs during sampling, data collection, analysis, or interpretation. For machine-learning research, data splitting, leakage prevention, label quality, class imbalance, concept drift, and model versioning are central. A model can achieve high predictive performance because information unavailable at deployment was inadvertently included during training. This is a data-management failure as much as a modelling failure. 9. ExamplesA university survey contains dates in three formats, duplicate respondents, and a substantial number of unanswered income questions. A defensible response is not to delete all incomplete records immediately. The researcher should inspect the survey instrument, determine whether nonresponse is patterned, standardise dates, identify duplicates using documented rules, report missingness, and conduct sensitivity analyses using appropriate methods. A hospital research project combines clinical records with wearable-device data. The records have different patient identifiers, time zones, sampling frequencies, and access restrictions. Before analysis, the team needs an approved linkage procedure, a controlled crosswalk stored separately, common temporal definitions, quality thresholds for device readings, and an audit trail of linkage decisions. A qualitative cybersecurity study collects incident reports from employees. Even if names are removed, rare job titles and event times may identify participants. The team should minimise collected details, use pseudonyms, restrict access to raw reports, assess disclosure risk in quotations, and obtain governance approval for publication examples. 10. Technology and Digital ApplicationsRelational database systems support structured data through schemas, keys, constraints, transactions, and queries. Data warehouses support integrated analytical reporting, while data lakes can store varied raw materials such as logs, documents, and media. A data lake without cataloguing and governance can become a “data swamp,” in which assets are difficult to find or interpret. Metadata catalogues and data dictionaries make datasets discoverable and clarify definitions. Version-control systems support code and documentation management. Workflow and orchestration tools can execute repeatable extraction and transformation pipelines. Containerisation can preserve software environments, although it does not replace documentation or ethical review. Encryption protects data in transit and at rest. Multi-factor authentication, role-based access control, key management, immutable audit logs, and data-loss-prevention controls reduce security risk. De-identification tools can assist with masking or pseudonymisation, but automated methods require human review because context and combinations of attributes may enable re-identification. Reproducible research environments may combine a repository, persistent identifiers, computational notebooks, scripted pipelines, and machine-readable metadata. Technology is valuable only when embedded in appropriate processes. A sophisticated platform cannot compensate for unclear ownership, weak consent, or undocumented decisions. 11. Strategic / Managerial ImportanceData governance affects research credibility, institutional reputation, legal exposure, funding opportunities, and the ability to collaborate. Consistent definitions prevent different teams from producing incompatible results. Clear ownership reduces delays in approving access. Documented pipelines lower the cost of repeating analyses and transferring projects when staff leave. At strategic level, leaders should treat data as an organisational asset with associated liabilities. Investment decisions should consider the value of reuse, the cost of poor quality, the consequences of breaches, and the skills required for stewardship. Governance should enable responsible research rather than create unnecessary bureaucracy. Proportionate controls, service standards, and clear escalation routes are more effective than policies that cannot be implemented. 12. Detailed Case StudyBackgroundThe following is a fictional illustrative case. Northbridge University is conducting a doctoral project on factors associated with student withdrawal from online programmes. The project combines learning-management-system logs, assessment records, demographic information, and interviews with former students. ProblemThe initial dataset contains inconsistent student identifiers, missing demographic values, duplicate log events, different definitions of “active student,” and interview transcripts containing identifiable personal details. Several analysts have copied files to personal devices for convenience. The research team cannot reproduce a published preliminary result because the filtering steps were not recorded. AnalysisThe project has both quality and governance problems. Identifier inconsistency threatens linkage validity. Duplicate events may inflate measures of engagement. Missing demographic information may be associated with students’ willingness to disclose, creating bias. The definition of withdrawal is a construct decision, not merely a technical field selection. Personal-device storage increases confidentiality risk, while absent transformation logs undermine reproducibility. The team performs a data inventory and classifies each source. It identifies which fields are necessary, which are sensitive, and which are not needed for the research question. It also reviews the consent materials and institutional approval to determine whether secondary use and linkage are permitted. Strategy / SolutionThe team establishes a secure project workspace with role-based access and multi-factor authentication. Raw source files are preserved in read-only storage. A separate, restricted crosswalk links institutional identifiers to study identifiers. A data dictionary defines every variable, coding rule, unit, and time reference. The researchers agree on an operational definition of withdrawal and document alternative definitions for sensitivity analysis. Automated checks identify invalid dates, duplicate events, impossible sequences, and missing values. Cleaning is performed through version-controlled scripts. Each derived dataset receives a version number and processing record. For interviews, names and unnecessary contextual details are removed or replaced with pseudonyms. Quotations are reviewed for deductive disclosure. The team creates a missingness report and evaluates whether demographic nonresponse is related to observed variables. Rather than claim that the data are unbiased, the final report describes the likely direction and limits of possible bias. Access is restricted according to role, personal-device copies are removed, and staff receive training on secure handling. An independent reviewer checks the data-management plan, linkage logic, and reproducibility package before publication. OutcomeThe revised analysis shows that the preliminary relationship was partly caused by duplicate log events and an overly broad definition of engagement. The corrected results are weaker but more defensible. The project produces a documented, reusable analytical dataset, approved metadata, code, and a controlled-access archive. No raw identifiable records are released publicly. Learning PointsData quality problems often originate in system design and definitions rather than in statistical analysis. Governance must cover linked datasets and derived files, not only original records. Reproducibility requires preserved inputs, code, versions, and decisions. Finally, transparent acknowledgement of uncertainty is more scholarly than presenting corrected data as perfect data. 13. Advantages / BenefitsEffective data management improves validity, reproducibility, efficiency, collaboration, security, and compliance. It reduces duplicated collection, prevents avoidable analytical errors, and supports legitimate secondary research. Metadata and provenance increase the value of datasets beyond the original project. Strong governance also protects participants, researchers, and institutions from foreseeable harm. 14. Limitations / ChallengesManagement systems require time, funding, technical expertise, and sustained institutional support. Standardisation can oversimplify complex qualitative material or culturally specific meanings. De-identification may reduce analytical utility, while strict access controls may slow collaboration. No method completely eliminates re-identification, bias, measurement error, or insider threat. Researchers must therefore make trade-offs explicit and use proportional controls. 15. Ethical and Governance ConsiderationsConsent should describe collection, linkage, storage, sharing, foreseeable uses, and withdrawal conditions in understandable language. Consent is not a universal solution: a participant may agree to one purpose but not unlimited future uses. Researchers should assess risks to individuals, groups, organisations, and communities, including discrimination, stigmatisation, surveillance, and reputational harm. Privacy requires purpose limitation, data minimisation, accuracy, retention control, and secure processing. Anonymisation removes the possibility of identifying a person only under a defensible assessment; pseudonymisation replaces identifiers but retains a route to re-identification. These concepts must not be confused. Applicable requirements depend on jurisdiction and context and may include data-protection legislation, health-information rules, contractual restrictions, intellectual-property law, records requirements, export controls, and institutional ethics policies. Researchers should seek current legal and institutional advice rather than assuming that one framework applies universally. Governance should also address conflicts of interest, algorithmic fairness, Indigenous or community data sovereignty, authorship, and responsible publication. 16. Current and Emerging TrendsResearch data environments increasingly use cloud infrastructure, automated pipelines, large language models, synthetic data, federated analysis, and privacy-enhancing computation. These developments create opportunities but also new risks. Cloud services require scrutiny of location, subcontractors, access logging, encryption, and exit arrangements. Generative systems may expose confidential inputs or generate inaccurate synthetic records. Federated approaches allow analysis to occur where data are held, reducing the need to transfer raw records. Differential privacy introduces controlled statistical noise to reduce disclosure risk, although it can affect accuracy and requires careful parameter choices. Synthetic data may support testing and teaching, but it should not automatically be treated as equivalent to real data. Regulators and funders increasingly expect demonstrable accountability, algorithmic impact assessment, and reproducible research practices. Automated data-quality monitoring and machine-actionable metadata are likely to become more common, but human oversight remains essential. 17. Best PracticesResearchers should begin a data-management plan before collection and revise it when the project changes. They should preserve raw data separately, use meaningful identifiers, maintain a data dictionary, and record provenance and transformation decisions. Quality checks should be automated where possible but reviewed by domain experts. Access should follow least privilege, with multi-factor authentication, encryption, tested backups, and audit logging for sensitive projects. Teams should use version control for code and documentation, standardise file naming and formats, and test reproducibility before publication. Missingness, exclusion, linkage uncertainty, and known biases should be reported honestly. Sharing should use the least restrictive approach that remains ethically and legally defensible. 18. Future ScopeFuture research will increasingly address governance for continuously generated, multimodal, and machine-created data. Doctoral scholars will need to combine statistical reasoning with data engineering, cybersecurity, privacy theory, legal literacy, and social analysis. Research institutions may develop data trusts, secure research enclaves, automated provenance systems, and interoperable governance metadata. The central challenge will be to support useful data integration without creating invisible systems of surveillance or exclusion. Future data management must therefore be technically robust, socially legitimate, environmentally responsible, and open to scrutiny by affected communities. 19. Chapter SummaryData management is a lifecycle discipline that connects research design, quality assurance, security, ethics, and governance. Reliable findings depend on defined concepts, suitable collection procedures, documented metadata, traceable provenance, controlled transformation, and appropriate storage. Researchers must distinguish errors from legitimate variation, analyse missingness rather than conceal it, and recognise that bias can enter through sampling, measurement, linkage, and processing. Privacy and governance require more than removing names. They involve purpose limitation, minimisation, consent, access control, retention, risk assessment, and accountability. FAIR and reproducible practices increase legitimate reuse, while the CIA triad supports confidentiality, integrity, and availability. Effective governance is proportionate and continuous: it protects participants and research integrity while enabling responsible collaboration and discovery. 20. Key Terms1. Access control: Rules determining who may use data and what actions they may perform. 2. Anonymisation: Processing intended to remove the possibility of identifying individuals. 3. Bias: Systematic distortion that makes data or findings unrepresentative of the intended phenomenon. 4. Data dictionary: A structured description of variables, meanings, formats, codes, and constraints. 5. Data governance: Policies, roles, standards, and controls for responsible data use. 6. Data lineage: The documented path through which data move and are transformed. 7. Data management: Planning, organising, protecting, processing, sharing, preserving, and disposing of data. 8. Data provenance: Evidence of a dataset’s origin, history, agents, and transformations. 9. Data quality: Fitness of data for a specified purpose. 10. De-identification: Removal or modification of identifying information to reduce disclosure risk. 11. FAIR principles: Findability, Accessibility, Interoperability, and Reusability principles for research resources. 12. Imputation: Estimation and replacement of missing values using a stated method. 13. Metadata: Information describing the content, structure, context, management, or use of data. 14. Missingness: The condition in which an expected data value is unavailable. 15. Pseudonymisation: Replacing identifiers with codes while retaining a possible re-identification route. 16. Research governance: Oversight structures ensuring lawful, ethical, secure, and accountable research. 17. Schema: The formal structure defining fields, relationships, types, and constraints in data. 18. Data stewardship: Ongoing responsibility for data quality, documentation, access, and appropriate use. 21. Review QuestionsShort Answer Questions1. What is the difference between a backup and an archive? 2. Define data provenance and explain why it supports reproducibility. 3. Identify four common dimensions of data quality. 4. Distinguish anonymisation from pseudonymisation. 5. What are the three elements of the CIA security triad? Long Answer Questions1. Explain how a doctoral researcher should design and implement a complete data-management lifecycle. 2. Discuss the causes and consequences of missing data and compare possible strategies for addressing them. 3. Explain how metadata and data dictionaries contribute to data quality and research reuse. 4. Evaluate the relationship between FAIR principles, open science, privacy, and controlled access. 5. Discuss how research governance should address ethical, legal, security, and reproducibility requirements simultaneously. Analytical / Application Questions1. A research team merges social-media posts with university records and discovers inconsistent identifiers and substantial demographic nonresponse. Design an assessment and remediation strategy, including quality, privacy, and bias considerations. 2. A machine-learning project reports excellent accuracy, but its training data include variables recorded only after the target outcome occurred. Analyse the governance and data-management failure and propose corrective actions. 3. Develop a proportionate data-management plan for a qualitative study involving sensitive interviews, including collection, transcription, access, de-identification, retention, publication, and disposal. 22. Multiple Choice Questions with AnswersQuestion 1Which practice best supports traceability from original records to a published research result? A. Replacing raw files with cleaned files B. Maintaining provenance records and version-controlled transformation scripts C. Allowing every team member unrestricted access D. Deleting intermediate datasets after analysis Correct Answer: B. Maintaining provenance records and version-controlled transformation scripts Question 2A dataset contains different date formats, duplicate records, and impossible values. What should researchers do first? A. Publish the data without changes B. Delete every record containing an error C. Profile the data and document quality problems before applying corrections D. Replace all unusual values with the mean Correct Answer: C. Profile the data and document quality problems before applying corrections Question 3Which statement best describes pseudonymisation? A. All identifying information is permanently impossible to recover B. Identifiers are replaced with codes, but re-identification may remain possible C. Data are made publicly available without restrictions D. Only inaccurate records are removed Correct Answer: B. Identifiers are replaced with codes, but re-identification may remain possible Question 4Under the FAIR principles, restricted-access data can still be considered accessible when they are: A. Available to everyone without authentication B. Stored only on a researcher’s personal computer C. Retrievable through an appropriate, documented access procedure D. Published without metadata Correct Answer: C. Retrievable through an appropriate, documented access procedure Question 5Which security measure primarily supports data availability? A. Tested and protected backups B. Removing all metadata C. Publishing passwords D. Changing variable names Correct Answer: A. Tested and protected backups Question 6Why is missingness not automatically evidence that records should be deleted? A. Missing values are always harmless B. The pattern of missingness may be related to observed or unobserved characteristics C. Deletion always increases sample size D. Missingness cannot affect conclusions Correct Answer: B. The pattern of missingness may be related to observed or unobserved characteristics Question 7What is the main purpose of a data dictionary? A. To encrypt every file in a project B. To describe variables, meanings, formats, codes, and constraints C. To replace ethical approval D. To determine authorship automatically Correct Answer: B. To describe variables, meanings, formats, codes, and constraints Question 8Which action best reflects the principle of least privilege? A. Giving all users administrator rights B. Providing each user only the access necessary for their role C. Allowing access without authentication D. Sharing raw data through public email Correct Answer: B. Providing each user only the access necessary for their role Question 9In the illustrative case, duplicate log events could lead to: A. Inflated measures of student engagement B. Guaranteed elimination of bias C. Improved confidentiality D. Automatic anonymisation Correct Answer: A. Inflated measures of student engagement Question 10Why is a data lake at risk of becoming a data swamp? A. It stores only relational tables B. It cannot store raw data C. Its varied contents become difficult to find, interpret, and govern without cataloguing D. It always deletes metadata Correct Answer: C. Its varied contents become difficult to find, interpret, and govern without cataloguing
|