Free IQ0-100 Practice Test Questions and Answers (2026)

Tacit knowledge refers to the skills, ideas, and experiences that are possessed by people but are not codified and may not necessarily be easily expressed. It is deeply rooted in an individual's actions and experience, as well as in the ideals, values, or emotions they embrace. This type of knowledge is often contrasted with explicit knowledge, which is formal and systematic. Tacit knowledge is "in people's heads" and is shared through conversation, storytelling, and shared experience.

A. Implicit: While related, "implicit knowledge" often refers to knowledge applied unconsciously. "Tacit" is the more standard and precise term in knowledge management for personal, uncodified knowledge.
C. Explicit: This is the opposite of tacit knowledge; it is knowledge that has been articulated, codified, and stored in media like documents or databases.
D. Extraneous: This term means irrelevant or unrelated and is not a category of knowledge in this context.

1. Nonaka, I. (1994). A Dynamic Theory of Organizational Knowledge Creation. Organization Science, 5(1), 14–37. In Section 3, "Two Dimensions of Knowledge Creation," Nonaka defines tacit knowledge as "personal, context-specific, and therefore hard to formalize and communicate." (p. 16). DOI: https://doi.org/10.1287/orsc.5.1.14

2. Polanyi, M. (1966). The Tacit Dimension. Doubleday & Company. The entire book is the foundational text for the concept, distinguishing between what we can articulate (explicit) and what "we can know more than we can tell" (tacit).

The most efficient strategy for yielding accurate search results in e-discovery for a litigation hold is to develop precise and well-reasoned search parameters. This includes negotiating keywords, defining date ranges, identifying custodians, and potentially using concept searching or other advanced analytics. This strategic step focuses the search effort, minimizes the collection of irrelevant data (false positives), and increases the likelihood of finding relevant information (true positives), thereby controlling costs and improving the accuracy and defensibility of the discovery process.

A. Identifying information in databases is a tactical task, not an overarching strategy for ensuring accuracy.
B. Retrieving information from off-site storage is a specific collection task, often inefficient, not a search strategy.
C. Evaluating email systems is part of defining the scope, not the strategy for executing an accurate search within that scope.

1. The Sedona Conference. (2017). The Sedona Principles, Third Edition: Best Practices, Recommendations & Principles for Addressing Electronic Document Production. Principle 6 states parties should be prepared to discuss search methodologies, which centers on developing parameters.

2. Electronic Discovery Reference Model (EDRM). The "Processing," "Review," and "Analysis" stages of the EDRM model rely on applying search parameters to cull data sets and identify relevant information efficiently. The development of these parameters is a key strategic activity. (See edrm.net for the model diagram and explanations).

3. Grossman, M. R., & Cormack, G. V. (2011). Technology-assisted review in e-discovery can be more effective and more efficient than manual review. Richmond Journal of Law & Technology, 17(3), 1-48. This academic paper demonstrates that the effectiveness of any search, manual or assisted, is highly dependent on the strategy and parameters used for the search.

Two primary challenges business leaders face in establishing an Information Workplace are poor information accessibility and a lack of governance. Firstly, when accurate and timely information is not readily available, it cripples an organization's ability to make quick, informed decisions (A). Secondly, this problem is often caused by the proliferation of multiple, disconnected data repositories that operate without a cohesive governance strategy (C). These information silos lead to data duplication, inconsistency, and an inability to find a single source of truth, directly undermining the goal of a unified and efficient Information Workplace.

B: The technology to integrate structured and unstructured information exists and is mature; the challenge is typically in its strategic implementation and cost, not its availability. D: Having an information management strategy and infrastructure in place is the solution or the desired goal, not a challenge.

1. Tallon, P. P., Ramirez, R. V., & Short, J. E. (2013). The Information Artifact in IT Governance: A Model of Antecedents and Performance Impacts. MIT Sloan Center for Information Systems Research, Working Paper No. 392. Page 4 discusses how information silos (related to C) and a lack of data availability (related to A) are key challenges addressed by information governance.

