Security Architecture

405 questions

Question 161Question

A healthcare organization must connect legacy diagnostic imaging equipment running unsupported operating systems to the enterprise network. The architecture must allow authorized workstations to retrieve image files while preventing lateral movement if an imaging system is compromised, and restricting administrative access to authenticated technicians. Which of the following network design strategies best fulfills these security requirements?

Show answer & explanation

Answer: Isolate the diagnostic equipment on a dedicated VLAN with strict East-West firewall rules and require administrative management to occur through a secure jump host.

Answer

Isolate the diagnostic equipment on a dedicated VLAN with strict East-West firewall rules and require administrative management to occur through a secure jump host.
Isolating legacy hardware on a dedicated VLAN with East-West firewall rules restricts lateral movement across internal zones, while requiring access via a jump host ensures administrative traffic is authenticated, monitored, and controlled.

Step-by-Step Solution

1
Analyze the threat profile of legacy biomedical equipment.
Identify that unsupported legacy operating systems present unpatchable vulnerability risks and require network-level containment.
Unmitigated vulnerabilities on legacy systems make them high-risk targets for compromise and lateral movement.
2
Evaluate internal network traffic control mechanisms.
Determine that East-West firewall policy enforcement and VLAN segmentation are required between internal subnets.
Perimeter firewalls only inspect North-South traffic and cannot prevent lateral movement between internal zones.
3
Establish secure administrative access controls.
Require management traffic to traverse a bastion host / jump server with multifactor authentication and session logging.
Direct management sessions from general user subnets to sensitive isolated zones introduce severe security risks.

Key Concept

Network Segmentation and East-West Traffic Isolation
Question 162Question

To enforce defense-in-depth across a multi-tenant cloud infrastructure hosting both virtual machines and container workloads, a platform security engineer must align security mechanisms with their specific operational boundaries. Match each virtualization or containerization technology on the left with its primary isolation boundary or resource control capability on the right.

Click a left item, then click its matching right item

Items

Linux Namespaces
Control Groups (cgroups)
Type-1 Bare-Metal Hypervisor
Kernel-level Security Modules (e.g., AppArmor / SELinux)

Matches

Show answer & explanation

Answer

Linux Namespaces matches with partitioning system resources; Control Groups (cgroups) matches with limiting hardware consumption; Type-1 Bare-Metal Hypervisor matches with enforcing hardware-assisted ring isolation between guest OS instances; and Kernel-level Security Modules matches with restricting process privileges via Mandatory Access Control profiles.
Each technology provides a specific layer of defense-in-depth: Linux Namespaces partition system resource visibility (PIDs, network interfaces, mount points); Control Groups (cgroups) govern hardware resource consumption limits (CPU, memory, I/O rates); Type-1 Bare-Metal Hypervisors manage guest virtual machines via hardware-assisted execution boundaries; and Kernel-level Security Modules enforce Mandatory Access Control policies to restrict process capabilities and syscall access on the shared host kernel.

Step-by-Step Solution

1
Analyze Linux Namespaces functionality
Namespaces control process visibility of system abstractions such as process IDs, network interfaces, and file system mounts.
Namespaces determine what an isolated containerized process can see.
2
Analyze Control Groups (cgroups) functionality
cgroups enforce resource allocations and ceilings for CPU usage, memory allocation, and I/O rates.
cgroups determine what host resources an isolated process can consume.
3
Analyze Type-1 Bare-Metal Hypervisor isolation
Bare-metal hypervisors run directly on hardware and enforce strict hardware-level memory and CPU Ring-0 isolation between guest kernels.
Hypervisors provide hardware-assisted virtualization boundaries between fully independent operating systems.
4
Analyze Kernel-level Security Modules (AppArmor/SELinux)
Security modules restrict syscall privileges and file path operations using Mandatory Access Control rules.
MAC profiles restrict container capabilities at runtime, preventing container escapes from accessing sensitive host system resources.

Key Concept

Containerization vs. Virtualization Isolation Architecture
Estimated Time:2m 0s
Question 163Question

A financial institution requires a storage security architecture for its high-performance database cluster. The design must protect data at rest against physical drive theft from the data center without incurring host operating system processor overhead, while centralizing cryptographic key management inside a dedicated tamper-resistant hardware appliance. Which of the following solutions best satisfies these security and architectural requirements?

Show answer & explanation

Answer: Self-Encrypting Drives (SEDs) integrated with an enterprise Hardware Security Module (HSM)

Answer

Self-Encrypting Drives (SEDs) integrated with an enterprise Hardware Security Module (HSM) best satisfies the requirements.
Self-Encrypting Drives (SEDs) perform symmetric bulk encryption directly on the drive controller hardware, ensuring data at rest is protected without placing cryptographic processing burdens on the host server CPU. Integrating SEDs with a Hardware Security Module (HSM) provides dedicated, tamper-resistant hardware for central key generation, storage, and lifecycle management, satisfying all criteria in the scenario.

