Security awareness programs require ongoing engagement to remain effective. If security incidents decrease initially but increase after eight months, the most likely cause is thatmessage materials are few and static, and renewal is not taking place(C). Static content becomes outdated or ignored over time, reducing its impact. Regular updates, new campaigns, and varied delivery methods (e.g., videos, quizzes) are essential to maintain employee awareness and adapt to evolving threats, as perISO/IEC 27001orNISTsecurity awareness guidelines.

Insufficient budget (A):While budget constraints could limit program scope, there’s no evidence in the scenario to suggest this is the primary issue.

Scope too narrow (B):A narrow scope might limit effectiveness initially, but the initial success suggests the scope was adequate; the issue is sustaining engagement.

Lack of resources for instructor-led sessions (D):Instructor-led sessions are one delivery method, but the core issue is likely outdated content rather than delivery format.

InITIL, theservice operationphase focuses on delivering and managing services, including activities like communicating scheduled outages (A), reporting service performance (B), and handling escalations (C).Defining service strategy(D) is part of theservice strategyphase, not service operation, as it involves planning and aligning services with business goals.

The customer’s focus on incorporatingfuture functional requirementsindicates a need forperfective maintenance(B). Inapplication management, perfective maintenance involves enhancing software to add new features or improve functionality to meet evolving business needs, such as adding new modules or capabilities.

Preventive maintenance (A):Focuses on preventing issues by optimizing performance or addressing potential problems, not adding new features.

Corrective maintenance (C):Involves fixing bugs or errors, not incorporating new functionality.

Adaptive maintenance (D):Adapts software to environmental changes (e.g., new operating systems), not specifically for new functional requirements.

Perfective maintenance aligns with theSDLC’s maintenance phase, ensuring the software evolves to support future business requirements.