Security Architecture

405 questions

Question 241Question

An aerospace engineering organization has implemented Zero Trust Architecture (ZTA) controls for engineers accessing proprietary CAD schematics stored in a hybrid cloud repository. During an active remote session from a corporate laptop, the security monitoring system detects that the local endpoint protection agent was disabled and the asset's dynamic risk score surged. Although the engineer successfully completed multi-factor authentication (MFA) at session initiation, access to the repository is revoked instantly. Which Zero Trust Architecture core principle is directly demonstrated by this access enforcement action?

Show answer & explanation

Answer: Continuous verification and dynamic risk assessment throughout the session lifecycle

Answer

Continuous verification and dynamic risk assessment throughout the session lifecycle
The scenario demonstrates immediate access termination when a client device's security posture degrades mid-session. Under Zero Trust Architecture principles, explicit verification must occur continuously rather than once at initial authentication. Policy Decision Points (PDPs) evaluate real-time contextual signals—such as endpoint health, user risk score, and system compliance—to adjust or revoke access dynamically throughout the connection lifecycle.

Step-by-Step Solution

1
Analyze the access control trigger and response described in the scenario.
Access was granted following MFA, but was dynamically terminated mid-session due to host security posture degradation (disabled protection agent and spiked risk score).
Understanding why access was altered mid-session identifies the specific operational policy logic.
2
Evaluate the action against Zero Trust Architecture principles.
Zero Trust dictates that authentication and authorization are never static events; Policy Decision Points (PDPs) must continuously re-evaluate sessions using dynamic context and real-time security signals.
This contrasts with legacy security architectures that assume trusted status after initial authentication.
3
Select the option that accurately describes this architectural behavior.
The concept of continuous verification and dynamic risk assessment throughout the session lifecycle correctly describes immediate revocation upon host posture decay.
It explicitly captures the core ZTA tenet of continuous re-assessment without relying on implicit, persistent session trust.

Key Concept

Continuous Verification and Dynamic Context-Based Access Control
Estimated Time:1m 30s
Question 242Question

A system administrator is upgrading a mission-critical server to eliminate single points of failure. The server hardware is equipped with dual hot-swappable power supply units. To ensure continuous operation even if a primary utility feed fails, which of the following configuration controls should the administrator implement?

Show answer & explanation

Answer: Connect each power supply unit to an independent power circuit fed by a separate Uninterruptible Power Supply (UPS).

Answer

Connecting each power supply unit to an independent power circuit fed by a separate Uninterruptible Power Supply (UPS).
Connecting dual hot-swappable power supplies to independent electrical circuits and separate UPS units eliminates single points of failure at the power layer. If one power source or supply fails, the remaining supply maintains system power without causing downtime.

Step-by-Step Solution

1
Identify the potential single point of failure described in the scenario.
The risk is an electrical power circuit or power supply failure affecting server uptime.
Dual power supply units are present, but if both are plugged into the same power distribution source, an outage on that circuit will cause total downtime.
2
Evaluate hardware fault tolerance mechanisms for power infrastructure.
Connecting each PSU to distinct electrical circuits backed by independent UPS units guarantees redundant power paths.
If one circuit or UPS fails, the second PSU continues drawing power seamlessly without interruption.

Key Concept

Power Infrastructure Redundancy and Fault Tolerance
Estimated Time:1m 0s
Question 243Question

A senior security architect is auditing an enterprise data center infrastructure to eliminate single points of failure (SPOFs) and ensure compliance with strict uptime service level agreements (SLAs). Match each hardware or operational redundancy mechanism to its corresponding technical implementation objective.

Click a left item, then click its matching right item

Items

Multipathing (MPIO)
Dual Power Supplies with Independent PDU Feeds
NIC Teaming (802.3ad LACP)
Asynchronous Multi-Site Storage Replication

Matches

Show answer & explanation

Answer

Multipathing (MPIO) matches maintaining redundant block-level I/O paths between host HBAs and SAN storage; Dual Power Supplies with Independent PDU Feeds matches mitigating electrical breaker trips and rack-level PDU disruptions; NIC Teaming (802.3ad LACP) matches aggregating physical Ethernet interfaces for Layer 2 failover; Asynchronous Multi-Site Storage Replication matches regional disaster protection over WAN links with non-zero RPO.
Each architectural control fulfills a distinct redundancy layer (storage I/O, electrical infrastructure, network interface aggregation, or disaster recovery site replication) without overlapping scope.

