What are two types of security that can be implemented across every phase of the Build, Ship, and Run lifecycle of a workload? (Choose two )

Question

Options

• ARuntime Security
• BFirewalling
• CVulnerability Management
• DCompliance or Configuration Management

• A
  6% (2)
• B
  3% (1)
• C
  92% (33)

Explanation

Vulnerability Management (C) and Compliance/Configuration Management (D) are correct because both practices span the entire Build, Ship, and Run lifecycle: vulnerabilities can be scanned in source code (Build), container images (Ship), and live workloads (Run), while compliance checks apply to code configurations, packaged artifacts, and running environments alike. Runtime Security (A) is incorrect because - as the name implies - it is scoped exclusively to the Run phase, monitoring live workloads for threats, and has no meaningful role during Build or Ship. Firewalling (B) is a network-layer control that primarily protects running infrastructure and does not extend naturally to the Build or Ship phases where there is no network traffic to filter. A helpful memory tip: ask yourself "can this practice touch code, a container image, AND a live system?" - if the answer is yes for all three, it's a lifecycle-wide control; Vulnerability Management and Compliance Management both pass that test, while Runtime Security and Firewalling do not.

No community discussion yet for this question.