Free WGU Information Technology Management QGC2 Information-Technology-Management Exam Questions

Understanding DevOps:

DevOps is an approach to software development and IT infrastructure that emphasizes collaboration between development and operations teams.

The key goal is to automate processes, streamline workflows, and deploy high-quality code faster.

Key Features of DevOps:

Continuous integration and continuous delivery (CI/CD) to automate code testing and deployment.

Emphasis on collaboration and automation to minimize manual interventions and reduce errors.

Why Other Options Are Incorrect:

Option A (Theory of reciprocity): Not relevant to IT development or infrastructure.

Option C (Business architecture): Focuses on organizational structure and strategy, not code automation.

Option D (Bimodal IT): Balances traditional IT with agile IT but does not focus explicitly on automation or quality code delivery.

:

'DevOps Principles and Practices' -- DevOps Institute

'Automating Development with DevOps' -- AWS Documentation

Green computing practices aim to reduce environmental impact by lowering energy use, minimizing e-waste, and extending hardware life cycles. One of the most effective practices is to extend device life through reuse and refurbishment. This prevents premature disposal, reduces demand for new hardware manufacturing, and lowers overall environmental impact.

Option B: Incorrect---prioritizing high performance can increase energy consumption and is not necessarily sustainable.

Option C: Incorrect---economical hardware does not always mean environmentally sustainable.

Option D: Incorrect---recycling is important, but refurbishment and reuse extend usable life and reduce waste earlier.

Thus, the IT practice that best supports green computing is extending device life with reuse and refurbishment.

WGU Information Technology Management -- IT Sustainability and Green Computing, section on Extending Equipment Life.

In Scrum, the product owner is responsible for maximizing the value of the product by managing the product backlog. This includes prioritizing requirements, refining backlog items, and ensuring that the development team works on the most valuable features first.

Option A: Velocity metrics are typically monitored by the Scrum Master and team, not the product owner.

Option B: Burndown charts are updated by the team, not managed by the product owner.

Option D: Assisting developers with coding and blockers is the responsibility of the Scrum Master and development team.

Thus, the product owner's main responsibility is to prioritize requirements and manage the backlog.

WGU Information Technology Management -- Agile and Scrum Practices, section on Scrum Roles: Product Owner.

Role of a Trusted Third Party:

Trusted third parties, like Certificate Authorities (CAs), validate the correlation between users and public keys.

They ensure secure communication by providing authentication (verifying user identity) and authorization (granting access rights).

Advantages in Disaster Recovery Planning:

Simplifies secure communication during recovery processes.

Provides a trusted mechanism for verifying identities and preventing unauthorized access.

Why Other Options Are Incorrect:

Option A (Monitors enclosures): Not related to public key verification.

Option B (Protects against encrypted attacks): While encryption enhances security, it is not the purpose of a trusted third party.

Option D (Features full-time monitoring): Not a function of trusted third parties like CAs.

:

Public Key Infrastructure (PKI) Best Practices -- NIST SP 800-32

Role of Trusted Third Parties in Disaster Recovery -- Gartner Research

Understanding the Development Phase in SDLC:

The development phase involves translating system design specifications into actual software.

This includes coding the system using programming languages and integrating modules as per the design.

Why Other Options Are Incorrect:

Option B: Describes the maintenance phase, which focuses on updates and corrections post-deployment.

Option C: Relates to the testing phase, where interoperability and functionality are verified.

Option D: Refers to the implementation phase, where the system is deployed for user operations.

:

SDLC Phases Explained -- NIST SP 800-64

'Software Development Life Cycle Best Practices' -- IEEE

Comprehensive and Detailed Explanation From Exact Extract:

In risk management, risks are evaluated based on probability (likelihood) and impact (consequence). Items that are high-risk and high-impact represent the most critical threats to project success and must be addressed proactively.

The appropriate response for high-risk, high-impact items is to create mitigation plans to address them, which includes:

Identifying specific actions to reduce the likelihood or impact of the risk.

Assigning owners responsible for executing mitigation actions.

Establishing timelines and triggers for when actions must be taken.

Monitoring these risks regularly in risk reviews and status meetings.

Why the other options are incorrect:

A . Develop a plan to revisit them in future phases -- Waiting to revisit critical risks delays action and increases the chance that they will negatively affect the project.

B . Draft a summary of risks for status reports -- Reporting alone does not reduce risk; it must be paired with concrete mitigation actions.

C . Track them without taking immediate action -- Simply tracking high-risk, high-impact items without acting is not acceptable risk management.

Therefore, high-risk, high-impact items should be handled by creating mitigation plans to address them, making D the correct answer.

Collaborative systems facilitate teamwork by providing tools for file sharing, communication, and project management. Examples include Microsoft Teams, Slack, and Google Workspace. These systems enhance productivity by enabling real-time collaboration, document sharing, and task management.

:

Laudon, K. C., & Laudon, J. P. (2020). Management Information Systems: Managing the Digital Firm. Pearson.

The Rational Unified Process (RUP) is an iterative software development framework with four phases: Inception, Elaboration, Construction, and Transition. The Elaboration phase comes after Inception and is focused on analyzing requirements, validating the system architecture, and addressing major risks before full-scale development begins.

Option B (Transition): Final phase, focused on deploying the system to end users.

