Security Architecture

405 soru

Soru 201Soru

An enterprise airport operations authority is redesigning its security architecture across operational technology (OT), cloud management, tenant infrastructure, and administrative networks. Match each network isolation and control mechanism on the left to its corresponding architectural requirement on the right.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

Unidirectional Data Diode
Microsegmentation with Host-based Enforcement
Hardened Jump Server with MFA and Session Auditing
Physical Air Gap with Media Sanitization Kiosk

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Unidirectional Data Diode pairs with outbound-only SCADA telemetry; Microsegmentation pairs with stopping East-West lateral movement between cloud microservices; Hardened Jump Server pairs with audited vendor administrative access; Physical Air Gap pairs with isolating critical runway control hardware via offline media ingestion.
Each isolation mechanism aligns with specific threat model requirements: data diodes physically enforce one-way telemetry streaming; microsegmentation controls internal lateral movement across cloud workloads; jump servers control and audit remote management access; air gaps eliminate all network-based attack vectors against critical physical control systems.

Adım Adım Çözüm

1
Evaluate hardware-enforced single-direction communication constraints.
Identify that streaming telemetry outbound while physically blocking inbound traffic requires a Unidirectional Data Diode.
Data diodes utilize physical optical transmitters and receivers that prevent electromagnetic or logical return channels.
2
Evaluate lateral communication controls for cloud workloads.
Match Microsegmentation to the requirement of limiting East-West traffic between individual containerized instances.
Traditional perimeter firewalls cannot inspect or restrict peer-to-peer traffic inside the same virtual layer 2 network segment without software-defined microsegmentation.
3
Evaluate privileged remote management architectures.
Match Hardened Jump Server with MFA and Session Auditing to third-party vendor administrative access requirements.
Jump boxes isolate external administrative sessions from internal infrastructure while recording session activity for compliance and forensics.
4
Evaluate total isolation controls for high-consequence OT infrastructure.
Match Physical Air Gap with Media Sanitization Kiosk to the safety-critical automated runway control systems.
Complete physical separation removes external connectivity attack vectors, using controlled offline kiosks as the sole ingestion path for maintenance files.

Anahtar Kavram

Network Segmentation and Isolation Architecture Controls
Tahmini Süre:2m 0s
Soru 202Soru

A logistics enterprise is migrating its fleet tracking telemetry infrastructure to a Zero Trust Architecture (ZTA). The security team is defining architecture baseline policies for API communication between edge gateway devices and core analytical microservices. Which of the following technical requirements directly align with core Zero Trust Architecture principles? (Select TWO).

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Continuously re-evaluate device security posture and request behavior for every API transaction, regardless of network location.; Enforce microsegmentation and dynamic access controls so edge devices are restricted to the minimal resources necessary for their specific function.

Cevap

The correct requirements are to continuously re-evaluate device security posture and request behavior for every API transaction regardless of network location, and to enforce microsegmentation and dynamic access controls so edge devices are restricted to the minimal resources necessary for their specific function.
Zero Trust Architecture (ZTA) eliminates implicit network perimeter trust by mandating continuous explicit verification of every transaction (evaluating security posture, location, and behavior) and applying least privilege through microsegmentation to isolate workloads and minimize blast radius.

Adım Adım Çözüm

1
Analyze core tenets of Zero Trust Architecture (ZTA).
ZTA operates under an assumed breach mindset, requiring continuous explicit verification and strict least privilege.
Traditional perimeter-based implicit trust models must be abandoned in favor of dynamic context evaluation.
2
Evaluate requirement for continuous context validation.
Every API request must be continuously authenticated and authorized based on dynamic context metrics.
Re-evaluating posture and request behavior prevents compromised endpoints from abusing persistent session trust.
3
Evaluate requirement for microsegmentation and least privilege access.
Access must be restricted granularly to only the exact microservice endpoints required for the gateway's role.
Microsegmentation prevents lateral movement across microservices if an edge device is compromised.

Anahtar Kavram

Zero Trust Architecture Principles: Continuous Explicit Verification and Microsegmentation Least Privilege
Soru 203Soru

An IT administrator needs to ensure that all data written to enterprise storage drives is automatically encrypted at the hardware level without placing an operational processing burden on the host operating system. Which of the following storage security solutions best fulfills this requirement?

Cevabı ve açıklamayı göster

Cevap: Self-Encrypting Drives (SED)

Cevap

Self-Encrypting Drives (SED)
Self-Encrypting Drives (SEDs) incorporate dedicated cryptographic hardware directly into the drive controller. This enables transparent, full-disk symmetric encryption at rest without consuming host CPU cycles or requiring operating system software configuration.

Adım Adım Çözüm