Step-by-Step Solution

1
Analyze requirement for physical storage encryption without host CPU overhead
Hardware-level disk encryption, such as Self-Encrypting Drives (SEDs), performs cryptographic operations directly on the disk controller, avoiding host processor degradation.
Software-based disk or database column encryption consumes host CPU cycles and memory.
2
Analyze requirement for centralized, tamper-resistant key management
Hardware Security Modules (HSMs) provide tamper-evident key storage and centralized lifecycle management for storage encryption keys.
Storing keys in software or host memory exposes them to memory dump attacks and lacks hardware tamper resistance.
3
Synthesize the optimal combined storage architecture
Combining SEDs with an HSM delivers full hardware-offloaded data-at-rest protection and secure key management.
This combination directly fulfills all scenario constraints.

Key Concept

Storage Security and Key Management Architecture
Question 164Question

An autonomous manufacturing enterprise is transitioning its edge-compute microservices and industrial IoT telemetry pipeline to a Zero Trust Architecture (ZTA). A security architect must define control plane and data plane operational requirements to enforce core Zero Trust tenets across all component communications.

Which of the following architectural requirements MUST be implemented to strictly align with Zero Trust Architecture principles? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Dynamically evaluate device health, user identity, and contextual risk attributes at the Policy Decision Point (PDP) for every transaction before authorizing access.; Enforce mutual TLS (mTLS) and continuous re-authorization for all inter-service communications regardless of physical or logical network location.

Answer

The correct requirements are dynamically evaluating device health, identity, and contextual risk at the Policy Decision Point for every transaction, and enforcing mutual TLS with continuous re-authorization across all inter-service communications regardless of network location.
Zero Trust Architecture strictly mandates explicit verification and continuous evaluation. Requiring the Policy Decision Point (PDP) to dynamically evaluate posture, identity, and risk metrics for every transaction ensures access decisions reflect real-time threat contexts. Furthermore, enforcing mutual TLS (mTLS) and continuous re-authorization across all inter-service communications aligns with the assumed breach paradigm, eliminating implicit trust based on network topology.

Step-by-Step Solution

1
Identify core Zero Trust Architecture tenets regarding request evaluation.
Zero Trust requires explicit verification per transaction using dynamic telemetry (identity, posture, environmental risk) handled by the Policy Decision Point (PDP).
Implicit trust is eliminated; authentication and authorization are contextual and continuous rather than static or location-based.
2
Analyze data plane network communication controls under Zero Trust.
All traffic must be secured end-to-end (e.g., using mTLS) and continuously re-verified at Policy Enforcement Points (PEPs) closest to the resources.
The underlying network is assumed compromised, necessitating microsegmentation and continuous session validation regardless of physical VLAN or subnet position.
3
Evaluate and eliminate perimeter-reliance misconceptions.
Reject options proposing post-authentication implicit trust zones or reliance on centralized perimeter firewalls in place of PEPs.
Legacy perimeter security fails to protect against lateral movement and violates the assumed breach tenet of Zero Trust.

Key Concept

Zero Trust Architecture Principles: Explicit Verification, Continuous Authentication, Assumed Breach, and Microsegmentation
Question 165Question

A security administrator is configuring host-level hardening for an application running in a Linux container environment. Which of the following security mechanisms directly restrict container resource usage and limit accessible host kernel system calls? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Control groups (cgroups); Secure Computing Mode (seccomp) profiles

Answer

Control groups (cgroups) and Secure Computing Mode (seccomp) profiles are the correct choices.
Control groups (cgroups) provide resource metering and limiting (CPU, memory, storage I/O) for containerized processes on the host. Secure Computing Mode (seccomp) restricts the system call interface exposed by the host kernel to the container, minimizing potential kernel exploitation vectors.

Step-by-Step Solution

1
Identify the host-level mechanism that restricts hardware resource allocation for containers.
Control groups (cgroups) manage and limit resources like memory, CPU, and disk I/O per container.
Prevents a single container from consuming all host resources.
2
Identify the mechanism that restricts process interactions with the host kernel interface.
Seccomp restricts system call privileges available to containerized processes.
Reduces kernel attack surface by blocking unnecessary system calls.

Key Concept

Linux kernel mechanisms for container resource governance and system call filtering
Question 166Question

A security administrator is configuring runtime security settings for a container execution host that processes untrusted third-party workloads. Which TWO of the following security controls should be implemented to reduce the kernel attack surface and prevent persistent host filesystem modifications during container execution?

Select all that apply

