Newly Released WGU Information-Technology-Management Exam PDF

Comprehensive and Detailed Explanation From Exact Extract:

The review conducted after deployment (often called a post-implementation review or post-deployment review) in the SDLC is intended to evaluate how successful the system is in the live environment and to identify opportunities for improvement. This review looks at:

Whether the system is delivering expected business benefits

How well it performs in real operational conditions

Feedback from users about usability and effectiveness

Issues encountered during and after rollout

Lessons learned for future projects

The emphasis is on continuous improvement and learning from the implementation experience to refine the current system and improve future system development efforts.

Option A (To plan the next phase of system upgrades) may be a result of the review, but planning upgrades is not the primary goal of the review itself.

Option B (To ensure users are properly trained) is part of deployment and change management activities, not the main goal of a post-deployment review.

Option D (To confirm the system meets original requirements) is largely addressed during system and acceptance testing before deployment.

Therefore, the goal of reviewing after deployment is to evaluate system success and identify improvements.

Comprehensive and Detailed Explanation From Exact Extract:

Intrusion detection is the process of using monitoring tools and systems to identify and alert on unauthorized or suspicious activities on networks or hosts, often in real time. Intrusion Detection Systems (IDS) analyze traffic or system events to detect:

Unauthorized access attempts

Malicious or abnormal behavior

Known attack signatures or anomalies

When potential intrusions are detected, these systems can generate alerts, and in some configurations (IDS/IPS), they may also help automate responses or integrate with other security tools.

Why the other options are incorrect:

A. Penetration testing – Simulates attacks to find vulnerabilities but is periodic and manual, not continuous real-time monitoring.

B. Access control – Governs who is allowed to access what (through authentication and authorization). It is preventive, not primarily focused on real-time detection of unauthorized attempts once they occur.

C. Log review – Involves analyzing stored logs, often after the fact, for auditing or investigation. It is not necessarily real-time detection.

Therefore, the correct answer is D. Intrusion detection, because it is the process that specifically uses monitoring tools to detect and respond to unauthorized access attempts in real time.

Comprehensive and Detailed Explanation From Exact Extract:

Symmetrical (symmetric) encryption uses a single shared secret key for both encryption and decryption of data. Both the sender and the receiver must have access to the same key, and the security of the communication depends on keeping that key confidential.

Key points about symmetric encryption:

One key for both directions: The same key encrypts plaintext and decrypts ciphertext.

Fast and efficient: Often used for encrypting large amounts of data (e.g., AES).

Commonly used in secure channels after an initial key exchange has occurred.

Why the other options are incorrect:

A. Asymmetrical encryption – Uses a public key for encryption and a private key for decryption. It does not rely on a single shared secret key; rather, it uses a key pair.

B. Secure hashing – A hash function transforms data into a fixed-size value; it is one-way and does not support decryption. Hashing is not an encryption method for secure two-way communication.

C. Data masking – Obscures data (e.g., hiding digits of a credit card number) for privacy in non-production use or display; it is not an encryption method for secure communication.

Therefore, the correct answer is D. Symmetrical encryption, because it specifically involves secure communication using a shared secret key known to both parties.

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.