Step-by-Step Solution

1
Analyze storage path redundancy requirements.
Multipathing (MPIO) provides host-to-SAN fault tolerance across redundant controllers and Fibre Channel/iSCSI paths.
MPIO operates at the block storage driver layer rather than standard network link aggregation.
2
Evaluate electrical fault tolerance controls.
Dual power supplies plugged into separate PDUs isolate electrical component failures.
Decoupling electrical circuits guarantees continuous host operation if a circuit or PDU encounters a fault.
3
Examine network link-layer resilience mechanisms.
NIC Teaming (802.3ad LACP) binds interface cards for switch port failover and link load distribution.
LACP aggregates physical Ethernet links to eliminate single cable or port failures.
4
Determine geographic site replication parameters.
Asynchronous replication allows multi-site protection across long distances without application latency degradation.
Because network latency over WAN prohibits zero-RPO synchronous commits, asynchronous transfer allows local writes to complete immediately.

Key Concept

Infrastructure Resilience and Redundancy Controls
Question 244Question

An defense contractor is engineering autonomous marine surveying submersibles deployed in untrusted oceanic regions. The vehicle onboard processing unit must generate device-unique cryptographic keys for encrypting collected telemetry. To resist sophisticated physical tamper attacks—such as silicon chip decapsulation, focused ion beam microprobing, and non-volatile memory readout if a submersible is captured—the keying material must not exist as stored digital bits anywhere on physical media when powered off. Which hardware security technology should be implemented to meet this requirement?

Show answer & explanation

Answer: A Physically Unclonable Function (PUF) embedded within the system-on-chip silicon

Answer

A Physically Unclonable Function (PUF) embedded within the system-on-chip silicon
A Physically Unclonable Function (PUF) leverages microscopic physical variations inherent in semiconductor manufacturing to generate unique cryptographic keys on demand. Because the key is derived dynamically from physical silicon properties rather than stored as persistent binary data in non-volatile memory, an attacker cannot extract key material even when performing physical chip decapsulation or direct microprobing.

Step-by-Step Solution

1
Analyze the threat model and physical constraints presented in the scenario.
The device operates autonomously without network access and faces physical capture, including physical silicon decapsulation and microprobing threats.
Understanding the physical attack vector dictates whether logical, discrete, or silicon-level key generation controls are required.
2
Evaluate key storage mechanics across candidate hardware components.
TPMs, TEEs, and standard non-volatile storage rely on persistent binary representations of keys, whereas a PUF derives keys dynamically from silicon manufacturing variations.
If keys are never stored as binary states in flash memory, physical memory extraction and decapsulation attacks cannot yield the key material.
3
Select the hardware mechanism that satisfies both offline operation and anti-decapsulation physical security.
The Physically Unclonable Function (PUF) fulfills all physical anti-tamper and dynamic key generation requirements.
PUF acts as a digital fingerprint of the silicon chip, synthesizing cryptographic keys only during runtime.

Key Concept

Physically Unclonable Functions (PUF) and Hardware Root of Trust Anti-Tamper Mechanisms
Estimated Time:2m 0s
Question 245Question

An enterprise automated distribution center utilizes networked Industrial Internet of Things (IIoT) controllers for material handling equipment. The security architecture team must enable the corporate enterprise resource planning (ERP) platform to exchange telemetry and commands with the IIoT controllers while preventing compromised IIoT devices from traversing laterally into corporate endpoints. Which of the following network design controls should the security team implement? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Place IIoT controllers into a dedicated microsegmented network zone governed by strict East-West access control policies.; Deploy an inline Next-Generation Firewall (NGFW) performing stateful protocol inspection between the corporate ERP network and the IIoT zone.

Answer

The security team should implement dedicated microsegmentation for IIoT devices with East-West access policies, and deploy an inline Next-Generation Firewall (NGFW) performing stateful protocol inspection between the corporate ERP network and the IIoT zone.
Placing IIoT controllers into a microsegmented zone enforces strict East-West control policies, preventing unauthorized lateral movement if one device is breached. Deploying an inline Next-Generation Firewall (NGFW) between the corporate ERP network and the IIoT zone ensures rigorous stateful North-South inspection and protocol filtering across boundary zones.

Step-by-Step Solution