Show answer & explanation

Answer: Apply secure computing mode (seccomp) profiles to restrict the system calls containers can make to the host kernel.; Mount the container's root filesystem as read-only and redirect temporary write operations to volatile memory storage.

Answer

The two correct security controls are restricting host kernel system calls via seccomp profiles and mounting the container root filesystem as read-only while using volatile memory for temporary write operations.
Implementing seccomp profiles directly reduces the kernel attack surface by blocking dangerous or unnecessary syscalls from reach of containerized applications. Additionally, forcing a read-only root filesystem prevents unauthorized file creation or persistent malicious modifications within the container image.

Step-by-Step Solution

1
Analyze the goal of reducing kernel attack surface exposure.
System call filtering (seccomp) limits the syscalls available to container processes, preventing compromised containers from invoking vulnerable host kernel routines.
Containers share the host operating system kernel directly, making syscall filtering essential for kernel attack surface reduction.
2
Analyze the goal of preventing persistent host filesystem modifications.
Configuring root filesystems as read-only forces any file modifications to fail or stay strictly in ephemeral storage.
Immutable infrastructure principles ensure that malicious modifications cannot persist across container restarts or infect the host file structure.

Key Concept

Container Host Hardening & Kernel Attack Surface Reduction
Question 167Question

A financial services company hosts multi-tenant microservices handling sensitive transaction processing. Following a penetration test, security assessors demonstrated that a compromised container could exploit a host Linux kernel vulnerability to gain root privileges on the underlying host OS, compromising adjacent containers. To mitigate this specific attack vector while preserving container deployment automation, which of the following controls should the security team implement?

Show answer & explanation

Answer: Deploy sandboxed container runtimes that utilize lightweight virtual machines to isolate each container footprint behind a dedicated kernel boundary.

Answer

Deploy sandboxed container runtimes that utilize lightweight virtual machines to isolate each container footprint behind a dedicated kernel boundary.
Deploying sandboxed container runtimes (such as Kata Containers or Firecracker) wraps each container workload inside a lightweight virtual machine. This provides a dedicated guest kernel for each container instance, ensuring that even if an attacker executes a kernel exploit inside a container, it cannot escape into the host OS kernel or affect adjacent tenant containers.

Step-by-Step Solution

1
Analyze the reported vulnerability vector
The attack relies on a kernel flaw in the host OS shared across traditional container environments.
Standard containers share the host kernel, meaning a kernel-level exploit bypasses standard container isolation.
2
Evaluate technical controls for kernel isolation
Sandboxed container runtimes wrap containers inside lightweight micro-VMs.
Micro-VM container runtimes provide a dedicated kernel for each workload while retaining fast spin-up and container orchestrator compatibility.
3
Differentiate from insufficient controls
Standard Linux namespaces, microsegmentation, and management RBAC do not isolate the kernel layer.
Only hardware-assisted hypervisor virtualization (even lightweight) removes the shared host kernel single point of compromise.

Key Concept

Container Micro-VM Sandboxing vs. Shared Kernel Isolation
Question 168Question

Match each storage security and data protection mechanism to its primary enterprise operational control function.

Click a left item, then click its matching right item

Items

LUN Masking
Hardware Security Module (HSM)
Endpoint Data Loss Prevention (DLP)
Tokenization

Matches

Show answer & explanation

Answer

LUN Masking matches restricting storage volume access by host HBA ports; Hardware Security Module matches dedicated hardware key management; Endpoint Data Loss Prevention matches monitoring and blocking unauthorized file transfers to local external storage; Tokenization matches replacing sensitive data fields with non-sensitive surrogate values.
Each security solution fulfills a distinct storage architecture requirement: LUN Masking isolates SAN volumes per host HBA, HSMs secure root cryptographic keys within dedicated hardware, Endpoint DLP enforces egress data policies on client endpoints, and Tokenization replaces sensitive data elements with non-cryptographic tokens.

Step-by-Step Solution

1
Analyze SAN block storage isolation mechanisms.
Identify LUN Masking as the storage architecture technique used to restrict volume visibility to authorized host HBAs.
Storage Area Networks require logical partitioning so servers only see assigned storage blocks.
2
Evaluate key protection architectures.
Map dedicated physical hardware appliances for root keys to Hardware Security Modules (HSMs).
HSMs offer hardened cryptographic boundaries separate from general application software.
3
Differentiate endpoint data protection controls from backend data obfuscation.
Assign file exfiltration blocking on host nodes to Endpoint DLP, and database field surrogate substitution to Tokenization.
DLP inspects user data transport actions, while tokenization alters data storage representations.

Key Concept

Enterprise Data Protection and Storage Architecture Controls
Question 169Question