1
Identify the primary system requirement in the scenario.
The requirement calls for hardware-level encryption of bulk data at rest without consuming host OS processing resources.
Software bulk encryption relies on host CPU cycles, whereas hardware encryption offloads cryptographic tasks.
2
Evaluate storage protection mechanisms against the requirement.
Self-Encrypting Drives (SEDs) contain built-in cryptoprocessors that transparently handle symmetric encryption directly on the drive controller.
This guarantees hardware-level protection without host system latency.

Anahtar Kavram

Hardware-Based Storage Encryption and Data-at-Rest Architecture
Soru 204Soru

An industrial IoT device manufacturer is designing a field-deployed microcontroller unit that operates in physically untrusted locations. Security engineers need to prevent attackers from executing anti-rollback (firmware downgrade) attacks—where an adversary physically unsolders external flash memory and writes a cryptographically valid, but older and vulnerable, firmware image. Which of the following hardware security controls best mitigates this physical firmware downgrade vector?

Cevabı ve açıklamayı göster

Cevap: One-Time Programmable (OTP) eFuses configured to permanently increment and enforce the minimum allowable firmware security version.

Cevap

One-Time Programmable (OTP) eFuses configured to permanently increment and enforce the minimum allowable firmware security version.
One-Time Programmable (OTP) eFuses provide an immutable, hardware-level state mechanism that is permanently burned whenever a new security version is introduced. Prior to booting, the hardware Root of Trust reads the eFuse register to verify that candidate firmware matches or exceeds the minimum allowed security version. This prevents execution of older, vulnerable firmware even if an attacker physically replaces the SPI flash memory chip.

Adım Adım Çözüm

1
Analyze the attack vector specified in the scenario.
The adversary has physical access to the device, allows chip desoldering, and attempts to flash an older, cryptographically valid image to exploit fixed software vulnerabilities (anti-rollback attack).
Asymmetric signature verification alone succeeds on old legitimate firmware builds unless an irreversible hardware state maintains the revoked status of previous versions.
2
Evaluate hardware security primitives designed for non-reversible state retention.
One-Time Programmable (OTP) eFuses physically alter microscopic electrical connections on the chip when blown during firmware updates.
Because blown eFuses cannot be unburned or reset, the internal hardware Root of Trust checks candidate firmware version counters against the eFuse register before handing off execution.

Anahtar Kavram

Hardware Anti-Rollback and eFuse Revocation Mechanisms
Soru 205Soru

Match each Identity and Access Management (IAM) protocol to its primary architectural use case.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

SAML 2.0
OAuth 2.0
OpenID Connect (OIDC)
RADIUS

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

SAML 2.0 matches XML-based web SSO federation; OAuth 2.0 matches token-based authorization for API access; OpenID Connect matches the authentication identity layer built on OAuth 2.0; RADIUS matches centralized AAA network access control.
Each IAM protocol satisfies a specific architectural domain: SAML 2.0 facilitates XML web federation across organizations; OAuth 2.0 grants granular authorization tokens to APIs; OpenID Connect adds an authentication identity layer over OAuth 2.0 using JWTs; RADIUS delivers network-level AAA for VPNs and wireless infrastructure.

Adım Adım Çözüm

1
Identify the primary architectural function (Authentication vs. Authorization vs. Network AAA) for each protocol.
Categorize SAML 2.0 and OIDC as web identity/SSO authentication, OAuth 2.0 as API authorization, and RADIUS as network AAA.
IAM architecture requires matching protocols to their specific layer in the security stack.
2
Differentiate web federation standards based on message format and structure.
Associate SAML 2.0 with XML assertions and OIDC with JSON Web Tokens (JWT) extending OAuth 2.0.
SAML 2.0 is enterprise XML-focused, while OIDC modernizes web authentication over RESTful/JSON endpoints.
3
Pair RADIUS with network-level authentication mechanisms.
Connect RADIUS to 802.1X port security and VPN access control.
RADIUS is designed for infrastructure device network access control, unlike web application protocols.

Anahtar Kavram

IAM Protocol Architectural Selection
Tahmini Süre:45s
Soru 206Soru

A system administrator is auditing isolation and runtime protection controls across a enterprise infrastructure hosting both virtual machines and containerized microservices. Match each security control on the left with the specific operational threat or attack vector it directly mitigates on the right.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

Hypervisor patch management and memory isolation baselines
Linux Control Groups (cgroups) quota enforcement
Read-only root file system configuration for container runtimes
Static image scanning integrated into the CI/CD deployment pipeline

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Hypervisor patch management matches VM escape exploitation; Control Groups (cgroups) enforcement matches resource exhaustion denial-of-service; Read-only root file system configuration matches malicious file persistence; Static image scanning matches deployment of unpatched software vulnerabilities.
Each security mechanism directly addresses a distinct layer of virtualization or container architecture: hypervisor patching protects hardware abstraction boundaries; cgroups manage shared kernel resource allocation; read-only root file systems enforce immutability at runtime; and static scanning secures software components in the build pipeline.