1
Identify the primary traffic flows and risks
North-South traffic flows between ERP and IIoT; East-West traffic flows between individual IIoT controllers.
Isolation requires distinct controls for lateral movement and zone-boundary transit.
2
Select intra-zone isolation mechanism
Microsegmentation with granular access control policies.
Prevents compromised IIoT endpoints from pivoting to neighboring controllers.
3
Select inter-zone perimeter enforcement mechanism
Inline Next-Generation Firewall (NGFW) with deep packet inspection.
Ensures stateful inspection and validation of telemetry/command protocols traversing between corporate and IIoT zones.

Key Concept

Secure Network Design and Microsegmentation
Question 246Question

A university is expanding its online video streaming platform by establishing a hybrid cloud architecture. The IT security team deploys virtual machines within a public cloud Infrastructure as a Service (IaaS) tenant to handle high-throughput video transcoding workloads, while maintaining student academic records within an on-premises datacenter. Which of the following operational security responsibilities fall solely on the university's internal security team for the public cloud IaaS components? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Configuring guest operating system network firewalls and installing OS-level security patches; Defining access control policies and identity permissions for video data storage buckets and application users

Answer

The university's internal security team is solely responsible for configuring guest operating system firewalls and applying OS patches, as well as managing access control policies for application data and identity permissions.
In Infrastructure as a Service (IaaS), the cloud provider manages the physical infrastructure, facility security, hardware, and hypervisor layer. The customer retains full responsibility for managing the guest operating systems (including OS firewall rules and patch management) and defining access control and identity permissions for data assets stored within the cloud environment.

Step-by-Step Solution

1
Analyze the cloud service model referenced in the scenario.
The infrastructure uses Infrastructure as a Service (IaaS).
Determining the service model establishes the baseline division of duties in the Shared Responsibility Model.
2
Delineate customer responsibilities from cloud service provider (CSP) responsibilities in IaaS.
The CSP manages physical facility security, host hardware, and the hypervisor layer. The customer manages guest OS, middleware, runtime applications, network security controls on the VM, and data access policies.
IaaS leaves all operating system management and data protection under the customer's operational scope.
3
Identify the two options matching the customer's operational scope.
Guest OS firewalling/patching and data/identity access control policy configuration are customer duties.
These activities align directly with customer-owned layers in IaaS architecture.

Key Concept

Cloud Shared Responsibility Model in IaaS Environments
Question 247Question

A biomedical research enterprise is migrating its hybrid cloud infrastructure to align with Zero Trust Architecture (ZTA) principles to protect sensitive patient records and proprietary research data. Which of the following architectural strategies MUST the security engineering team implement to strictly enforce Zero Trust principles? (Select TWO).

Select all that apply

Show answer & explanation

Answer: Implement continuous, risk-based session evaluation at the Policy Decision Point (PDP) that dynamically reassesses access grants based on endpoint telemetry and user behavior.; Enforce microsegmentation around individual workload components so that all lateral east-west network traffic is explicitly authenticated, authorized, and encrypted.

Answer

The correct architectural strategies are implementing continuous, risk-based session evaluation at the Policy Decision Point (PDP) using dynamic telemetry, and enforcing microsegmentation around individual workload components so that all lateral east-west traffic is explicitly authenticated, authorized, and encrypted.
Zero Trust Architecture requires continuous explicit verification and strict resource isolation. Implementing dynamic telemetry checks at the Policy Decision Point (PDP) ensures access grants are re-evaluated continuously against current risk state. Enforcing microsegmentation prevents lateral attacker movement by inspecting and authorizing all internal east-west traffic regardless of network location.

Step-by-Step Solution

1
Evaluate Zero Trust core tenets regarding continuous verification and dynamic access control.
Dynamic policy evaluation at the Policy Decision Point (PDP) ensures access permissions dynamically adapt to changes in device posture, threat intelligence, and user risk metrics.
Static initial logins are insufficient; continuous posture and risk assessment are required under Zero Trust principles.
2
Analyze network isolation and segmentation requirements under an assumed breach posture.
Microsegmentation restricts lateral movement by requiring explicit authorization and encryption for all internal workloads, treating all east-west network traffic as un-trusted.
Perimeter defenses and legacy VPNs grant implicit trust once inside, which contradicts Zero Trust requirements.

Key Concept

Zero Trust Architecture Principles: Continuous Verification, Microsegmentation, and Explicit Access Controls
Question 248Question

A system administrator is configuring isolation controls on a host operating system running multiple production application containers. Which of the following security mechanisms directly restrict containerized processes from escalating privileges on the host kernel and limiting system calls? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Configuring Secure Computing Mode (seccomp) profiles for container runtime environments; Enabling user namespaces to map container root users to non-root host accounts

