Free WGU Information-Technology-Management Practice Exam with Questions & Answers | Set: 6

A Disaster Recovery Plan (DRP) outlines the procedures, technologies, and resources needed to restore systems, data, and operations following a disruption. This includes backups, redundant systems, alternate facilities, and recovery strategies to ensure operational continuity.

Option A: Risk management identifies and prioritizes risks, but DR handles recovery actions.

Option B: Infrastructure upgrades improve systems but are not focused on continuity.

Option C: Compliance plans ensure adherence to regulations, not recovery.

Thus, the correct plan for backups and redundancy is the Disaster recovery plan.

Comprehensive and Detailed Explanation From Exact Extract:

A key benefit of manufacturing ERP systems is improved coordination of materials used in production. ERP integrates purchasing, inventory management, and production planning so that materials and components are:

Ordered at the right time

Delivered in the right quantities

Available at the correct locations for manufacturing activities

This integration reduces stockouts, excess inventory, and delays caused by missing parts, thereby making production more efficient and reliable. Improved material coordination supports smoother workflows on the production floor and better alignment between demand and supply.

Option A (Customized machine software) refers to specialized software for specific machines or equipment, which is not the primary benefit of a manufacturing ERP system.

Option B (Streamlined hiring processes) is a human resources function and would be associated with HR systems, not specifically manufacturing ERP.

Option C (Enhanced supplier marketing) relates more to marketing and promotion to suppliers, which is not a central benefit of manufacturing ERP.

Thus, the primary benefit listed that aligns with manufacturing ERP is improved material coordination.

In the Transition phase of the Rational Unified Process (RUP), the system is deployed into the production environment, and ownership of the system is formally transferred to stakeholders. This phase involves user training, fine-tuning, and final acceptance, ensuring that the business takes responsibility for the system.

Option B (Inception): Defines the project scope and business case.

Option C (Elaboration): Focuses on refining requirements and validating architecture.

Option D (Construction): Involves building and coding the system.

Thus, system ownership is assigned to stakeholders in the Transition phase.

Comprehensive and Detailed Explanation From Exact Extract:

Operational decision-making focuses on short-term, day-to-day activities that keep the organization running efficiently. These decisions are typically structured, routine, and concern the execution of existing processes, such as staffing, work assignments, and scheduling.

Managing schedules and daily workflows is a classic operational-level activity because it involves:

Assigning tasks to staff for the current or upcoming shifts

Adjusting workflows to handle daily workload changes

Ensuring that routine operations proceed according to plan

Option B (Evaluating investment opportunities) is associated with tactical or strategic financial decisions, not daily operations.

Option C (Designing corporate policies) is part of tactical or strategic governance, focused on rules and guidelines that shape behavior across the organization.

Option D (Setting long-term strategic goals and objectives) clearly reflects strategic decision-making, focusing on the direction of the organization over years.

Therefore, managing schedules and daily workflows is the correct example of operational decision-making.

Understanding Virtualization:

Virtualization is the process of creating virtual versions of physical resources, such as servers, storage, or networks, to maximize their utilization.

Cost Reduction and Simplified Management:

Virtualization reduces hardware costs by allowing multiple virtual machines to run on a single physical server.

It simplifies IT management by enabling easier resource allocation, scaling, and disaster recovery.

Why Other Options Are Incorrect:

Option A: Virtualization increases resource availability, not restricts it.

Option C: Virtualization enhances workload distribution, reducing stagnation.

Option D: It reduces reliance on manual operations by enabling automation and centralized control.

Comprehensive and Detailed Explanation From Exact Extract:

Internet Protocol (IP) telephony, often called Voice over IP (VoIP), transmits voice (and often video) over data networks using the Internet Protocol. Within unified communications, a key benefit of IP telephony is that it enables voice and video communication to be integrated over the same IP-based infrastructure used for data.

Benefits in the UC context include:

Integration of voice and video services on the same network.

Easier integration with other UC components such as presence, conferencing, and collaboration tools.

More flexible and scalable communication services compared to traditional circuit-switched phone systems.

Why the other options are incorrect:

B. It has superior sound quality for all users – Sound quality depends on network conditions, bandwidth, codecs, and configuration; IP telephony can be high quality, but it is not guaranteed superior for all users.

C. It is compatible with chat and email – While IP telephony can be integrated into a broader UC platform that also supports chat and email, this is an indirect benefit of the overall UC system rather than the core defining benefit of IP telephony itself.

D. It uses physical phone lines – This is incorrect. IP telephony replaces or reduces reliance on traditional physical phone lines by using IP networks instead.

Therefore, the most accurate benefit described in the options is that IP telephony integrates voice and video over IP networks as part of a unified communications environment.

Sales tracking is a core feature of CRM systems that allows sales representatives to monitor leads, opportunities, and deals through each stage of the sales pipeline. This enables better forecasting, prioritization, and management of customer relationships.

Option B: Customer asset tracking monitors product ownership, not sales pipeline progress.

Option C: Sales performance metrics measure results, not track deal progress in real-time.

Option D: Customer segmentation categorizes customers but does not track deals.

Thus, the CRM feature for monitoring deal progress is Sales tracking.

The Development phase of the SDLC is where programmers write, compile, and build code to create the actual software system. This is based on the specifications created in the design phase.

Option A (Deployment): Involves moving the system to production.

Option B (Testing): Focuses on defect detection and validation.

Option D (Design): Defines technical specifications but does not involve coding.

Thus, the coding occurs in the Development phase.

Comprehensive and Detailed Explanation From Exact Extract:

A CRM system facilitates collaboration among sales, marketing, and customer service teams by acting as a centralized platform where customer-related information is stored, updated, and shared. This centralized sharing platform allows all teams to:

Access the same up-to-date customer profiles, interaction history, and preferences

See previous communications, issues, and opportunities related to each customer

Coordinate activities (such as campaigns, sales follow-ups, and support cases) based on a unified view of the customer

Avoid duplicated efforts and conflicting messages

By providing this shared environment, CRM ensures that each team’s actions are informed by the same data, improving coordination and the overall customer experience.

Option A (Managing campaign workflow approvals) is a specific marketing process, not the broader cross-team collaboration capability.

Option B (Assigning shared customer tasks) can be a useful function, but it is one feature inside the broader concept of collaborating via a centralized platform.

Option C (Tracking internal communication metrics) focuses on measurement rather than enabling day-to-day collaboration around customer information.

Therefore, the way a CRM system most directly facilitates collaboration among sales, marketing, and customer service is by providing a centralized sharing platform for customer data and interactions.

Comprehensive and Detailed Explanation From Exact Extract:

Within the SDLC, integration testing is the testing phase that focuses on how different components or modules of the software work together. After individual units or components have been tested in isolation (unit testing), integration testing verifies that the interactions, data flows, and interfaces between these components function correctly as a combined system segment.

Integration testing aims to:

Detect interface defects between modules.

Ensure that combined components communicate and cooperate as intended.

Validate that data passed between modules is correct and handled properly.

Why the other options are incorrect:

B. Unit testing – Focuses on individual components or functions in isolation to verify that each one works correctly on its own, not how they work together.

C. Parallel testing – Involves running the new system and the old system simultaneously to compare outputs, often used during system replacement or migration, not specifically about module interaction.

D. Acceptance testing – Conducted to verify that the system meets business requirements and user needs, typically performed by end users or customers near the end of the SDLC; it is not focused on internal component integration.

Therefore, integration testing is the SDLC testing phase that specifically focuses on how different components of the software work together.