Adım Adım Çözüm

1
Analyze virtual machine isolation mechanisms.
Identify that hypervisor patching specifically targets vulnerabilities allowing guest-to-host privilege escalation and VM escape.
Hypervisors manage hardware virtualization boundaries; failure to patch allows guest workloads to break out of hardware abstraction.
2
Differentiate container resource boundary controls from namespace isolation.
Map Linux Control Groups (cgroups) directly to resource consumption limits.
cgroups set boundaries on system resources like CPU, memory, and disk I/O, preventing neighbor starvation.
3
Evaluate container file system runtime security.
Connect read-only root file systems to preventing unauthorized file modifications and persistence.
Immutable runtime container storage prevents attackers from dropping binaries or modifying system binaries during runtime compromise.
4
Examine pre-deployment supply chain security controls.
Associate CI/CD static image scanning with identifying known vulnerabilities in container images.
Automated scanning checks container layers against vulnerability databases before code is deployed.

Anahtar Kavram

Virtualization vs Containerization Security Boundaries
Soru 207Soru

A software development firm hosts its multi-tenant build infrastructure on a high-performance Storage Area Network (SAN). During a security assessment, auditors identified two main storage architecture vulnerabilities: block-level data traffic traversing the storage fabric between compute hypervisors and storage arrays is unencrypted and subject to packet sniffing, and logical unit numbers (LUNs) can potentially be accessed by unauthorized host adapters attached to the same fabric switches. Which set of storage architecture controls most effectively mitigates both identified vulnerabilities?

Cevabı ve açıklamayı göster

Cevap: Enforce Fibre Channel Security Protocol (FC-SP) with IPsec transport encryption across the fabric, paired with hardware switch zoning and storage array LUN masking.

Cevap

Enforcing Fibre Channel Security Protocol (FC-SP) with IPsec transport encryption across the fabric, paired with hardware switch zoning and storage array LUN masking, provides comprehensive protection for both data in transit and volume segregation.
The solution requiring Fibre Channel Security Protocol (FC-SP) with IPsec transport encryption across the fabric, paired with hardware switch zoning and storage array LUN masking, directly addresses both security gaps. FC-SP and IPsec encrypt block-level SAN traffic in transit across the storage network, neutralizing passive sniffing attacks. Hardware zoning on SAN switches isolates HBA port communications, and array-level LUN masking restricts logical volume visibility exclusively to authorized initiator World Wide Names (WWNs) or iSCSI Qualified Names (IQNs).

Adım Adım Çözüm

1
Analyze data-in-transit security requirements for SAN storage traffic.
Unencrypted block-level storage traffic across Fibre Channel or IP-based SANs requires transport layer encryption such as FC-SP or IPsec to prevent network sniffing.
Encryption at the fabric layer protects raw block communications between hypervisor initiators and array targets.
2
Analyze volume access isolation requirements at the storage layer.
Restricting volume access to authorized host bus adapters (HBAs) requires a combination of network-layer switch zoning and storage-layer LUN masking.
Zoning controls fabric switch communication paths, while LUN masking ensures only designated initiator WWNs/IQNs can mount specific storage volumes.
3
Synthesize the controls into a unified storage security architecture.
Combining FC-SP/IPsec with zoning and LUN masking directly resolves both fabric sniffing and unauthorized LUN mounting threats.
This strategy applies defense-in-depth across the SAN fabric and storage array control plane.

Anahtar Kavram

SAN Data Protection and Storage Network Segregation
Tahmini Süre:2m 0s
Soru 208Soru

A security engineer is hardening a shared Linux host operating system that runs containerized financial processing microservices. To minimize the risk of a container escape and kernel compromise, which TWO security mechanisms should the engineer implement to restrict container privileges and limit interaction with the host kernel?

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Apply custom seccomp (secure computing mode) profiles to restrict the system calls that container processes can issue to the host kernel.; Configure Linux user namespaces to map container root accounts to unprivileged user IDs on the underlying host operating system.

Cevap

Applying custom seccomp profiles to restrict host kernel system calls and configuring Linux user namespaces to map container root accounts to unprivileged host users are the correct controls.
The correct controls are applying seccomp profiles and configuring user namespaces. Seccomp profiles limit the system calls containerized processes can make directly to the host kernel, significantly reducing kernel exploit vulnerabilities. User namespaces ensure that even if an application inside a container runs as root, it is mapped to a non-privileged account on the host OS, preventing root access on the host during a breakout.

Adım Adım Çözüm