Answer

The correct mechanisms are configuring Secure Computing Mode (seccomp) profiles and enabling user namespaces.
Seccomp restricts the syscall boundary exposed by the host kernel to containerized workloads, while user namespaces isolate administrative privileges by ensuring a container's root user does not map to root authority on the underlying host operating system.

Step-by-Step Solution

1
Analyze container kernel isolation requirements
Identify controls that limit kernel attack surfaces and host account exposure.
Containers share the underlying host OS kernel, making system call filtering critical.
2
Evaluate system call restriction mechanisms
Seccomp profiles restrict syscall access per container process.
Restricting syscalls prevents compromised containers from executing dangerous kernel routines.
3
Evaluate identity and privilege boundary controls
User namespaces map container UID 0 (root) to an unprivileged host UID.
This prevents container escapes from granting root privileges on the underlying host machine.

Key Concept

Container Host Isolation and Kernel Hardening Mechanisms
Question 249Question

An organization is updating its high-availability and resilience architecture for a critical enterprise resource planning (ERP) system. A system administrator proposes replacing off-site asynchronous data backups with a local RAID 10 storage configuration, arguing that RAID 10 provides both fault tolerance and complete disaster recovery resilience. Which of the following best explains the fundamental vulnerability created by this proposed change?

Show answer & explanation

Answer: RAID 10 provides localized hardware fault tolerance against drive failure but does not protect against catastrophic site loss, data corruption, or physical disasters.

Answer

RAID 10 provides localized hardware fault tolerance against drive failure but does not protect against catastrophic site loss, data corruption, or physical disasters.
The correct answer highlights that while RAID 10 offers excellent fault tolerance by mirroring and striping disks locally, it is not a disaster recovery mechanism. If the data center experiences a physical disaster, or if data is deleted or encrypted by ransomware, RAID mirrors those destructive changes immediately across all drives. Off-site backups or replication remain mandatory for disaster recovery.

Step-by-Step Solution

1
Analyze the proposed architectural modification.
The proposal substitutes off-site data backups with local RAID 10 storage arrays.
Disaster recovery planning requires evaluating whether local redundant storage can compensate for site-level backup strategies.
2
Evaluate the technical capabilities of RAID 10.
RAID 10 combines disk mirroring and striping, allowing array survival during individual disk failures without operational downtime.
RAID provides localized hardware fault tolerance and high availability for storage media.
3
Identify boundary limitations of RAID 10 compared to backups.
RAID 10 instantly mirrors logical corruptions, malicious deletions, and ransomware encryption across mirrored pairs, and remains vulnerable to complete facility destruction.
Fault tolerance mechanisms sustain operational continuity through component failures, whereas backups and off-site replication facilitate disaster recovery following site loss or data corruption.

Key Concept

Distinguishing Fault Tolerance from Disaster Recovery and Backups
Question 250Question

A security architect is establishing physical and firmware-level hardening controls for an industrial IoT edge gateway deployed in physically accessible utility substations. Which option correctly matches each embedded hardware security control to its primary operational security role?

Click a left item, then click its matching right item

Items

Microcontroller Memory Protection Unit (MPU)
Immutable Mask ROM Bootloader
Tamper-Resistant Secure Element (SE)
Inline Bus Encryption Engine

Matches

Show answer & explanation

Answer

Microcontroller Memory Protection Unit (MPU) matches restricting task memory and peripheral access by privilege level; Immutable Mask ROM Bootloader matches serving as the unalterable Hardware Root of Trust for initial boot validation; Tamper-Resistant Secure Element (SE) matches providing hardened cryptographic storage resistant to physical/side-channel extraction; Inline Bus Encryption Engine matches protecting external memory interconnects against physical bus probing.
Each component is mapped to its core architectural security scope: the MPU isolates software privilege levels and memory space; the Immutable Mask ROM forms the immutable Root of Trust for booting; the Secure Element safeguards cryptographic keys against physical tamper; and the Inline Bus Encryption Engine secures physical hardware interconnects against logic analyzer capture.

Step-by-Step Solution

