Question 360
Loss of one controller makes all policy updates fail across the virtual network and recovery options are undefined. Which software-defined networking control best addresses the design issue?
- SDN flow-rule audit
- Northbound API authorization
- Southbound API authentication
- SDN control-plane availability
- SDN controller access security
Explanation
Correct Answer
D:Controller redundancy and resilience planning reduce single-control-plane failure risks. Device behavior during controller loss must be tested.
Incorrect Answers
A:Flow-rule review correlates intended policy with actual switch forwarding entries for situations characterized by unexplained programmable forwarding entries; the case points instead to resilience of centralized network control.
B:Northbound authorization governs which applications can invoke controller capabilities and at what scope for situations characterized by application-to-controller API privileges; the case points instead to resilience of centralized network control.
C:Authenticating and protecting southbound communications prevents untrusted control messages from altering device state when the underlying evidence concerns trust between controller and switches rather than the stated resilience of centralized network control.
E:Controllers are high-value management-plane assets; strong identity, RBAC and audit protect broad network policy authority; that is relevant to privileged centralized network programming but does not directly account for resilience of centralized network control.
Question 361
A multi-tenant provider runs firewall functions on shared hosts but must prevent one tenant from modifying another's rule set. Which network-function virtualization measure best satisfies the request?
- Virtual firewall policy separation
- VNF lifecycle orchestration
- VNF resource isolation
- VNF image signature validation
Explanation
Correct Answer
A:Tenant isolation in virtual network functions limits management and data-plane exposure among customers. Scope controls must be tested.
Incorrect Answers
B:Orchestration coordinates VNF deployment, monitoring, scaling and retirement for situations characterized by managed lifecycle of network functions; the case points instead to separation of tenant firewall configurations.
C:Compute quotas and placement controls help prevent noisy-neighbor resource exhaustion among virtualized functions when analysts encounter performance isolation among VNFs; this question instead describes separation of tenant firewall configurations.
D:Signed image verification checks approved VNF artifact provenance and integrity; that is relevant to trustworthy virtual network appliance image but does not directly account for separation of tenant firewall configurations.
Question 362
Operators deploy virtual router appliances from a repository and want to detect tampered images before instantiation. Which network-function virtualization measure best satisfies the request?
- VNF image signature validation
- VNF lifecycle orchestration
- Service function chaining verification
- Virtual firewall policy separation
Explanation
Correct Answer
A:Signed image verification checks approved VNF artifact provenance and integrity. Registry access controls protect distribution.
Incorrect Answers
B:Orchestration coordinates VNF deployment, monitoring, scaling and retirement; this characterizes managed lifecycle of network functions, whereas the reported condition is trustworthy virtual network appliance image.
C:Service-chain validation ensures traffic crosses required security functions in the intended sequence; the operational difference is required order of virtual traffic services versus the scenario's trustworthy virtual network appliance image.
D:Tenant isolation in virtual network functions limits management and data-plane exposure among customers for situations characterized by separation of tenant firewall configurations; the case points instead to trustworthy virtual network appliance image.
Question 363
One overloaded intrusion detection VNF starves other customer functions for CPU and memory on shared infrastructure. Which network-function virtualization measure best satisfies the request?
- VNF image signature validation
- Service function chaining verification
- VNF resource isolation
- Virtual firewall policy separation
Explanation
Correct Answer
C:Compute quotas and placement controls help prevent noisy-neighbor resource exhaustion among virtualized functions.
Incorrect Answers
A:Signed image verification checks approved VNF artifact provenance and integrity for the specific concern of trustworthy virtual network appliance image, not the requirement involving performance isolation among VNFs.
B:Service-chain validation ensures traffic crosses required security functions in the intended sequence; the operational difference is required order of virtual traffic services versus the scenario's performance isolation among VNFs.
D:Tenant isolation in virtual network functions limits management and data-plane exposure among customers; this characterizes separation of tenant firewall configurations, whereas the reported condition is performance isolation among VNFs.
Question 364
Packet inspection is silently bypassed because a virtualized chain routes client traffic directly to the application backend. Which network-function virtualization measure best satisfies the request?
- VNF lifecycle orchestration
- Virtual firewall policy separation
- Service function chaining verification
- VNF image signature validation
Explanation
Correct Answer
C:Service-chain validation ensures traffic crosses required security functions in the intended sequence. Network paths, not merely service inventory, determine enforcement.
Incorrect Answers
A:Orchestration coordinates VNF deployment, monitoring, scaling and retirement when the underlying evidence concerns managed lifecycle of network functions rather than the stated required order of virtual traffic services.
B:Tenant isolation in virtual network functions limits management and data-plane exposure among customers for situations characterized by separation of tenant firewall configurations; the case points instead to required order of virtual traffic services.
D:Signed image verification checks approved VNF artifact provenance and integrity in a setting defined by trustworthy virtual network appliance image; the observed issue is required order of virtual traffic services.
Question 365
Virtual routers are deployed without reliable patch, health, retirement or configuration-state tracking. Which network-function virtualization measure best satisfies the request?
- VNF image signature validation
- VNF resource isolation
- Virtual firewall policy separation
- Service function chaining verification
- VNF lifecycle orchestration
Explanation
Correct Answer
E:Orchestration coordinates VNF deployment, monitoring, scaling and retirement. Security must be included in templates and approval workflows.
Incorrect Answers
A:Signed image verification checks approved VNF artifact provenance and integrity when analysts encounter trustworthy virtual network appliance image; this question instead describes managed lifecycle of network functions.
B:Compute quotas and placement controls help prevent noisy-neighbor resource exhaustion among virtualized functions; its distinguishing scope is performance isolation among VNFs, not the reported managed lifecycle of network functions.
C:Tenant isolation in virtual network functions limits management and data-plane exposure among customers when the underlying evidence concerns separation of tenant firewall configurations rather than the stated managed lifecycle of network functions.
D:Service-chain validation ensures traffic crosses required security functions in the intended sequence; it handles required order of virtual traffic services, while the decisive evidence in the question is managed lifecycle of network functions.
Question 366
A web container starts with UID 0 unnecessarily, making a compromise more damaging if isolation fails or host mounts are exposed. Which container security control best addresses the weakness?
- Drop unnecessary Linux capabilities
- Read-only root filesystem
- Container image vulnerability scanning
- Run containers as non-root
Explanation
Correct Answer
D:Non-root execution limits process authority inside a container and reduces certain escape consequences. Effective privileges still depend on runtime settings.
Incorrect Answers
A:Capability reduction removes selected privileged operations from container processes when the underlying evidence concerns excessive kernel privileges in application containers rather than the stated excessive root identity inside container.
B:A read-only root filesystem limits writable areas in a container; the operational difference is unauthorized modification of container image contents versus the scenario's excessive root identity inside container.
C:Image scanning compares OS and software components with vulnerability data; it handles vulnerabilities in packaged container layers, while the decisive evidence in the question is excessive root identity inside container.
Question 367
A small API container retains powerful kernel capabilities even though it only needs outbound network access and file reads. Which container security control best addresses the weakness?
- Run containers as non-root
- Drop unnecessary Linux capabilities
- Container image vulnerability scanning
- Container seccomp profile
Explanation
Correct Answer
B:Capability reduction removes selected privileged operations from container processes. Do not grant broad privileges for convenience.
Incorrect Answers
A:Non-root execution limits process authority inside a container and reduces certain escape consequences for the specific concern of excessive root identity inside container, not the requirement involving excessive kernel privileges in application containers.
C:Image scanning compares OS and software components with vulnerability data in a setting defined by vulnerabilities in packaged container layers; the observed issue is excessive kernel privileges in application containers.
D:Seccomp filters constrain Linux system calls available to a container process when analysts encounter syscall attack surface exposed to container; this question instead describes excessive kernel privileges in application containers.
Question 368
A production container should not allow malware to modify its application binaries after deployment, aside from specified temporary directories. Which container security control best addresses the weakness?
- Container image vulnerability scanning
- Read-only root filesystem
- Run containers as non-root
- Drop unnecessary Linux capabilities
Explanation
Correct Answer
B:A read-only root filesystem limits writable areas in a container. Planned volumes and tmpfs mounts can support required state.
Incorrect Answers
A:Image scanning compares OS and software components with vulnerability data; it handles vulnerabilities in packaged container layers, while the decisive evidence in the question is unauthorized modification of container image contents.
C:Non-root execution limits process authority inside a container and reduces certain escape consequences; it handles excessive root identity inside container, while the decisive evidence in the question is unauthorized modification of container image contents.
D:Capability reduction removes selected privileged operations from container processes; it handles excessive kernel privileges in application containers, while the decisive evidence in the question is unauthorized modification of container image contents.
Question 369
An application needs only a limited set of system calls, and administrators want to block access to dangerous unused kernel interfaces. Which container security control best addresses the weakness?
- Read-only root filesystem
- Container seccomp profile
- Container image vulnerability scanning
- Drop unnecessary Linux capabilities
Explanation
Correct Answer
B:Seccomp filters constrain Linux system calls available to a container process. Careful testing avoids breaking legitimate functionality.
Incorrect Answers
A:A read-only root filesystem limits writable areas in a container; that is relevant to unauthorized modification of container image contents but does not directly account for syscall attack surface exposed to container.
C:Image scanning compares OS and software components with vulnerability data for situations characterized by vulnerabilities in packaged container layers; the case points instead to syscall attack surface exposed to container.
D:Capability reduction removes selected privileged operations from container processes in a setting defined by excessive kernel privileges in application containers; the observed issue is syscall attack surface exposed to container.
Question 370
Teams pull base images from a registry without knowing whether packaged libraries contain publicly disclosed vulnerabilities. Which container security control best addresses the weakness?
- Read-only root filesystem
- Run containers as non-root
- Drop unnecessary Linux capabilities
- Container image vulnerability scanning
- Container seccomp profile
Explanation
Correct Answer
D:Image scanning compares OS and software components with vulnerability data. Rebuilds and runtime verification ensure fixes reach workloads.
Incorrect Answers
A:A read-only root filesystem limits writable areas in a container when analysts encounter unauthorized modification of container image contents; this question instead describes vulnerabilities in packaged container layers.
B:Non-root execution limits process authority inside a container and reduces certain escape consequences in a setting defined by excessive root identity inside container; the observed issue is vulnerabilities in packaged container layers.
C:Capability reduction removes selected privileged operations from container processes in a setting defined by excessive kernel privileges in application containers; the observed issue is vulnerabilities in packaged container layers.
E:Seccomp filters constrain Linux system calls available to a container process for situations characterized by syscall attack surface exposed to container; the case points instead to vulnerabilities in packaged container layers.