2. Al-Ruithe, M., Benkhelifa, E., & Hameed, K. (2018). Key Challenges in Information Governance. 2018 13th International Conference on Computer Engineering and Systems (ICCES). https://doi.org/10.1109/ICCES.2018.8639221. The paper identifies "Information Silos" and "Poor decision making" as significant challenges in information governance.

3. AIIM. (2020). State of the Intelligent Information Management Industry 2020: A Wake-up Call to Get Your Information House in Order. This industry report frequently cites the problems of "information chaos" and "multiple repositories" (C) as key barriers to digital transformation.

Metadata provides the contextual information necessary to understand a record's origin, structure, and history. This context is fundamental to establishing a record's authenticity, reliability, and integrity over time. By documenting attributes like creation date, author, and modification history, metadata serves as the foundation for a record's evidential value, proving it is what it purports to be and has not been tampered with.

A. Metadata applies to both physical and electronic records, not just electronic ones.
B. Metadata describes a record, which is then used to apply a retention schedule; it does not determine the value itself.
D. While good records management contributes to transparency, it is a broad organizational outcome, not a direct benefit of metadata.

1. International Organization for Standardization. (2016). ISO 15489-1:2016 Information and documentation — Records management — Part 1: Concepts and principles. Section 7.2, "Metadata for records," specifies that metadata is required to ensure the authenticity, reliability, integrity, and usability of records.

2. National Archives and Records Administration (NARA). (2020). Bulletin 2020-01: Guidance on Records Management for the Transition and Closing of a Presidential Administration. Section "Metadata," emphasizes that metadata provides context and structure, which are essential for managing records and ensuring their value.

3. Gilliland, A. J. (2016). Setting the Stage. In Introduction to Metadata (3rd ed.). Getty Research Institute. This university-level text explains that metadata supports evidence and authenticity by providing administrative, descriptive, and technical context. (Available via Getty Publications).

Folksonomy is the specific term used to describe the collaborative classification system that results from social tagging. In enterprise social media and other Web 2.0 platforms, users apply keywords (tags) to content. The aggregation of these user-generated tags creates a "folk taxonomy," or folksonomy. It is a bottom-up, user-driven approach to organizing information, reflecting the vocabulary and conceptual models of the users themselves rather than a predefined, formal structure.

A. Mashups are web applications that combine data or functionality from multiple sources into a single integrated tool.
C. Microblogging is a form of online communication where users share short text updates, images, or links.
D. Cloud computing is a model for delivering on-demand computing services over the internet, related to infrastructure, not tagging.

1. Guy, M., & Tonkin, E. (2006). Folksonomies: Tidying up tags?. D-Lib Magazine, 12(1). The article's abstract and introduction directly define folksonomies as the result of social tagging. Retrieved from http://www.dlib.org/dlib/january06/guy/01guy.html

2. Vander Wal, T. (2007, February 2). Folksonomy Coinage and Definition. This is the original definition from the term's creator, stating, "Folksonomy is the result of personal free tagging of information... for one's own retrieval."

3. Peters, I. (2009). Folksonomies: Indexing and retrieval in Web 2.0. Walter de Gruyter. Chapter 1 provides a detailed academic definition, linking the practice of social tagging directly to the concept of a folksonomy.

An organization is ultimately responsible for its records, regardless of their physical location. Therefore, it must contractually obligate any third-party vendor to manage and retain those records according to the organization's own retention policies and schedules. When litigation is anticipated, the organization has a duty to preserve relevant evidence. This duty extends to records held by third parties. The organization must issue a formal legal hold notice to the vendor, requiring them to suspend any destruction of the specified records and to acknowledge their compliance.

A. Allowing a vendor to use its own policy would lead to non-compliance with the organization's legal and regulatory obligations for its own records.
C. Records held by a third party are considered under the organization's "custody or control" and are fully discoverable in litigation; excluding them would be spoliation.