1
Analyze the hardware protection layer enforced at the microcontroller CPU execution level.
Identify that the Memory Protection Unit (MPU) isolates memory regions and peripherals based on task privilege levels.
MPUs define access permissions for specific memory segments to prevent non-privileged tasks from modifying core hardware configuration.
2
Identify the foundation of the boot signature verification chain.
Map the Immutable Mask ROM Bootloader to the initial Hardware Root of Trust.
Because mask ROM cannot be altered post-fabrication, it guarantees that the initial boot execution vector cannot be corrupted or bypassed.
3
Evaluate key storage mechanisms resilient against physical attack vectors.
Associate the Tamper-Resistant Secure Element (SE) with side-channel resistant cryptographic key operations.
Secure Elements incorporate active shields and power-glitch protection specifically to counter physical hardware extraction techniques.
4
Evaluate memory interconnect defenses for off-chip communication paths.
Match the Inline Bus Encryption Engine to protecting external memory buses against physical probing.
Unencrypted buses between system-on-chip controllers and external memory are vulnerable to logic analyzers; inline bus encryption encrypts data over these physical traces.

Key Concept

Hardware-based security mechanisms provide distinct operational guarantees across processing privilege isolation, boot sequence verification, key protection against physical attacks, and memory bus confidentiality.
Question 251Question

Match each storage security technology to its primary operational application within an enterprise architecture.

Click a left item, then click its matching right item

Items

Self-Encrypting Drive (SED)
Data Loss Prevention (DLP)
Hardware Security Module (HSM)
Tokenization

Matches

Show answer & explanation

Answer

The correct pairings match Self-Encrypting Drive (SED) to hardware-level disk encryption; Data Loss Prevention (DLP) to data monitoring and exfiltration prevention; Hardware Security Module (HSM) to key generation and secure key storage; and Tokenization to replacing sensitive data fields with non-sensitive placeholder values.
Each technology is correctly paired with its core operational capability. Self-Encrypting Drives deliver controller-based disk encryption, Data Loss Prevention mitigates unauthorized data exfiltration, Hardware Security Modules protect cryptographic keys and perform high-assurance crypto operations, and Tokenization substitutes sensitive data fields with non-sensitive tokens using a secure vault.

Step-by-Step Solution

1
Evaluate Self-Encrypting Drive (SED)
Identified as disk controller hardware-level bulk encryption.
SED operates transparently on disk controller hardware without requiring host CPU cycles.
2
Evaluate Data Loss Prevention (DLP)
Identified as a content monitoring and exfiltration enforcement system.
DLP inspects structured and unstructured data to detect and prevent unauthorized policy violations.
3
Evaluate Hardware Security Module (HSM)
Identified as a dedicated tamper-resistant cryptographic appliance.
HSMs store master keys and perform cryptoprocessing inside a secure physical boundary.
4
Evaluate Tokenization
Identified as a data substitution method using non-sensitive placeholders.
Tokenization maps sensitive database values to surrogate tokens via a database vault rather than mathematical encryption algorithms.

Key Concept

Data Protection and Storage Security Architecture Controls
Question 252Question

A global audit firm is implementing a Zero Trust Architecture (ZTA) for partner consultants accessing sensitive financial databases. During an active user session, real-time endpoint telemetry reports that a consultant's laptop has disabled its endpoint detection agent and initiated access from an unrecognized IP address, despite having passed initial Multi-Factor Authentication (MFA). Which of the following architectural responses best exemplifies core Zero Trust principles in this scenario?

Show answer & explanation

Answer: Instruct the Policy Decision Point (PDP) to dynamically re-evaluate the session trust score and signal the Policy Enforcement Point (PEP) to terminate or restrict access immediately.

Answer

Instruct the Policy Decision Point (PDP) to dynamically re-evaluate the session trust score and signal the Policy Enforcement Point (PEP) to terminate or restrict access immediately.
Under Zero Trust Architecture, access is never implicitly granted or maintained based solely on initial authentication. When risk signals change (such as disabled security agents or context anomalies), the Policy Decision Point (PDP) dynamically re-evaluates trust and directs the Policy Enforcement Point (PEP) to restrict or terminate access in real time.

Step-by-Step Solution

1
Analyze the scenario metrics and threat posture change during an active session.
The device posture degraded (EDR agent disabled) and context changed unexpectedly (unrecognized IP address).
Zero Trust assumes breach and requires continuous inspection rather than static, one-time authentication.
2
Determine the required Zero Trust Architecture component interaction.
The PDP processes real-time telemetry to update the dynamic trust score, and the PEP enforces the updated policy decision by immediately restricting or terminating access.
ZTA relies on dynamic control plane decisions to enforce granular access state changes in real time.