An industrial manufacturing plant operates a Safety Instrumented System (SIS) to control physical emergency shutdown valves. The security architecture team must forward real-time operational telemetry from the SIS domain to a cloud-based enterprise monitoring platform. However, regulatory standards mandate that no network path can exist that allows incoming commands or external traffic to reach the safety controllers under any circumstances. Which of the following network segmentation controls best satisfies this requirement?

Show answer & explanation

Answer: A physical data diode deployed at the boundary between the OT network collectors and the enterprise network

Answer

Deploying a physical data diode at the boundary between the operational technology collectors and the enterprise network is the optimal solution.
A physical data diode uses hardware-level mechanisms (such as an LED pointing to a photo-receiver across an optical gap) to enforce unidirectional communication at Layer 1. This physical design ensures that telemetry can be sent to the enterprise network while rendering inbound signal transmission physically impossible, fully satisfying the requirement to prevent external command injection into safety controllers.

Step-by-Step Solution

1
Analyze the functional and security requirements of the scenario
Telemetry data must flow outbound from the Safety Instrumented System (SIS) to the enterprise platform, but absolute isolation against inbound traffic/commands must be guaranteed.
Safety Instrumented Systems control critical physical processes where unintended software command injection could cause physical harm or infrastructure failure.
2
Evaluate candidate network segmentation controls against the strict non-reversibility requirement
Software controls (firewalls, jump boxes, pVLANs) maintain bidirectional logical capabilities or stateful session return channels.
Any software-defined control can potentially be bypassed via zero-day vulnerabilities, configuration errors, or session exploitation.
3
Identify the hardware-enforced unidirectional isolation mechanism
A physical data diode allows optical transmission in only one direction while lacking physical receiving hardware on the sender side.
This guarantees at the physical layer (Layer 1) that return traffic, acknowledgments, or inbound exploits cannot travel backward into the safety zone.

Key Concept

Unidirectional Data Diodes and Industrial Control System (ICS/OT) Microsegmentation
Estimated Time:2m 0s
Question 170Question

A security architect is updating an enterprise data protection framework to address regulatory compliance and storage security requirements across cloud and on-premises infrastructure. Match each data protection technology to the enterprise operational requirement it primarily fulfills.

Click a left item, then click its matching right item

Items

Hardware Security Module (HSM)
Format-Preserving Tokenization
SAN LUN Masking
DLP Document Fingerprinting

Matches

Show answer & explanation

Answer

Hardware Security Module (HSM) matches dedicated cryptographic key protection in tamper-resistant hardware; Format-Preserving Tokenization matches substituting sensitive values with formatted surrogates; SAN LUN Masking matches isolating storage volumes by Host Bus Adapter (HBA) WWNs; and DLP Document Fingerprinting matches identifying sensitive unstructured file exfiltration using content hashes.
Each pair correctly matches a key storage and data protection architecture technology to its operational role. HSM provides physical and logical protection for master keys; format-preserving tokenization protects sensitive payloads while avoiding application breaking changes; SAN LUN masking enforces volume access boundaries; and DLP document fingerprinting protects unstructured IP exfiltration.

Step-by-Step Solution

1
Analyze key management requirements
Identify that dedicated, tamper-resistant cryptographic hardware isolation maps to a Hardware Security Module (HSM).
HSMs provide specialized cryptographic protection for root and master keys.
2
Evaluate data masking and schema preservation needs
Identify that substituting sensitive fields with surrogate values while maintaining string structure maps to Format-Preserving Tokenization.
Tokenization replaces sensitive values while format-preserving techniques maintain field length and validation syntax.
3
Examine SAN access control mechanisms
Identify that restricting LUN visibility using World Wide Names (WWNs) at the storage target maps to SAN LUN Masking.
LUN masking prevents unauthorized servers on the SAN fabric from seeing or mounting storage volumes allocated to other hosts.
4
Examine egress monitoring technologies
Identify that matching unstructured document content against stored cryptographic signatures maps to DLP Document Fingerprinting.
Fingerprinting enables Data Loss Prevention solutions to track proprietary file forms and exact text patterns during transfer.

Key Concept

Enterprise storage security controls must align specific architectural mechanisms—such as hardware key protection, storage volume isolation, data tokenization, and DLP content inspection—with distinct threat models and operational constraints.
Question 171Question

A fintech enterprise is redesigning its cloud-native payment gateway architecture to achieve PCI-DSS compliance. The security architecture must restrict lateral movement between individual microservices inside the cardholder data environment (CDE), enforce strict inline policy inspection for outbound internet-bound management connections, and eliminate reliance on internal network location trust. Which of the following network architecture controls should the security team implement to satisfy these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Implement microsegmentation using software-defined networking (SDN) policies to enforce granular East-West traffic filtering between workloads.; Deploy an inline Next-Generation Firewall (NGFW) at the egress boundary to inspect and filter North-South outbound management traffic.