1. ARMA International. (2017). The Principles®: Generally Accepted Recordkeeping Principles. Principle of Protection, Page 11, states the program must ensure protection for records, a duty that extends contractually to third-party providers. Principle of Compliance, Page 9, requires the program to comply with the organization's own legal and regulatory requirements.

2. The Sedona Conference. (2010). The Sedona Conference® Commentary on Legal Holds: The Trigger & The Process. Public Comment Version. Page 11 discusses the scope of preservation, which includes documents in the "possession, custody, or control" of the organization, explicitly covering data held by third parties.

The primary purpose of a legal hold, also known as a litigation hold, is the preservation of information. When an organization reasonably anticipates litigation, a government investigation, or an audit, it has a legal duty to issue a hold. This directive overrides normal document retention and destruction schedules to ensure that all potentially relevant electronically stored information (ESI) and physical documents are protected from being altered, deleted, or otherwise destroyed. This preservation is the foundational step upon which all subsequent eDiscovery activities, such as collection and review, are built.

A. Distributing notification is the method for implementing a hold, but the ultimate purpose is the preservation itself.
B. Collecting and exporting information for review are subsequent steps in the eDiscovery process, which are only possible if the data has been preserved by the hold.
C. Collecting information based on keywords is part of the eDiscovery collection phase, not the primary purpose of the initial preservation hold.

1. The Sedona Conference. (2007). The Sedona Conference Commentary on Legal Holds: The Trigger & The Process. The commentary states, "The purpose of a legal hold is to preserve information for discovery and to prevent spoliation." (Page 1).

2. AIIM International. (2020). Automating Information Governance. White Paper. Section: "Managing Legal Holds and eDiscovery". This document emphasizes that a legal hold's function is to "suspend normal retention/disposition rules for information that may be relevant to a legal matter."

3. Federal Rules of Civil Procedure, Rule 37(e). "Failure to Preserve Electronically Stored Information." This rule outlines the sanctions for failing to take reasonable steps to preserve ESI, implicitly defining the purpose of such preservation efforts (i.e., a legal hold).

The primary technological challenge in implementing telecommuting is ensuring reliable, secure, and performant network connectivity. This includes provisioning secure VPNs, managing access controls, and addressing the variability of employees' home internet bandwidth and reliability. Without a stable and secure network foundation, other telecommuting tools and applications cannot function effectively, and corporate data is put at risk. All other technological aspects of remote work depend on resolving these core networking issues first.

A. Email is a mature, ubiquitous technology and is not a primary implementation challenge for telecommuting.
B. Privacy is a critical security and policy concern, but its technical implementation relies on the underlying network infrastructure being secure and functional.
D. Managing worker hours is a human resources or management challenge, not a direct technological implementation issue.

1. Stallings, W., & Brown, L. (2018). Computer Security: Principles and Practice (4th ed.). Pearson. (Chapter 21, "Network Security," details the complexities of securing remote access, including VPNs and wireless security, which are central to telecommuting).

2. Cornell University, Division of Information Technologies. (2023). Securely Work from Off-Campus or Other Remote Locations. Retrieved from https://it.cornell.edu/security-and-policy/securely-work-campus-or-other-remote-locations (This guide emphasizes the use of VPNs and secure network practices as foundational for remote work).

3. Wang, B., et al. (2021). Work from Home is Here to Stay: Call for Papers for a Special Issue of the Journal of Applied Psychology. Journal of Applied Psychology, 106(12), 1757–1762. https://doi.org/10.1037/apl0000987 (Discusses technological resources, including "reliable internet access," as a key factor for successful WFH implementation).

U.S. NARA and AIIM guidance recommend leveraging each platform’s native API/feeds for direct, metadata‐rich capture; where APIs are limited, predefined searches/RSS streams can be harvested and ingested into the records system, ensuring completeness, authenticity, and automation.