Key Concept

Continuous Verification and Dynamic Policy Enforcement in Zero Trust Architecture
Estimated Time:2m 0s
Question 253Question

An organization wants to enable its employees to access an external web-based software application using their existing internal network credentials without prompting them to re-enter their passwords. Which of the following identity architecture technologies best satisfies this requirement?

Show answer & explanation

Answer: Federated Single Sign-On using Security Assertion Markup Language (SAML)

Answer

Federated Single Sign-On using Security Assertion Markup Language (SAML)
Federated Single Sign-On (SSO) using SAML (Security Assertion Markup Language) allows an organization's Identity Provider (IdP) to authenticate users locally and pass secure tokens to an external Service Provider (SP). This eliminates the need for users to re-enter credentials when accessing third-party software.

Step-by-Step Solution

1
Analyze the scenario requirement
The requirement asks for a solution allowing internal corporate credentials to authenticate access to an external third-party application without multiple password prompts.
This requires a federated identity architecture that establishes trust between an internal Identity Provider (IdP) and an external Service Provider (SP).
2
Evaluate potential IAM protocols and technologies
SAML is standard for browser-based federated single sign-on between enterprise identity stores and cloud services.
SAML tokens securely transmit authentication assertions between the enterprise and the application.

Key Concept

Federated Identity Management and Single Sign-On (SSO)
Question 254Question

An organization is configuring a geographically separated secondary data center to maintain continuous operations for its mission-critical transactional database. The business requirement dictates a Recovery Point Objective (RPO) of zero and automatic failover without human intervention in the event of an site outage. Which of the following technical design choices and infrastructure components must be implemented to fulfill these specific requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Synchronous database replication across both sites; Dynamic Global Server Load Balancing (GSLB) with automated health probes and low TTL DNS records

Answer

The necessary technical controls are synchronous database replication and dynamic Global Server Load Balancing (GSLB) with automated health probes.
To achieve RPO = 0, data must be written simultaneously to both locations via synchronous replication. To achieve automated failover, GSLB with continuous health checks automatically updates routing paths when the primary endpoint fails to respond.

Step-by-Step Solution

1
Analyze RPO requirements
An RPO of zero requires synchronous replication so that transactions are committed simultaneously at both sites without data lag.
Asynchronous methods incur latency gaps resulting in lost data during an unannounced failure.
2
Analyze automated failover requirements
Automated failover requires GSLB with health monitoring to dynamically detect primary site degradation and redirect user traffic seamlessly.
Manual DNS playbooks introduce human delay and extend recovery time beyond high availability bounds.

Key Concept

High Availability and Active-Active Site Replication
Question 255Question

A security architect is designing an enterprise deployment strategy incorporating both virtual machines and application containers. Match each architectural isolation mechanism on the left with its corresponding security function or boundary property on the right.

Click a left item, then click its matching right item

Items

Control Groups (cgroups)
Linux Namespaces
Type 1 Hypervisor
Secure Computing Mode (seccomp)

Matches

Show answer & explanation

Answer

Control Groups (cgroups) matches with hardware resource limiting; Linux Namespaces matches with resource visibility partitioning; Type 1 Hypervisor matches with direct bare-metal hardware abstraction; Secure Computing Mode (seccomp) matches with syscall filtering.
Control Groups (cgroups) enforce resource allocation limits; Linux Namespaces enforce logical visibility boundaries; Type 1 Hypervisors provide bare-metal hardware abstraction; and Secure Computing Mode (seccomp) restricts kernel system call access.

Step-by-Step Solution

1
Analyze container resource governance mechanisms.
Control Groups (cgroups) regulate compute, memory, and storage bandwidth limits per container process group.
cgroups prevent resource exhaustion and noisy neighbor issues.
2
Analyze container visibility isolation controls.
Linux Namespaces segment global system resources (process trees, network devices, filesystem mount points) into isolated process environments.
Namespaces ensure one container cannot see or interact directly with another container's processes or file mounts.
3
Evaluate hypervisor virtualization architectures.
A Type 1 hypervisor operates directly on raw host hardware, enforcing strong VM boundary separation at the virtual CPU and memory abstraction level.
Type 1 hypervisors eliminate host OS vulnerability exposure present in Type 2 virtualization.
4
Identify kernel surface attack reduction controls.
Seccomp restricts the system call interface exposed by the host kernel to running container processes.
Filtering unused or dangerous syscalls reduces container escape vulnerabilities.