Answer

The security team should implement microsegmentation via SDN policies to restrict East-West workload communication and deploy an inline NGFW at the egress boundary for North-South traffic inspection.
Microsegmentation enables fine-grained policy enforcement at the individual workload level, effectively isolating systems and blocking East-West lateral movement inside the cardholder data environment. Deploying an inline NGFW at the perimeter boundary ensures all outbound (North-South) management traffic undergoes application-aware inspection and threat prevention prior to egressing.

Step-by-Step Solution

1
Evaluate internal workload isolation requirements for lateral movement prevention.
Microsegmentation leverages software-defined controls to isolate workloads at the granular container or host interface level.
Traditional network boundaries (VLANs) do not prevent lateral movement between hosts on the same subnet, whereas microsegmentation enforces granular rules on East-West traffic.
2
Evaluate egress network boundary inspection requirements.
An inline Next-Generation Firewall (NGFW) monitors and inspects North-South traffic crossing the perimeter.
Egress filtering with application-layer awareness ensures outbound sessions to external services adhere to compliance policies and prevents unauthorized data exfiltration.

Key Concept

Secure Network Design, Microsegmentation, and Egress Boundary Filtering
Question 172Question

A healthcare technology organization is designing a data protection architecture to archive multi-terabyte patient records in a cloud-based storage repository. Regulatory mandates require that the enterprise security team maintain exclusive physical control over key generation, rotation, and revocation lifecycle operations. Additionally, the bulk encryption mechanism must support high-throughput processing for mass ingestion without delegating root key custody to the cloud service provider. Which of the following storage security architecture configurations best satisfies both performance requirements and regulatory key ownership constraints?

Show answer & explanation

Answer: Perform bulk symmetric data encryption on-premises using Data Encryption Keys (DEKs) that are wrapped by Key Encryption Keys (KEKs) generated and managed inside a local Hardware Security Module (HSM) prior to uploading the ciphertext.

Answer

Bulk symmetric data encryption on-premises utilizing Data Encryption Keys (DEKs) wrapped by Key Encryption Keys (KEKs) managed inside an enterprise Hardware Security Module (HSM) before cloud upload.
Envelope encryption combined with an on-premises Hardware Security Module (HSM) satisfies both requirements. Symmetric algorithms efficiently handle multi-terabyte bulk payload encryption, while maintaining KEKs within a physical on-premises HSM guarantees complete enterprise custody over key generation, rotation, and revocation operations.

Step-by-Step Solution

1
Analyze Key Lifecycle and Custody Requirements
Identified that key generation, rotation, and revocation must reside strictly on-premises in enterprise hardware under direct physical control.
Regulatory compliance mandates that root keys cannot be delegated to or held by the cloud provider.
2
Evaluate Cryptographic Performance Requirements
Selected symmetric encryption (e.g., AES-256) for bulk payload processing.
Symmetric algorithms provide high-throughput processing necessary for multi-terabyte archive ingestion.
3
Select Storage Architecture Envelope (Envelope Encryption)
Configured local HSM to manage root Key Encryption Keys (KEKs) that wrap short-lived Data Encryption Keys (DEKs).
Envelope encryption separates data payload encryption from key governance, providing scalability and strict on-premises key control.

Key Concept

Data Encryption at Rest and Key Management Architecture (Envelope Encryption & HSM)
Question 173Question

An organization is configuring a shared Linux host operating system to execute unmanaged containerized microservices for multiple untrusted third parties. The security team must minimize the attack surface of the shared host kernel and prevent one tenant's containerized process from inspecting or interacting with processes of another tenant. Which TWO of the following mechanisms directly accomplish these security goals?

Select all that apply

Show answer & explanation

Answer: Configure Linux kernel namespaces to restrict process IDs, mount points, and network interface visibility between container environments.; Implement custom seccomp (secure computing mode) filters to restrict the set of system calls available to running container processes.

Answer

The correct mechanisms are configuring Linux kernel namespaces to restrict process IDs, mount points, and network interface visibility, and implementing custom seccomp filters to restrict system calls executed on the host kernel.
Configuring Linux kernel namespaces isolates process IDs, network stacks, and mount points across containers so tenant workloads cannot view each other's environments. Applying seccomp profiles restricts the syscalls container processes can make to the host kernel, preventing malicious or unneeded syscalls from compromising the host operating system.

Step-by-Step Solution