B. Manual screenshots/printing are labor-intensive, lose embedded metadata, and cannot scale for high-volume or dynamic content.
D. Bespoke capture tools duplicate API functionality, require continuous maintenance for every platform change, and are rarely cost-effective.

1. National Archives Bulletin 2014-02, “Guidance on Managing Social Media Records,” §3.b-3.d (pp. 5-6).

2. AIIM CIP Study Guide v3, Module 5 “Social Media Records,” p. 129-130.

3. University of Maryland iSchool, INFM 612 Lecture 10 slides, “Recordkeeping for Social Media,” slide 14.

Role-Based Access Control (RBAC) is the most effective solution. It standardizes access by assigning permissions based on a user's defined role within the project (e.g., "Project Lead," "Developer," "Auditor"), irrespective of their home organization. This approach ensures consistent privileges for all team members performing the same function, simplifying administration and enforcing the principle of least privilege across the distributed team. It directly addresses the problem of inconsistent procedures by creating a unified, role-centric policy.

A. A standard checklist helps standardize the process but does not fix the underlying problem of inconsistent privilege assignment logic.
B. Routing all requests to one administrator creates a significant bottleneck and is not a scalable or efficient solution for a collaborative project.
C. Controlling privileges based on the user's organization is the root cause of the problem, as it perpetuates the inconsistent access rules.

1. Ferraiolo, D. F., & Kuhn, D. R. (1992). Role-Based Access Control. In Proceedings of the 15th National Computer Security Conference (pp. 554-563). NIST/NCSC. This foundational paper establishes RBAC as a method to associate permissions with roles to manage access in large, complex organizations.

2. Sandhu, R. S., Coyne, E. J., Feinstein, H. L., & Youman, C. E. (1996). Role-based access control models. IEEE Computer, 29(2), 38-47. https://doi.org/10.1109/2.485845. (See Section II, "Motivation for RBAC," which discusses managing access in multi-user environments).

Write Once Read Many (WORM) is a data storage technology that allows information to be written to a storage medium a single time and prevents it from being erased or altered. This technology is specifically designed to ensure data immutability, which is the core requirement of the question. WORM-compliant storage is essential for organizations needing to meet strict regulatory, legal, or archival requirements for information integrity and authenticity over long periods.

A. Public key infrastructure: This is a security framework for encryption and identity verification, not for ensuring the unalterable state of stored information.
C. Private key infrastructure: This is a component of PKI and is related to security and authentication, not the physical or logical immutability of storage media.
D. Redacting annotation: Redaction involves removing or obscuring information from a document, which is an alteration, not a method of preservation.

1. University of North Carolina at Chapel Hill, School of Information and Library Science. (n.d.). Glossary of Archival and Records Terminology. "WORM (Write-Once-Read-Many)". Defines WORM as a type of storage medium to which data can be written only once but read an unlimited number of times.

2. Hedstrom, M. (2002). Research Challenges in Digital Archiving and Long-term Preservation. "Technology for Digital Preservation". Cornell University Library, RLG DigiNews. Discusses WORM as a technological strategy for ensuring the fixity and integrity of digital objects over time. Section 2.2.

3. AIIM International. (2019). AIIM Certified Information Professional (CIP) Study Guide. Chapter 5: "Preserving and Disposing". Discusses technologies for long-term preservation, including WORM storage as a key method for ensuring record immutability.

The goal of an enterprise portal for a globally dispersed staff is to create a single, unified "digital workplace." The most effective approach is to provide a single point of access to all necessary resources. Integrating data, content, information, knowledge, and applications into one portal breaks down information silos, streamlines workflows, and enhances collaboration and efficiency. Separating these components would defeat the primary purpose of creating a cohesive and efficient collaborative environment.

