Full Access WGU Information-Technology-Management Tutorials

Comprehensive and Detailed Explanation From Exact Extract:

In IT and UX design, a wireframe is a low-fidelity, structural blueprint of a screen, page, or interface. Its key characteristics are:

It shows the basic layout: placement of menus, buttons, content areas, images, forms, and navigation elements.

It does not focus on visual styling: usually no colors, branding, fonts, or detailed graphics.

It generally has no interactivity: it represents what goes where, not how the system behaves in detail.

Wireframes are used to:

Clarify information hierarchy and navigation flow.

Align stakeholders on the structure of the solution before investing in visual design or development.

Serve as a bridge between requirements and higher-fidelity mockups or prototypes.

This is exactly described by “a basic layout without visual design or interactivity,” which matches Option C.

Why the other options are incorrect:

A. A diagram of system data flow without functionalityThat describes a data flow diagram (DFD), not a wireframe. DFDs focus on data movement, not page layout.

B. A polished design with visual design and interactivityThat describes a high-fidelity mockup or interactive prototype, not a wireframe.

D. A detailed coded interface for backend testingThat refers to an implemented UI or test harness, which goes far beyond the purpose and fidelity of wireframes.

Comprehensive and Detailed Explanation From Exact Extract:

In cybersecurity, data integrity means that data has not been altered, tampered with, or corrupted during storage or transmission. Hashing is the primary method used to help ensure integrity. A hash function takes an input (such as a file or message) and produces a fixed-size hash value or message digest. If the data changes in any way, even slightly, the resulting hash value will also change, revealing that the data was modified.

Why D is correct: Hashing supports verification that data remains unchanged during transmission by comparing the hash calculated at the source with the hash calculated at the destination. Matching values indicate the data has not been altered.

Why the others are incorrect:

A. Encryption – Encryption protects confidentiality by making data unreadable to unauthorized parties, but by itself it does not prove that the data wasn’t modified.

B. Access control lists (ACLs) – ACLs regulate who can access what, but they do not verify whether data was changed during transmission.

C. Authentication – Authentication verifies who is accessing a system or resource (identity), not whether the data content remained intact in transit.

Understanding Reporting in CRM:

The reporting phase of CRM involves extracting data to generate summaries and insights.

Reports help in understanding customer activities, such as identifying top customers based on spending.

Application in the Scenario:

The manager requests a report listing the top five customers by total spending, a classic example of CRM reporting.

Why Other Options Are Incorrect:

Option A (Distributing): Distributing is not a CRM phase.

Option B (Analyzing): Analyzing involves identifying trends or patterns, not generating a simple report.

Option C (Predicting): Predicting is forward-looking and does not match the scenario of reviewing past data.

Definition of the Accountability vs. Ownership Paradox:

This paradox arises when a CIO is held accountable for the results of technology initiatives but lacks authority over critical business processes or decisions that impact those results.

It reflects a misalignment between responsibility and control.

Impact on Organizations:

Leads to inefficiencies and miscommunications between IT and other business units.

Creates barriers to achieving organizational goals due to lack of cohesive decision-making authority.

Incorrect Options Analysis:

A: This describes strategic planning, not the paradox.

B: Relates to organizational change, but does not capture the accountability dilemma.

D: Refers to concerns about competitive disruption, unrelated to the paradox.

References and Documents of Information Technology Management:

"CIO Accountability Frameworks" (Forrester Research).

ITIL Governance Practices: Bridging Accountability Gaps (Axelos).