1
Evaluate the requirement for process and resource visibility separation between containerized tenant environments.
Linux kernel namespaces partition kernel resources so that one container process cannot view or access the processes, network interfaces, or filesystem mounts of another container.
Namespaces establish the core process and visibility isolation boundaries for containers on a shared kernel.
2
Evaluate the requirement for host kernel attack surface reduction against malicious process calls.
Seccomp (secure computing mode) profiles intercept and block arbitrary or risky system calls before they reach the host kernel.
Restricting system calls reduces the potential vector for container escape exploits targeting host kernel vulnerabilities.
3
Identify misconceptions regarding container filesystem controls and network perimeters.
Read-only image layers do not provide hypervisor-like hardware ring isolation, and perimeter firewalls cannot prevent host-local privilege escalations.
Hardware isolation requires hypervisors (VMs), while local kernel exploits bypass network edge firewalls.

Key Concept

Kernel Namespaces and Seccomp Profiles for Container Host Hardening
Question 174Question

Match each virtualization and containerization security mechanism on the left with its primary operational function on the right.

Click a left item, then click its matching right item

Items

Type 1 Hypervisor
Linux Namespaces
Control Groups (cgroups)
Container Microsegmentation

Matches

Show answer & explanation

Answer

Type 1 Hypervisor pairs with bare-metal hardware virtual machine management; Linux Namespaces pairs with process visibility isolation; Control Groups (cgroups) pairs with resource allocation restrictions; Container Microsegmentation pairs with granular container network traffic policy enforcement.
Each security mechanism is accurately matched to its design purpose: Type 1 Hypervisors manage bare-metal VM isolation, Linux Namespaces restrict container visibility, Control Groups enforce resource limits, and Microsegmentation secures container-to-container network communication.

Step-by-Step Solution

1
Differentiate between hypervisor virtualization and container OS-level isolation.
Identify Type 1 Hypervisor as bare-metal hardware abstraction for VMs.
Bare-metal hypervisors manage virtual machines directly on hardware without relying on a general-purpose host OS.
2
Distinguish between Linux kernel features used for container isolation.
Associate Linux Namespaces with resource visibility and Control Groups (cgroups) with resource limitations.
Namespaces control what a container can see (PIDs, mounts, networking), while cgroups control how much compute capacity a container can consume.
3
Identify network-layer isolation specific to microservice environments.
Link Container Microsegmentation to fine-grained network access controls.
Microsegmentation prevents unauthorized lateral movement by isolating network flows between specific workloads.

Key Concept

Virtualization and Container Isolation Controls
Question 175Question

A security architect is designing a high-availability infrastructure across two geographically separated cloud regions for a critical financial transactions platform. The business impact analysis specifies a Recovery Point Objective (RPORPO) of near-zero (RPO<1 secondRPO < 1\text{ second}) and a Recovery Time Objective (RTORTO) of less than 30 seconds30\text{ seconds}. The design must prevent split-brain condition states during network partitions and ensure continuous operation during full regional outage scenarios. Which TWO of the following architecture controls or configurations must be combined to meet these strict availability, consistency, and resilience requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Synchronous database replication across active regions coupled with a quorum-based witness server deployed in an independent third availability zone; Global server load balancing (GSLB) with health probes for dynamic traffic redirection and low Time-To-Live (TTL) DNS failover records

Answer

The architecture requires synchronous database replication with a third-zone quorum witness alongside Global Server Load Balancing (GSLB) with automated health probes and low DNS TTL records.
Achieving a near-zero RPO and sub-minute RTO across dual regions requires synchronous database replication with a third-zone quorum witness to prevent split-brain states, combined with Global Server Load Balancing (GSLB) and low DNS TTL for rapid automated traffic rerouting.

Step-by-Step Solution

1
Analyze RPO requirement (RPO<1 secondRPO < 1\text{ second})
Near-zero RPO requires synchronous data replication between active nodes so transactions are committed at both sites before returning success.
Asynchronous replication can introduce latency gaps leading to data loss upon failure, whereas synchronous replication guarantees data consistency.
2
Evaluate split-brain prevention for multi-region active designs
Deploying an independent tie-breaker/witness node in a third availability zone maintains cluster consensus.
If connectivity breaks between the two primary regions, the third-party witness determines which region holds the true quorum, preventing both sites from operating independently as primary.
3
Analyze RTO requirement (RTO<30 secondsRTO < 30\text{ seconds})
Global Server Load Balancing (GSLB) with continuous health checking and short DNS TTL enables rapid automated client redirection.
Automated traffic management redirects incoming requests to healthy endpoints without waiting for manual intervention or prolonged DNS cache expiration.

Key Concept

High Availability and Multi-Site Disaster Resilience
Question 176Question

A system administrator is evaluating deployment options for an enterprise workload. Which of the following fundamental architectural characteristics distinguishes application containers from virtual machines?

Show answer & explanation