B. Separating records, data, and applications creates silos, forcing users to navigate multiple systems and hindering a unified collaborative experience.
C. Focusing only on analytic dashboards is too narrow; it ignores the broader need for document access, collaboration tools, and transactional applications.
D. Creating a separate secure portal for data and applications re-introduces the very fragmentation and inefficiency that a unified portal aims to solve.

1. Detlor, B. (2010). Information management. International Journal of Information Management, 30(2), 103-108. https://doi.org/10.1016/j.ijinfomgt.2009.12.001. This paper discusses the evolution of portals towards integrated "information workplaces" that combine information, applications, and collaboration.

2. Benbya, H., Passiante, G., & Belbaly, N. A. (2004). Corporate portal: a tool for knowledge management synchronization. International Journal of Information Management, 24(3), 201-220. https://doi.org/10.1016/j.ijinfomgt.2003.12.012. The article emphasizes the portal's role in integrating disparate information sources and applications to support knowledge work.

3. Laudon, K. C., & Laudon, J. P. (2018). Management Information Systems: Managing the Digital Firm (15th ed.). Pearson. Chapter 11, "Managing Knowledge and Artificial Intelligence," describes enterprise portals as providing a single point of access to information and applications.

The problem describes user confusion with a new website's structure, layout, and visual cues, leading to a high bounce rate. Usability testing is the most direct method to diagnose these types of issues. It involves observing representative users as they attempt to perform tasks on the site. This qualitative approach provides deep insights into why users are struggling, revealing specific problems with navigation, information architecture, and overall user experience that quantitative methods like A/B testing cannot explain.

A. A/B testing: This method compares two versions of a single element to see which performs better, which is not suitable for diagnosing foundational structural confusion.
B. Multivariate testing: This tests multiple combinations of page elements simultaneously to optimize a design, but it doesn't explain the root cause of user confusion.
D. Conversion testing: This measures the rate at which users complete goals. While related to the problem, it identifies the outcome (low conversion) but not the cause.

1. Nielsen, J. (1994). Usability Engineering. Morgan Kaufmann. Chapter 1, "What is Usability," and Chapter 6, "Usability Testing," establish the principles of observing users to find design flaws.

2. MIT OpenCourseWare. (2011). 6.813/6.831 User Interface Design and Implementation, Lecture 5: Usability Testing. Massachusetts Institute of Technology. The lecture notes detail usability testing as the primary method for "finding usability problems in a user interface."

3. Lazar, J., Feng, J. H., & Hochheiser, H. (2017). Research Methods in Human-Computer Interaction (2nd ed.). Morgan Kaufmann. Chapter 7, "Usability Testing," describes the process as a key method for evaluating how well people can use an information system.

Digital Rights Management (DRM) provides persistent protection for content by embedding usage rights and restrictions directly into the files themselves. The primary benefit of this approach is that these rules travel with the content wherever it goes. This allows an organization to extend its governance and compliance policies (e.g., preventing printing, copying, or forwarding) to information even after it has left the secure, managed corporate environment, such as when it is sent to a partner or downloaded to a personal device.

A. While DRM uses encryption, its main benefit is policy enforcement, not just managing the encryption platform itself.
C. DRM is a preventative control to stop misuse, whereas identifying misuse that has already occurred is typically the function of auditing or Data Loss Prevention (DLP) systems.
D. This describes the types of content DRM can support (its features), not the core organizational benefit it provides.

1. AIIM International. (2010). Information Governance: The Art & Science of Managing Information in the Digital Age. AIIM White Paper. This document discusses how technologies like DRM are used to enforce information policies persistently across and beyond the enterprise. (Section: "Enforcing policies").

2. Subramanya, S. R., & Yi, B. K. (2006). "Digital Rights Management". IEEE Potentials, 25(2), 31-34. https://doi.org/10.1109/MP.2006.1649002. The paper describes DRM as a technology to control the use of digital content after sale or distribution. (Section: "DRM Architecture").