1
Identify the primary threat vector in containerized shared-host architectures.
Containers share a single host kernel, making syscall interface restriction critical to preventing host compromise.
Restricting kernel interactions decreases the surface area available for container escape exploits.
2
Evaluate privilege boundary controls.
User namespaces remap internal container UIDs (such as UID 0) to unprivileged host UIDs.
This prevents container root processes from executing privileged actions on the host OS if container isolation fails.
3
Evaluate syscall restriction controls.
Seccomp limits which system calls can be made by processes within a container to the Linux kernel.
Disabling unused kernel syscalls blocks unauthorized low-level kernel interaction.

Anahtar Kavram

Kernel surface reduction and privilege isolation in container security
Soru 209Soru

Match each storage security technology to its primary operational function.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

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

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Tokenization maps to replacing sensitive data fields with non-sensitive surrogate tokens; Self-Encrypting Drive (SED) maps to providing automatic, hardware-level block encryption directly on physical storage media; Hardware Security Module (HSM) maps to safeguarding and managing cryptographic keys inside dedicated physical security hardware; Data Loss Prevention (DLP) maps to monitoring and blocking unauthorized transmission or exfiltration of sensitive information.
Tokenization obfuscates data using surrogate tokens; SED provides automated physical drive encryption; HSM secures cryptographic keys; DLP inspects data to prevent unauthorized transfers.

Adım Adım Çözüm

1
Analyze each security technology listed on the left.
Identified Tokenization, SED, HSM, and DLP as primary storage and data protection mechanisms.
Each technology satisfies a specific, distinct function within enterprise storage architecture.
2
Match each technology to its unique functional capability.
Tokenization replaces data with surrogate tokens; SED encrypts disk blocks directly; HSM protects cryptographic keys; DLP prevents exfiltration.
Matching capabilities directly tests core knowledge of data protection and storage security mechanisms.

Anahtar Kavram

Storage and Data Protection Controls
Soru 210Soru

A fintech enterprise is restructuring its cloud-native microservices architecture to mitigate risks associated with lateral movement after a compromised service credential allowed unauthorized database queries. The security engineering team must align service-to-service communication with core Zero Trust Architecture (ZTA) principles. Which implementation strategy best enforces the Zero Trust principles of explicit verification and dynamic access control for every transaction request?

Cevabı ve açıklamayı göster

Cevap: Configuring the Policy Decision Point (PDP) to continuously evaluate identity attributes, contextual threat intelligence, and resource compliance state before issuing per-request authorization decisions to the Policy Enforcement Point (PEP).

Cevap

Configuring the Policy Decision Point (PDP) to continuously evaluate identity attributes, contextual threat intelligence, and resource compliance state before issuing per-request authorization decisions to the Policy Enforcement Point (PEP).
In a Zero Trust Architecture (ZTA), access decisions are never granted implicitly based on network location or initial login state. Instead, the Policy Decision Point (PDP) continuously evaluates contextual attributes (such as service identity, device compliance, telemetry, and threat risk) for every request, instructing the Policy Enforcement Point (PEP) to enforce fine-grained access control.

Adım Adım Çözüm

1
Analyze the core architectural requirements of Zero Trust Architecture (NIST SP 800-207 framework).
Zero Trust requires explicit verification of every access attempt, continuous risk assessment, least privilege access, and strict separation between the control plane and data plane.
Implicit trust based on network location or session duration must be eliminated to prevent lateral movement.
2
Differentiate between the functional roles of the Policy Decision Point (PDP) and Policy Enforcement Point (PEP).
The PDP acts in the control plane to evaluate policy parameters (user identity, device health, risk score, context) and generates authorization decisions. The PEP acts in the data plane to allow or block individual communication flows based on PDP directives.
Decoupling policy computation from traffic forwarding ensures granular, dynamic, and centrally managed security enforcement.
3
Evaluate the choices against Zero Trust tenets.
Evaluating identity attributes and contextual posture per-request via the PDP to instruct the PEP is the only strategy that eliminates implicit perimeter trust and enforces explicit per-request verification.
Options relying on subnet trust, long-lived session tokens, or pure anomaly detection fail to implement dynamic, identity-centric access control.

Anahtar Kavram

Zero Trust Architecture Control Plane Separation and Continuous Explicit Verification
Tahmini Süre:2m 0s
Soru 211Soru

A system administrator is hardening container instances operating on a shared host. Which TWO of the following mechanisms directly enforce kernel-level isolation and resource boundaries for container processes?

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Linux namespaces and control groups (cgroups); Seccomp profiles restricting allowed system calls

Cevap

Linux namespaces and control groups (cgroups), alongside seccomp profiles restricting allowed system calls, provide direct kernel-level process isolation and resource boundary enforcement for containerized environments.
Containers rely on kernel-level primitives. Linux namespaces isolate system resources (such as process trees, mount points, and network stacks), cgroups constrain resource consumption, and seccomp restricts the system calls available to containerized processes.