Answer: Containers share the host operating system kernel, whereas virtual machines run independent guest operating systems on top of a hypervisor.

Answer

Containers share the host operating system kernel, whereas virtual machines run independent guest operating systems on top of a hypervisor.
Containers virtualize at the operating system layer and share the host system's kernel among all container instances. In contrast, virtual machines run on a hypervisor that abstracts hardware, requiring each virtual machine to run its own complete guest operating system.

Step-by-Step Solution

1
Analyze the architectural boundary of virtual machines.
Virtual machines use a hypervisor to emulate physical hardware, allowing each guest OS to run independently with its own kernel.
Hardware virtualization provides strong isolation through separate operating system kernels.
2
Analyze the architectural boundary of application containers.
Containers package application code and dependencies while sharing the host OS kernel and utilizing kernel isolation features.
OS-level virtualization avoids the overhead of running multiple guest kernels.
3
Compare the key architectural distinction between the two models.
The primary difference is kernel sharing versus dedicated guest operating systems.
This single distinction dictates performance efficiency, resource overhead, and isolation strength.

Key Concept

Operating system kernel sharing in containerization versus hypervisor hardware virtualization
Question 177Question

An enterprise health technology organization is deploying a high-throughput centralized database storage system processing millions of protected health information (PHI) records daily. Compliance standards mandate hardware-level protection for cryptographic key management where master keys are non-exportable and tamper-resistant. Additionally, data-at-rest bulk block encryption performance overhead must be offloaded directly to dedicated disk hardware, preventing media encryption keys from residing in host operating system memory. Which of the following storage security architectures satisfies both the performance and key isolation requirements?

Show answer & explanation

Answer: Self-Encrypting Drives (SEDs) utilizing hardware-based full disk encryption managed by an enterprise Hardware Security Module (HSM) for Key Encryption Key (KEK) lifecycle operations

Answer

Self-Encrypting Drives (SEDs) utilizing hardware-based full disk encryption managed by an enterprise Hardware Security Module (HSM) for Key Encryption Key (KEK) lifecycle operations
The combination of Self-Encrypting Drives (SEDs) and a Hardware Security Module (HSM) perfectly satisfies both requirements. SEDs perform AES bulk encryption directly on the drive controller, eliminating OS memory key exposure and CPU performance overhead. The HSM provides a dedicated, tamper-resistant hardware appliance for securely generating, storing, and managing the Key Encryption Keys (KEKs) used to unlock or manage the drives.

Step-by-Step Solution

1
Analyze the performance requirement for bulk storage encryption.
Bulk encryption must be executed at the disk hardware layer without host CPU/RAM overhead or exposing media keys in OS memory, pointing directly to Self-Encrypting Drives (SEDs).
SEDs implement hardware AES circuit encryption directly on the drive controller, ensuring near-zero latency and protecting Data Encryption Keys (DEKs) inside hardware.
2
Analyze the hardware key isolation and compliance requirement.
Key Encryption Keys (KEKs) and master keys must reside in dedicated, non-exportable hardware, pointing to a Hardware Security Module (HSM).
HSMs provide FIPS 140-2/3 validated tamper-evident environments for managing top-level cryptographic keys.
3
Synthesize the combined storage security architecture.
Pairing SEDs (for hardware-offloaded bulk encryption) with an enterprise HSM (for master KEK management) fulfills all compliance and throughput criteria.
This dual-layer hardware approach meets enterprise compliance for zero host-memory key exposure and high-performance throughput.

Key Concept

Storage Security Architecture: Integrating SEDs for hardware-level bulk encryption with HSMs for key governance
Question 178Question

An enterprise security architect is establishing operational boundaries across a multi-cloud enterprise ecosystem. Match each cloud security implementation task on the left with the corresponding cloud service model on the right.

Click a left item, then click its matching right item

Items

Configuring execution timeouts, API gateway triggers, and event-driven permissions for stateless microservices without managing any OS or web server.
Applying security updates to guest operating systems, configuring virtual network firewalls, and managing persistent block storage volumes.
Enforcing enterprise data loss prevention (DLP) rules and tenant access control via API integrations for a vendor-hosted productivity suite.
Managing application source code security, database table permissions, and runtime framework configurations while the underlying OS is patched by the cloud vendor.

Matches

Show answer & explanation

Answer

Task 1 matches Function as a Service (FaaS) / Serverless; Task 2 matches Infrastructure as a Service (IaaS); Task 3 matches Software as a Service (SaaS); Task 4 matches Platform as a Service (PaaS).
Each cloud service model defines a specific division of responsibilities under the Shared Responsibility Model: IaaS delegates OS, virtual network, and storage controls to the customer; PaaS delegates application runtime and database configuration to the customer while automating OS management; SaaS limits customer responsibility to data access and identity management; FaaS abstracts all infrastructure and server runtimes, focusing strictly on stateless event execution.