Key Concept

Virtualization and Containerization Isolation Mechanisms
Question 256Question

An enterprise network security architect is updating the organization's network architecture to enhance isolation and access control. Match each network design or segmentation technique on the left with its corresponding enterprise implementation requirement on the right.

Click a left item, then click its matching right item

Items

Air Gap
Microsegmentation
Jump Box
Screened Subnet

Matches

Show answer & explanation

Answer

Air Gap pairs with physical separation from all networks; Microsegmentation pairs with software-defined lateral policy enforcement; Jump Box pairs with a secure, audited administrative access gateway; Screened Subnet pairs with isolating public-facing services between security boundaries.
The concepts correctly align with their standard technical definitions: Air Gaps mandate complete physical isolation; Microsegmentation restricts East-West lateral traffic at the workload level via software policies; Jump Boxes act as secure intermediate administrative access points; and Screened Subnets isolate public-facing assets between perimeter firewalls.

Step-by-Step Solution

1
Identify absolute isolation without network medium connectivity.
Air Gap corresponds to complete physical network disconnection.
Air-gapping ensures no data can cross network media electronically.
2
Determine granular lateral traffic controls in virtualized environments.
Microsegmentation corresponds to controlling East-West traffic between individual workloads.
Microsegmentation operates at fine granularity using software-defined security policies.
3
Locate administrative transit control requirements.
Jump Box corresponds to the intermediate secure gateway for administration.
Jump hosts centralize management authentication and session auditing.
4
Evaluate perimeter placement for externally exposed services.
Screened Subnet corresponds to placing public-facing services between security boundaries.
Screened subnets shield private internal resources from untrusted internet ingress.

Key Concept

Secure Network Segmentation Archetypes
Question 257Question

An organization is modernizing its identity and access management (IAM) architecture to support modern web applications and API access controls. Which of the following protocols should the security team implement to provide federated user identity authentication and delegated API authorization? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: OpenID Connect (OIDC); OAuth 2.0

Answer

The correct open standards are OpenID Connect (OIDC) for identity authentication and OAuth 2.0 for API authorization.
OpenID Connect (OIDC) and OAuth 2.0 work together in modern identity architectures. OIDC provides user authentication by returning an ID token, while OAuth 2.0 handles authorization by granting access tokens for API requests.

Step-by-Step Solution

1
Identify the standard required for user authentication in web and federated architectures.
OpenID Connect (OIDC) extends OAuth 2.0 by introducing JSON Web Tokens (JWTs) called ID tokens to verify user identity.
OIDC is designed specifically as the authentication protocol layer.
2
Identify the framework required for delegated API authorization.
OAuth 2.0 issues access tokens that grant applications permission to access protected APIs without sharing passwords.
OAuth 2.0 governs access control and authorization decisions.

Key Concept

Federated Authentication and API Authorization Protocols
Question 258Question

An energy company is deploying smart grid Remote Terminal Units (RTUs) in unmonitored utility field enclosures. During a physical security assessment, penetration testers attached high-speed logic analyzers to the exposed printed circuit board (PCB) traces connecting the microcontroller to external system RAM, successfully intercepting plaintext cryptographic keys transmitted across the bus during normal runtime operations. Which of the following hardware security controls should the security architect specify to mitigate this vulnerability?

Show answer & explanation

Answer: Bus encryption

Answer

Bus encryption dynamically encrypts data in transit over physical memory buses between processing units and external RAM, preventing attackers with physical probing tools from intercepting cleartext key material.
Bus encryption (such as inline memory encryption) continuously encrypts data and address lines between the processor and RAM using hardware-based cryptographic engines. This prevents physical side-channel and bus-sniffing attacks from capturing sensitive data or keys from exposed circuit traces.

Step-by-Step Solution

1
Analyze the threat vector described in the deployment scenario.
The attack involves physical probe attachment (logic analyzers) to printed circuit board (PCB) traces between the main microcontroller and external system RAM to capture cleartext data in transit.
Identifying the specific physical attack vector narrows down the required hardware-level security control.
2
Evaluate candidate hardware security mechanisms against physical bus sniffing.
Bus encryption (inline memory encryption) uses hardware engines to encrypt data written to external memory and decrypt it upon read operations, rendering intercepted signals on PCB traces unreadable.
Cryptographic protection must occur at the bus layer to protect signal lines operating outside chip packaging.
3
Differentiate bus encryption from boot integrity and asymmetric signature controls.
Controls like Secure Boot and asymmetric code signing ensure firmware integrity at launch, but do not provide runtime confidentiality across hardware interconnects.
Distinguishing integrity controls from runtime bus confidentiality controls confirms the correct selection.