The core problem described is a lack of version control, a common issue with unstructured storage like shared drives. A document management solution (DMS) is the most appropriate and comprehensive technology to resolve this. A DMS provides automated versioning, check-in/check-out capabilities, audit trails, and a centralized, controlled environment. This systematically eliminates confusion over which version is the most recent and ensures a single source of truth for information.

B. Naming conventions are a manual process, prone to human error, and do not provide the robust control or audit features of a dedicated system.
C. Using spreadsheets to track versions is another manual, inefficient, and error-prone workaround, not a scalable solution.
D. A records management program governs the lifecycle of official records for compliance, which is different from managing versions of active, in-process documents.

1. MIT Libraries. (n.d.). Data Management and Publishing: Version Control. Retrieved from https://libguides.mit.edu/data-management/version-control (This guide explains the limitations of manual versioning and recommends using dedicated systems for robust control).

2. University of Edinburgh, Information Services. (n.d.). Research Data Management: Organising your data. Retrieved from https://www.ed.ac.uk/information-services/research-support/research-data-service/after/organising-your-data (Section on "File version control" highlights the need for systematic approaches beyond manual naming).

Transactional Content Management (TCM) is a subset of ECM focused on automating high-volume, repetitive, process-centric activities. A core activity is document imaging (A), which involves capturing and digitizing paper documents (e.g., invoices, applications) to initiate a digital workflow. Because these transactions often represent official business activities, robust records management (C) is essential to ensure the resulting digital documents are managed, retained, and disposed of in compliance with legal and regulatory requirements.

B. Document collaboration is the primary focus of collaborative content management systems, which handle unstructured, ad-hoc processes, not high-volume transactions.
D. Content analytics is a broader capability that can be applied to any content repository; it is not a defining, core activity of TCM itself.

1. Vom Brocke, J., & Rosemann, M. (Eds.). (2010). Handbook on Business Process Management 1: Introduction, Methods, and Information Systems. Springer. Page 427 discusses Transactional Content Management as focusing on process-oriented applications like invoice processing, which inherently involves imaging and records management.

2. O'Callaghan, A., & Smits, M. (2005). A Strategy for Aligning Business Goals and Enterprise Systems. In Encyclopedia of Information Science and Technology, First Edition (pp. 2680-2686). IGI Global. The text differentiates transactional systems (focused on process automation) from collaborative systems.

3. AIIM International. (2010). What is Enterprise Content Management (ECM)?. AIIM White Paper. While a trade organization, AIIM's foundational definitions are widely cited in academic literature. Early versions of their models clearly define TCM as linking content to business transactions, with imaging and records management as key components. (Archived versions are often referenced in university curricula).

Mobile websites are developed using standard web technologies and are accessed via a browser, making them universally compatible across different mobile devices. Native applications, however, are built using platform-specific languages (e.g., Swift for iOS, Kotlin for Android) and must be downloaded. This platform-specific design allows native apps to directly access device hardware (GPS, camera, etc.) and integrate seamlessly with the operating system, which typically results in a superior, faster, and more feature-rich user experience compared to the limitations of a web browser.

A. This is reversed. Native applications require certification and distribution through app stores, while mobile websites do not.
B. This is generally false. Native apps often load faster after installation as many assets are stored locally, reducing network latency for subsequent use.

Kim, M., & Lee, S. (2015). "A Study on the User Experience of Mobile Application: Native App vs. Web App." International Journal of Multimedia and Ubiquitous Engineering, 10(1), 267-276. https://doi.org/10.14257/ijmue.2015.10.1.26 (This academic paper compares user experience and platform dependency).

Stanford University, CS 193p - "Developing Apps for iOS," Course materials, Lecture 1 "Course Overview," distinguishes native app development from web development, highlighting platform specificity and user experience advantages.

"Telecommuting support" refers to the comprehensive framework an organization establishes to enable employees to work effectively from locations other than a central office. This is not just about a single technology but encompasses providing the necessary tools (e.g., laptops, secure network access, collaboration software), policies (e.g., communication protocols, security requirements), and organizational conditions (e.g., management trust, performance metrics) that allow for flexible work locations and hours while maintaining productivity and security.