Step-by-Step Solution

1
Analyze Task 1 regarding stateless execution microservices without OS or web server management.
Identified as Function as a Service (FaaS) / Serverless, where infrastructure and OS management are fully abstracted.
Serverless architectures require developers only to upload code functions and define event triggers.
2
Analyze Task 2 regarding guest OS updates, virtual firewalls, and persistent storage management.
Identified as Infrastructure as a Service (IaaS).
Under IaaS shared responsibility, the cloud provider manages physical hardware and hypervisors, whereas the customer manages guest OS, network controls, and storage encryption.
3
Analyze Task 3 regarding tenant access control and DLP integration for vendor-hosted productivity suites.
Identified as Software as a Service (SaaS).
SaaS applications are completely hosted by the cloud provider, leaving the customer only in control of data access, user identities, and data loss prevention configurations.
4
Analyze Task 4 regarding application source code, database table permissions, and runtime framework configurations with provider OS patching.
Identified as Platform as a Service (PaaS).
PaaS abstracts operating system administration while giving the customer control over application deployment, runtime configurations, and backend database schemas.

Key Concept

Cloud Shared Responsibility Model across Service Models (IaaS, PaaS, SaaS, FaaS)
Question 179Question

An organization is deploying new laptop computers to remote workers and wants to store full-disk encryption keys securely within dedicated microcontrollers soldered directly onto each computer motherboard. Which hardware security component provides this local cryptoprocessor functionality for device integrity verification and key storage?

Show answer & explanation

Answer: Trusted Platform Module (TPM)

Answer

The correct option is the Trusted Platform Module (TPM).
The Trusted Platform Module (TPM) is a secure cryptoprocessor integrated directly onto host motherboards to provide hardware-based cryptographic operations, secure storage for full-disk encryption keys, and system integrity verification through boot measurement.

Step-by-Step Solution

1
Identify the key requirement in the scenario.
The requirement calls for a motherboard-soldered microchip dedicated to storing encryption keys and attesting host integrity.
Hardware security architecture uses localized cryptoprocessors for endpoint device binding.
2
Evaluate hardware cryptoprocessor capabilities.
The Trusted Platform Module (TPM) fulfills the exact role of an endpoint motherboard-level cryptographic processor.
TPMs securely store cryptographic keys, measurements, and signatures used by full-disk encryption like BitLocker.

Key Concept

Hardware Root of Trust and Trusted Platform Module (TPM) functions
Question 180Question

Match each hardware security mechanism to its primary security function.

Click a left item, then click its matching right item

Items

Trusted Platform Module (TPM)
Hardware Security Module (HSM)
eFuse
UEFI Secure Boot

Matches

Show answer & explanation

Answer

The hardware security mechanisms match their functions as follows: Trusted Platform Module (TPM) pairs with storing host keys and measuring endpoint boot integrity; Hardware Security Module (HSM) pairs with enterprise high-throughput cryptographic processing; eFuse pairs with permanently altering physical chip states for anti-rollback protection; and UEFI Secure Boot pairs with verifying cryptographic signatures on bootloaders before execution.
Each security mechanism directly aligns with its hardware role: Trusted Platform Module (TPM) serves host endpoints by storing keys and holding hardware boot measurements; Hardware Security Module (HSM) offloads server-side cryptographic workloads; eFuse physically enforces immutable hardware states such as rollback protection; and UEFI Secure Boot verifies cryptographically signed startup binaries.

Step-by-Step Solution

1
Analyze endpoint-level cryptographic hardware controls.
Trusted Platform Module (TPM) is identified as the local microcontroller on host motherboards for key storage and measurements.
TPMs are standard endpoint chips used to protect full disk encryption keys and verify device posture.
2
Analyze enterprise-level high-performance hardware crypto appliances.
Hardware Security Module (HSM) is identified as the high-throughput server appliance.
HSMs handle centralized enterprise key management and offload heavy cryptographic operations.
3
Analyze physical hardware lock mechanisms in microchips.
eFuse is identified as the technology that permanently alters internal circuits.
Once an eFuse is blown, the physical change is irreversible, prohibiting firmware downgrades or unauthorized debug interface access.
4
Analyze firmware startup signature verification mechanisms.
UEFI Secure Boot is identified as the process checking boot code signatures.
Secure Boot prevents rootkits by verifying digital signatures against known trust anchors before code executes.

Key Concept

Hardware-based root of trust components and embedded system security controls
Estimated Time:1m 0s
PreviousPage 9 / 21Next
Security Architecture Practice Questions — CompTIA Security+ — Page 9 | Examkin