Key Concept

Bus Encryption and Hardware Bus Protection
Question 259Question

An enterprise financial institution is designing a storage architecture for high-throughput transaction databases hosted on a Storage Area Network (SAN). Security requirements specify that bulk data at rest must be encrypted at the drive hardware level to eliminate host CPU performance degradation, and all storage keys must be centrally managed using a standardized network protocol integrated with a Hardware Security Module (HSM). Which of the following storage security solutions best meets these requirements?

Show answer & explanation

Answer: Self-Encrypting Drives (SEDs) managed via Key Management Interoperability Protocol (KMIP) connected to an enterprise HSM

Answer

Self-Encrypting Drives (SEDs) managed via Key Management Interoperability Protocol (KMIP) connected to an enterprise HSM
Self-Encrypting Drives (SEDs) utilize dedicated, on-board cryptoprocessors to encrypt and decrypt data at wire speed without burdening host system CPU cycles. Using the Key Management Interoperability Protocol (KMIP) enables seamless integration between storage hardware controllers and a dedicated enterprise Hardware Security Module (HSM) for automated key lifecycle management.

Step-by-Step Solution

1
Analyze the hardware encryption performance requirement.
Identified that performing bulk encryption directly on drive hardware (Self-Encrypting Drives) offloads cryptographic processing from host CPUs.
Software-based host encryption introduces processing latency and CPU overhead on database host servers.
2
Evaluate key management and protocol standards.
Determined that Key Management Interoperability Protocol (KMIP) provides the standardized interface required to communicate between storage controllers and a centralized Hardware Security Module (HSM).
KMIP normalizes key lifecycle management across heterogeneous enterprise storage arrays and key vaults.

Key Concept

Hardware-based storage encryption with centralized key management protocols
Estimated Time:1m 30s
Question 260Question

A cybersecurity architect for a critical infrastructure energy provider is aligning enterprise security controls with foundational Zero Trust Architecture (ZTA) principles to protect operational technology (OT) and cloud control systems. Match each Zero Trust principle on the left with its corresponding operational security implementation on the right.

Click a left item, then click its matching right item

Items

Assume Breach
Explicit Verification
Microsegmentation
Least Privilege Access

Matches

Show answer & explanation

Answer

Assume Breach pairs with enforcing mTLS encryption and inspecting all internal and external network traffic as untrusted; Explicit Verification pairs with evaluating multi-factor identity, device health, and risk signals for every request; Microsegmentation pairs with establishing isolated perimeters around individual workloads to restrict lateral movement; Least Privilege Access pairs with granting just-in-time permissions limited strictly to minimum required operations.
Each Zero Trust principle correctly aligns with its core architectural intent: Assume Breach treats internal traffic as inherently untrusted; Explicit Verification dynamically checks identity and context for every request; Microsegmentation contains threat proliferation by isolating individual workloads; and Least Privilege Access limits temporal and operational privileges to the bare minimum.

Step-by-Step Solution

1
Analyze the principle of 'Assume Breach' within Zero Trust Architecture.
Identify that assuming breach means treating internal network zones as untrusted, necessitating pervasive encryption (mTLS) and telemetry monitoring across all internal flows.
Legacy perimeter security relies on trusted internal zones, whereas Zero Trust presumes internal network segments may already harbor compromised nodes.
2
Analyze the principle of 'Explicit Verification'.
Identify that explicit verification requires continuous, multi-attribute policy evaluation (identity, device posture, location, threat context) prior to authorizing access.
Explicit verification replaces single-point-in-time authentication with dynamic, context-aware validation for every transaction.
3
Analyze the architectural concept of 'Microsegmentation'.
Identify that microsegmentation isolates workload boundaries to restrict lateral movement across network segments.
Placing fine-grained ingress and egress policy enforcement points around workloads prevents compromise propagation.
4
Analyze the principle of 'Least Privilege Access'.
Identify that least privilege access limits permissions via just-in-time elevation and tight operational scoping.
Minimizing active permissions limits potential damage if credentials or accounts are intercepted.

Key Concept

Core Zero Trust Architecture Principles and Controls
Estimated Time:2m 0s
PreviousPage 13 / 21Next