Option C (Construction): Development and coding of the system, after architecture is validated.

Option D (Inception): Early phase, focused on business case and scope definition.

Thus, the correct phase before validating the system architecture is Elaboration.

WGU Information Technology Management -- Systems Development Methodologies, section on Rational Unified Process (RUP) Phases.23

An Online Transaction Processing (OLTP) system supports real-time processing of sales and inventory data. In retail, OLTP systems update information immediately as transactions occur, enabling front-line employees to make accurate, real-time decisions on sales, stock, and customer service.

Option B: Decision support systems (DSS) help managers with complex analysis, not real-time retail decisions.

Option C: Management information systems (MIS) provide summaries and reports, not live updates.

Option D: CRM systems manage customer relationships, not transaction-level sales and inventory.

Thus, the system is Online Transaction Processing (OLTP).

WGU Information Technology Management -- Information Systems, section on OLTP Systems.

Definition of ERP Systems:

ERP integrates core business processes across various departments, such as finance, HR, procurement, and production.

It creates a centralized communication platform for cross-departmental collaboration and seamless data sharing.

Purpose of ERP:

Ensures real-time data visibility across the organization.

Promotes collaboration by eliminating data silos and enabling efficient workflows.

Incorrect Options Analysis:

B . Supply Chain Management (SCM): Focuses on logistics and supply chain optimization, not general collaboration.

C . Customer Relationship Management (CRM): Concentrates on customer interactions.

D . Electronic Data Interchange (EDI): Facilitates data sharing with external partners, not internal collaboration.

and Documents of Information Technology Management:

'ERP Integration Best Practices' (Gartner).

ITIL Service Design: ERP Modules Overview (Axelos).

Simulation is a prototyping method that replicates how a system or solution would function in real-world scenarios. It allows businesses to test various data inputs, business rules, and operational conditions before full implementation. This method helps identify potential issues and optimize decision-making.

:

Banks, J., Carson, J. S., Nelson, B. L., & Nicol, D. M. (2010). Discrete-Event System Simulation. Prentice Hall.

Pidd, M. (2004). Computer Simulation in Management Science. John Wiley & Sons.

Comprehensive and Detailed Explanation From Exact Extract:

In the system development life cycle (SDLC), implementation planning focuses on how the completed system will be introduced into the live environment. This planning includes organizing and scheduling the system's rollout, determining when and how different components will go live, identifying the sequence of deployment tasks, defining cutover strategies (such as phased, pilot, or full implementation), and coordinating responsibilities across technical and business teams.

The objective is to ensure a smooth transition from development to production, minimizing disruption to daily operations and ensuring that all resources, dependencies, and timelines are clearly understood and managed.

Option A (Summarizing user experiences after deployment) is part of post-implementation review or evaluation, not implementation planning.

Option B (Defining and evaluating coding standards) belongs to design or development standards, not rollout planning.

Option C (Reviewing individual software components) is associated with unit or component testing, not rollout scheduling.

Therefore, implementation planning in the SDLC is best described as organizing and scheduling the system's rollout.

Understanding Unified Communications Systems:

Unified Communications (UC) integrates multiple communication tools like voice, video, messaging, and collaboration tools into a single platform.

Its goal is to enhance real-time communication and collaboration within and outside the organization.

Reducing Latency:

UC reduces delays (latency) in communication by enabling instant messaging, video conferencing, and real-time collaboration tools.

This ensures faster decision-making and improves organizational efficiency.

Why Other Options Are Incorrect:

Option A: Managing customer expectations is more aligned with CRM systems.

Option C: Generating solutions involves creativity and innovation tools, not UC.

Option D: While UC improves efficiency, it does not specifically aim to make employees 'comfortable.'

:

'Unified Communications: Transforming Organizational Communication' -- Gartner

IT Communication Frameworks and UC Standards

Understanding Anti-Spam Policies:

Anti-spam policies prohibit the sending of unsolicited emails, particularly outside the organization.

Such policies protect an organization's reputation and comply with legal frameworks like the CAN-SPAM Act.

Focus on External Communications:

The policy ensures employees refrain from sending emails that may be perceived as spam, safeguarding the organization from legal and reputational risks.

Why Other Options Are Incorrect:

Option A: Information use policies focus on managing and protecting data, not email practices.

Option B: Monitoring policies are about observing employee activity but do not prevent spam.

Option D: Social media policies govern employee behavior on social platforms, not email usage.

:

'Anti-Spam Guidelines for Businesses' -- FTC

IT Policy Frameworks and Guidelines (ISO 27002)

Benefits of In-House Development and Maintenance:

In-house teams gain deep knowledge of the organization's business processes, enabling better alignment between IT systems and business needs.

Combines technical expertise with business insights, resulting in a workforce that understands the company's unique challenges and opportunities.

Why Other Options are Incorrect:

A . Financial savings: In-house development often incurs higher costs due to salaries, training, and infrastructure.

B . Utilizing state-of-the-art resources: This is typically a benefit of outsourcing, not in-house development.

D . Fastest development time: In-house development is often slower compared to outsourcing due to limited resources.

and Documents of Information Technology Management:

'In-House vs. Outsourced Development: A Comparative Analysis' (Forrester).

ITIL Service Design and Workforce Development (Axelos).