UGC NET Questions (Paper – 1)

Wiki-based environments provide simple editing interfaces so that multiple users can add, modify and link content pages. The revision history ensures transparency and allows rollback of problematic edits. This collaborative model supports collective knowledge construction and continuous updating of information. Thus sites such as Wikipedia exemplify wiki-based collaborative environments.

Option A:
Option A, static publishing, implies content managed only by a few administrators and rarely updated, which contrasts with the dynamic, user-edited nature of wikis.

Option B:
Option B, one way broadcasting, suggests information flowing from a single source to many receivers without their participation in content creation. Wikis are intentionally designed to be many-to-many rather than one-to-many.

Option C:
Option C, closed proprietary, would restrict editing rights and code access, whereas many wikis encourage broad participation and often rely on open technologies.

Option D:
Option D is correct because wikis are defined precisely as web systems enabling collaborative editing of linked pages, and the description in the stem fits this definition.

Wikis are web-based tools that allow multiple users to collaboratively edit content through a browser. Version history keeps track of changes made by different contributors and allows earlier versions to be restored. In education, wikis support group projects, glossaries and peer review activities. The scenario of co-authoring and tracking a group report clearly matches these features.

Option A:
A private paper diary involves only one author and no collaborative editing. It is not mediated by ICT and does not reflect wiki usage.

Option B:
A computer used purely as a calculator does not exploit web-based collaborative functions. It represents a very limited use of ICT.

Option C:
A printed notice is static and cannot be edited interactively by multiple users. It lacks the dynamic and networked nature of a wiki.

Option D:
This option correctly highlights shared authoring, online access and version tracking, which are key characteristics of wikis used for educational collaboration.

Statements A, B, C, E and F describe core features and practices of educational wikis, whereas D is false. Wikis enable collaborative editing with tracked versions and support project documentation and shared understanding. Guidelines and discussion pages further help maintain quality and resolve disagreements. The claim that instructors can never moderate or revert content is incorrect, so D must be omitted.

Option A:
Option A is incorrect because it omits F and therefore ignores the role of discussion pages in supporting collaboration. While A, B, C and E are correct, leaving out F removes an important communicative feature of many wiki platforms. This makes the option incomplete.

Option B:
Option B is correct because it brings together all the true statements and excludes D. It highlights collaborative editing, version control, group knowledge-building, guidelines and discussion channels as key aspects of educational wikis. Thus it best matches the full set of correct statements.

Option C:
Option C is incorrect because it omits A, which clearly identifies wikis as shared editable spaces. Without A, the collaborative nature of wikis is not fully captured. Even though B, C, E and F are true, leaving out A makes the combination incomplete.

Option D:
Option D is incorrect because it excludes B and so fails to acknowledge revision history as a core feature. While A, C, E and F are true, tracking of versions is also essential, and its omission means the set is not fully correct.

Statements A, B, D and E accurately describe common features of collaborative document tools, while C and F are incorrect. Revision history and comments support transparent, iterative improvement, but do not guarantee error-free output. Offline sync broadens access, and flexible permissions control how participants interact with a document. Therefore, the combination A, B, D and E only is correct.

Option A:
Option A is incomplete because it leaves out E, thereby failing to acknowledge offline editing and later synchronisation—an important feature for users with intermittent connectivity.

Option B:
Option B is incomplete because it omits A, so it does not mention revision history and accountability for changes, which are central advantages of collaborative editing.

Option C:
Option C is correct because it groups all the true statements and excludes C’s claim about guaranteed perfection and F’s denial of integrations. It recognises collaborative tools as powerful yet still requiring human review.

Option D:
Option D is incorrect because it accepts F, which states that shared documents can never integrate with LMS or other systems. In practice, many platforms allow embedding or linking collaborative documents within course spaces.

The track changes feature records each modification to a document, marking insertions, deletions and formatting changes so they can be reviewed later. It supports collaborative editing between authors and reviewers. This is especially useful in academic and administrative settings. Thus, the described feature is track changes.

Option A:
Option A is correct because track changes is the recognised name in word processors for visualising and managing edits.

Option B:
Option B, mail merge, creates multiple personalised copies and does not highlight revisions.

Option C:
Option C, auto correct, automatically fixes common typing errors but does not display explicit edit histories.

Option D:
Option D, thesaurus, suggests synonyms and is unrelated to tracking document edits.