Adım Adım Çözüm

1
Identify container isolation mechanisms operating at the host kernel layer.
Linux namespaces provide process boundary separation, cgroups limit hardware resource allocation, and seccomp limits system call access.
Containers share the host operating system kernel, requiring kernel-level security features to restrict process permissions and resource access.
2
Evaluate and eliminate non-container isolation mechanisms.
Perimeter firewalls filter network traffic rather than host processes, and Type-1 hypervisors provide full VM hardware isolation rather than standard container isolation.
External network controls and hypervisor virtualization do not provide standard process isolation inside a shared OS container environment.

Anahtar Kavram

Kernel-level container isolation mechanisms
Soru 212Soru

A biopharmaceutical research enterprise is refactoring its data protection and storage security architecture across a hybrid deployment containing high-throughput NVMe Storage Area Network (SAN) arrays and off-site cloud object storage. The design must ensure zero-trust data protection for proprietary genomic data at rest and during transit, enforce cryptographically isolated key management, maintain ultra-low latency bulk encryption, and prevent sensitive data exfiltration from endpoint storage interfaces. Which of the following architectural controls should the security architect select to satisfy these enterprise security objectives? (Select THREE.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Deploy Hardware Security Modules (HSMs) integrated via Key Management Interoperability Protocol (KMIP) to isolate Key Encryption Keys (KEKs) from host systems and manage Data Encryption Key (DEK) wrapping.; Configure Self-Encrypting Drives (SEDs) featuring hardware-based AES bulk encryption and cryptographic erase (crypto-shredding) functionality on the storage array controller.; Implement contextual Data Loss Prevention (DLP) controls at storage egress points and endpoints to monitor pattern signatures and block unauthorized exfiltration.

Cevap

The correct controls are deploying HSMs via KMIP for isolated key management, utilizing hardware SEDs for low-latency bulk encryption at rest, and deploying DLP controls to prevent data exfiltration.
The combination of HSM-managed key envelopes via KMIP, array-level SED symmetric encryption, and enterprise DLP deployment provides complete defense-in-depth across data lifecycle states (rest, transit, use) while preserving NVMe SAN performance and regulatory separation of duties.

Adım Adım Çözüm

1
Analyze key management and cryptographic isolation requirements.
Identified envelope encryption via HSM and KMIP as the robust standard for isolating Key Encryption Keys (KEKs) and wrapping Data Encryption Keys (DEKs).
Cryptographic key separation ensures storage administrators cannot compromise raw keys directly from storage nodes.
2
Evaluate high-performance bulk data storage encryption methods for NVMe SAN arrays.
Selected hardware-based Self-Encrypting Drives (SEDs) utilizing AES symmetric encryption.
Hardware-based SEDs offload cryptographic overhead from host CPUs, sustaining high NVMe throughput while offering instant crypto-shredding capability.
3
Address data exfiltration threats across storage and endpoint boundaries.
Enforced inline and endpoint Data Loss Prevention (DLP) monitoring.
DLP inspects content pattern markers to restrict unauthorized copying or egress of proprietary intellectual property.

Anahtar Kavram

Enterprise Data Protection and Storage Architecture Controls
Soru 213Soru

A smart utility metering company is migrating its real-time telemetry processing pipeline to a public cloud environment. The architecture utilizes cloud-hosted virtual machines (IaaS) for running custom protocol ingestion agents and a fully managed database service (PaaS) for long-term data warehousing. Which TWO of the following operational security tasks remain the direct responsibility of the utility company's security team across both service models?

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Configuring role-based access controls and identity permissions for database objects and virtual machines; Encrypting customer metering data at rest and managing the cryptographic key rotation policies

Cevap

The utility company remains directly responsible for configuring role-based access controls and identity permissions, as well as encrypting customer metering data at rest and managing key rotation policies.
Under the cloud Shared Responsibility Model, data security (including data encryption at rest and managing encryption keys) and identity governance (configuring user access permissions and role-based policies) are strictly customer responsibilities regardless of whether IaaS, PaaS, or SaaS is utilized. The cloud service provider manages lower-level physical infrastructure and platform components, but tenant data configuration and access rights are always managed by the customer.

Adım Adım Çözüm

1
Analyze the cloud deployment components and service models in the scenario.
The infrastructure uses Infrastructure as a Service (IaaS) for virtual machine ingestion agents and Platform as a Service (PaaS) for the managed data warehouse.
Identifying the service models establishes the division of duties under the Shared Responsibility Model.
2
Evaluate candidate security tasks against customer vs. Cloud Service Provider (CSP) responsibility boundaries.
The CSP manages physical facilities, hypervisors, server hardware, and database engine infrastructure. The customer retains control and responsibility over identity/access management (IAM), data security, data classification, and encryption configuration across both service types.
Under the cloud shared responsibility model, ownership of data and access control configurations always resides with the customer tenant.

Anahtar Kavram

Shared Responsibility Model across IaaS and PaaS deployment models
Soru 214Soru

A logistics enterprise hosting financial transaction archives on an enterprise Storage Area Network (SAN) must ensure bulk data at rest remains cryptographically protected if physical drives are stolen or improperly decommissioned. The security architecture team mandates that encryption and decryption operations execute directly on the storage controller hardware without host server performance overhead, while key generation and key lifecycle management must remain strictly isolated inside a dedicated FIPS 140-3 validated key management appliance. Which of the following storage security solutions best meets these requirements?

Cevabı ve açıklamayı göster

Cevap: Deploy Self-Encrypting Drives (SEDs) within the storage array and integrate them with an external Hardware Security Module (HSM) using the Key Management Interoperability Protocol (KMIP).

Cevap

Deploying Self-Encrypting Drives (SEDs) integrated with an external Hardware Security Module (HSM) via KMIP is the correct storage security architecture choice.
Combining hardware-based Self-Encrypting Drives (SEDs) with an external Hardware Security Module (HSM) satisfies both performance and key isolation constraints. SEDs perform symmetric encryption directly on the drive controller to eliminate host system overhead, while the HSM acts as a centralized, FIPS-validated appliance for managing root keys via standardized protocols like KMIP.

Adım Adım Çözüm

1
Analyze performance and hardware encryption requirements
Self-Encrypting Drives (SEDs) use built-in media encryption keys (MEK) and hardware logic to encrypt/decrypt data at wire speeds without host CPU load.
The scenario requires zero performance overhead on the host OS servers during bulk storage encryption.
2
Analyze external key management requirements
An external Hardware Security Module (HSM) communicating via Key Management Interoperability Protocol (KMIP) securely generates, stores, and manages Key Encryption Keys (KEKs) for the storage array.
The requirement specifies keeping key lifecycle management isolated inside a FIPS 140-3 validated appliance.

Anahtar Kavram

Storage Encryption at Rest and HSM-based Key Management Architecture
Tahmini Süre:1m 30s
Soru 215Soru

An enterprise security architect is categorizing control plane and data plane functional duties during a Zero Trust Architecture (ZTA) migration. Match each Zero Trust architecture component on the left with its specific operational responsibility on the right.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

Policy Engine (PE)
Policy Administrator (PA)
Policy Enforcement Point (PEP)
Threat Intelligence System

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

The Policy Engine renders access authorization decisions; the Policy Administrator commands control plane session establishment or teardown; the Policy Enforcement Point gates data plane traffic; and the Threat Intelligence System supplies contextual threat data to dynamic trust scoring processes.
In Zero Trust Architecture (NIST SP 800-207), the control plane is split into evaluation logic (Policy Engine) and control execution (Policy Administrator), which together make up the Policy Decision Point (PDP). The Policy Enforcement Point (PEP) resides in the data plane to directly gate resource access. External contextual providers, such as Threat Intelligence Systems, supply real-time attack data to inform dynamic trust decisions.

Adım Adım Çözüm

1
Differentiate between Policy Decision Point (PDP) components and Policy Enforcement Point (PEP) locations.
Identified the Policy Engine and Policy Administrator as core PDP components in the control plane, while the PEP functions strictly within the data plane boundary.
ZTA relies on a clear operational separation between control plane decision logic and data plane traffic enforcement.
2
Distinguish between the decision logic (PE) and the execution logic (PA) within the PDP.
Matched the Policy Engine to policy calculation and access decision rendering, and the Policy Administrator to signaling the PEP to open or close session channels.
The PE evaluates contextual inputs against trust algorithms, whereas the PA communicates decision outcomes to enforcement gates.
3
Map supporting data sources to their external telemetry role.
Associated the Threat Intelligence System with providing real-time external threat feeds and dynamic risk context.
Continuous authorization relies on contextual data sources outside standard static identity attributes.

Anahtar Kavram

Zero Trust Control Plane vs. Data Plane Component Functions (NIST SP 800-207)
Soru 216Soru

Match each enterprise data protection architectural control to its corresponding storage security function.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

Tokenization with Format-Preserving Encryption
Hardware Security Module (HSM) with KMIP
LUN Masking and Fabric Zoning
Cryptographic Erase on Self-Encrypting Drives (SED)

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Tokenization with Format-Preserving Encryption matches replacing sensitive values with surrogate tokens while preserving database column schemas. Hardware Security Module (HSM) with KMIP matches providing centralized, tamper-resistant key generation and management. LUN Masking and Fabric Zoning matches restricting SAN access so only authorized HBAs can attach to specific storage targets. Cryptographic Erase on SEDs matches rapidly rendering physical drives unreadable during decommissioning by destroying internal encryption keys.
Each storage security mechanism operates at a distinct operational layer of data storage architecture: application/database field protection (tokenization with FPE), root key lifecycle governance (HSM with KMIP), SAN fabric path isolation (LUN masking and zoning), and media sanitization at end-of-life (cryptographic erase).

Adım Adım Çözüm

1
Analyze field-level data protection and schema preservation needs.
Identify Tokenization with Format-Preserving Encryption as the technique that substitutes sensitive values while keeping existing field formatting intact.
Tokenization replaces raw sensitive entries with surrogate values, avoiding database application syntax errors without storing actual plaintext.
2
Evaluate key protection architectures and interoperability protocols.
Connect HSM with KMIP to centralized hardware key generation, storage, and cross-platform key management communication.
HSMs provide physical and logical tamper protection for keys, and KMIP standardizes key management operations across multi-vendor storage environments.
3
Examine SAN network segmentation and storage access restriction controls.
Match LUN Masking and Fabric Zoning to Host Bus Adapter (HBA) initiator-to-target access enforcement.
Zoning isolates FC switch network communication, and LUN masking ensures storage controllers restrict volume visibility to intended host HBAs.
4
Assess storage drive retirement and media sanitization mechanisms.
Link Cryptographic Erase on SEDs to the immediate destruction of the internal Data Encryption Key (DEK).
Destroying the underlying DEK makes all encrypted blocks on self-encrypting drives permanently unrecoverable in seconds.

Anahtar Kavram

Data Protection and Storage Security Architecture Controls
Soru 217Soru

A enterprise cloud services provider is decommissioning a high-density, multi-tenant Storage Area Network (SAN) array containing sensitive tenant data. The SAN storage tier utilizes Self-Encrypting Drives (SEDs) configured to manage media encryption keys via a centralized Key Management Interoperability Protocol (KMIP) cluster. Due to lease agreements, the physical NVMe solid-state drives must remain intact and intact hardware must be returned to the lessor within a strict two-hour window. Which of the following technical procedures provides the most effective and cryptographically sound method to ensure all tenant data is permanently unrecoverable before the drives are removed?

Cevabı ve açıklamayı göster

Cevap: Instruct the centralized KMIP server to purge the Media Encryption Keys (MEKs) or Key Encryption Keys (KEKs) associated with the SED array to execute cryptographic erasure.

Cevap

Destroying or purging the Key Encryption Keys (KEKs) or Media Encryption Keys (MEKs) on the centralized KMIP server to perform cryptographic erasure (crypto-shredding) is the most effective approach.
Cryptographic erasure (crypto-shredding) relies on deleting the encryption key (MEK/KEK) that protects encrypted data at rest. Because the storage array utilizes Self-Encrypting Drives integrated with a KMIP key manager, purging the keys on the KMIP cluster renders all underlying block data instantaneously unrecoverable while leaving physical drive hardware completely undamaged.

Adım Adım Çözüm

1
Analyze storage architecture components
Identified Self-Encrypting Drives (SEDs) connected to an external enterprise Key Management Interoperability Protocol (KMIP) server storing key material.
Data at rest on SEDs is encrypted at the hardware level using symmetric keys locked by master keys managed externally.
2
Evaluate time and physical hardware constraints
Physical drives must remain undamaged due to lease return obligations, and decommissioning must occur within two hours.
Physical destruction (degaussing, shredding) violates lease terms, and full sector zeroization across multi-terabyte NVMe arrays exceeds the allowed timeframe.
3
Select cryptographic erasure method
Sanitize the media instantly by revoking/deleting the corresponding KEKs/MEKs on the KMIP key management cluster.
Without access to the decryption keys, the encrypted data remaining on the flash sectors becomes mathematically impossible to decipher, achieving NIST SP 800-88 compliant sanitization in seconds.

Anahtar Kavram

Cryptographic Erasure (Crypto-shredding) & Centralized Key Management (KMIP)
Soru 218Soru

An enterprise digital publishing company is migrating its core subscription portal and web application servers to an Infrastructure as a Service (IaaS) environment hosted by a public cloud provider. Under the cloud shared responsibility model, which of the following security operations remains the sole responsibility of the enterprise security team?

Cevabı ve açıklamayı göster

Cevap: Configuring guest operating system patches and host-based firewalls on deployed virtual machines

Cevap

Configuring guest operating system patches and host-based firewalls on deployed virtual machines is the responsibility of the enterprise security team.
In Infrastructure as a Service (IaaS), the cloud service provider abstracts and manages the physical data center, hardware, network infrastructure, and virtualization layer (hypervisor). The customer retains operational control over the virtual machine instances, including installing, patching, and configuring guest operating systems, middleware, applications, network security rules, and host-based firewalls.

Adım Adım Çözüm

1
Identify the cloud service model referenced in the scenario.
The scenario explicitly specifies Infrastructure as a Service (IaaS).
Security boundaries and operational responsibilities depend directly on whether the service model is IaaS, PaaS, or SaaS.
2
Apply the Cloud Shared Responsibility Model rules for IaaS.
The provider secures the infrastructure (hardware, hypervisor, data center physical security), whereas the customer secures everything operating on top of the hypervisor (guest OS, applications, configurations, data).
Customers maintain administrator access to virtual instances in IaaS, making OS patching and local security controls their responsibility.
3
Evaluate the options against customer responsibilities.
Guest operating system patching and local host firewall configuration correctly reflect customer duties under IaaS.
Physical security, hypervisor updates, and physical disk destruction belong strictly to the cloud provider.

Anahtar Kavram

Shared Responsibility Model in Infrastructure as a Service (IaaS)
Soru 219Soru

An infrastructure engineer is designing network-level resiliency for a critical telemetry gateway cluster operating within an industrial plant. The business continuity requirement specifies that the server nodes must maintain active network connection redundancy across two physically separate upstream access switches. Crucially, the network management team cannot make any configuration changes or protocol modifications (such as enabling port channels or link aggregation) on the existing switches. Which of the following networking configurations should the engineer implement to satisfy these requirements?

Cevabı ve açıklamayı göster

Cevap: Switch-independent active-backup NIC teaming with transmit load balancing

Cevap

Switch-independent active-backup NIC teaming with transmit load balancing provides host-level network path redundancy without requiring switch configuration changes.
The correct choice utilizes switch-independent active-backup NIC teaming. This architecture allows the host operating system to handle adapter failover independently using MAC management or probing, satisfying both the dual-switch redundancy requirement and the strict operational constraint preventing switch-side configuration changes.

Adım Adım Çözüm

1
Identify the primary constraint and objective in the scenario.
Objective is network link redundancy across dual switches; constraint is zero configuration changes on the access switches.
Any protocol requiring switch-side setup (like LACP or etherchannel) is immediately eliminated.
2
Distinguish host-managed NIC redundancy from switch-managed link aggregation.
Switch-independent NIC teaming allows the host hypervisor to manage link status via probing/beaconing without switch assistance.
The operating system controls which network interface card transmits frames, falling back seamlessly if a link fails.
3
Differentiate network interface high availability from storage fault tolerance and disaster recovery.
Multipath storage/RAID addresses block data access, while SAN replication addresses disaster recovery.
Only NIC teaming directly resolves host-to-switch network communication resilience.

Anahtar Kavram

Switch-Independent NIC Teaming for Host Network Resilience
Tahmini Süre:1m 30s
Soru 220Soru

During a security audit following an incident attempt on a containerized microservices environment, an analyst discovers that an attacker successfully gained remote code execution within a running container process. However, when the attacker attempted to modify system clock settings and mount host storage volumes, the operations failed because administrative privilege flags were restricted at the kernel level by the container runtime engine. Which security mechanism directly prevented the container process from performing these high-privilege host kernel operations?

Cevabı ve açıklamayı göster

Cevap: Linux kernel capability stripping (such as dropping CAP_SYS_ADMIN)

Cevap

Linux kernel capability stripping (such as dropping CAP_SYS_ADMIN) restricts containerized processes from performing administrative kernel operations.
The correct option correctly identifies Linux kernel capabilities as the security control responsible for breaking root power into granular permissions. By dropping capabilities such as CAP_SYS_ADMIN from the container runtime profile, the host kernel refuses requests to mount filesystems or alter system clocks even if the process operates as root inside the container.

Adım Adım Çözüm

1
Analyze the incident scenario requirements
The attacker achieved execution inside the container but was prevented from performing privileged host kernel operations (such as volume mounting or system clock adjustments).
Understanding the boundary being enforced (process-to-kernel level) identifies which isolation control is responsible.
2
Evaluate container privilege isolation mechanisms
Containers share the host Linux kernel. By default or custom configuration, dropping Linux capabilities (e.g., CAP_SYS_ADMIN, CAP_SYS_TIME) restricts specific system call groups regardless of the user's UID inside the container.
Kernel capabilities decompose traditional root privileges into granular permissions enforced directly by the host OS kernel.
3
Differentiate capability control from hypervisor and network mechanisms
Virtual machine hypervisors isolate guest kernels rather than process capabilities, while firewalls handle network communications.
Accurately matching the operational layer (kernel capabilities) eliminates non-kernel or network-only security controls.

Anahtar Kavram

Linux Kernel Capabilities and Container Privilege Restriction
ÖncekiSayfa 11 / 21Sonraki
Security Architecture Alıştırma Soruları — CompTIA Security+ — Sayfa 11 | Examkin