A. This describes a single communication task that might be part of telecommuting, not the overall support structure for it.
B. This describes a specific activity (research) that can be done remotely but does not define the broad support system.
D. This describes work-related travel or a "digital nomad" lifestyle, which is a form of remote work but not the definition of the organizational support itself.

1. Pérez, M. P., Sánchez, A. M., & de Luis Carnicer, P. (2002). Benefits and barriers of telework: perception differences of human resources managers according to company's size. Journal of Enterprise Information Management, 15(4), 276-288. The paper defines telework support as involving technology, organizational adaptation, and human resource policies. DOI: https://doi.org/10.1108/17410390210436828

2. Baruch, Y. (2001). The status of research on teleworking and an agenda for future research. International Journal of Management Reviews, 3(2), 113-129. Section 2, "Defining Teleworking," discusses it as a flexible work arrangement supported by technology and organizational policy. DOI: https://doi.org/10.1111/1468-2370.00058

Functional requirements specify what the system should do—its behaviors, features, and functions. They define the specific actions the system must be able to perform. Non-functional requirements, in contrast, describe the qualities or constraints of the system, defining how the system should perform its functions. These are often called "quality attributes" and include aspects like performance, security, reliability, and usability. This distinction is a foundational concept in systems engineering and software development.

B. This option incorrectly reverses the definitions of functional and non-functional requirements.
C. This option incorrectly defines non-functional requirements as de-prioritized items, which relates to project management backlog grooming, not requirements classification.
D. This option uses vague terms; both requirement types are essential to defining the overall solution and its implementation.

1. Glinz, M. (2007). On Non-Functional Requirements. 15th IEEE International Requirements Engineering Conference (RE'07), pp. 21-26. DOI: 10.1109/RE.2007.56. (Section II.A defines functional requirements as "what the system should do" and non-functional requirements as "constraints on the system or its properties").

2. University of Texas at Austin, Department of Computer Science. (n.d.). CS 373: Software Engineering, Lecture 5: Requirements. Retrieved from https://www.cs.utexas.edu/~downing/cs373/lectures/05requirements.pdf (Slide 11 distinguishes "Functional: what the system does" from "Non-functional: constraints on the system").

A wiki is the most effective tool for this scenario. It is specifically designed for collaborative content creation and management. The committee can create separate pages for each meeting's agenda, minutes, and associated reports. Wikis inherently support version control, allowing members to track changes and revert if necessary. All related documents are stored in a central, accessible location, unlike email where versions become scattered across inboxes. The structure of a wiki allows for easy linking between related documents, creating an organized and persistent knowledge base for the committee's work.

A. A blog is a chronological publication tool, not well-suited for the collaborative editing and structured organization of official documents.
B. Email is inefficient for collaboration, leading to version control problems and difficulty in finding the final, authoritative document.
D. Microblogging is for short, informal updates and is entirely unsuitable for drafting and publishing formal documents like minutes and reports.

1. Augar, N., Raitman, R., & Zhou, W. (2004). Teaching and learning online with wikis. In R. Atkinson, C. McBeath, D. Jonas-Dwyer & R. Phillips (Eds.), Beyond the comfort zone: Proceedings of the 21st ASCILITE Conference (pp. 95-104). This paper discusses the use of wikis as a tool for collaborative knowledge construction.

2. MIT OpenCourseWare. (n.d.). 21W.789 Communicating in Technical Organizations, Course Notes. "Collaboration Tools" section compares various tools, highlighting wikis for their strength in co-authoring and maintaining a shared knowledge repository.

3. Leuf, B., & Cunningham, W. (2001). The Wiki Way: Quick Collaboration on the Web. Addison-Wesley Professional. The foundational text explains the core principles of a wiki as a platform for collaborative writing and knowledge management.