All practice questions

2232 questions

Question 661Question

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 662Question

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 663Question

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 664Question

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 665Question

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 666Question

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 667Question

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 668Question

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 669Question

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 670Question

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 671Question

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
Question 672Question

A security analyst at a global hospitality enterprise discovers an unauthorized remote access tool installed on point-of-sale systems across multiple properties. Investigation reveals that an external adversary gained initial access using compromised credentials from a third-party vendor to deploy custom malware specifically designed to harvest credit card data for long-term monetary profit. Based on these observed attributes, which threat actor type and primary motivation best describe this adversary?

Show answer & explanation

Answer: Organized crime motivated by financial gain

Answer

Organized crime motivated by financial gain
The correct answer accurately identifies organized crime motivated by financial gain. Organized cybercrime syndicates typically target financial instruments, point-of-sale infrastructure, and credit card numbers using external attack vectors (such as compromised supply chain credentials) to generate illicit revenue.

Step-by-Step Solution

1
Analyze the attack vector and access method
The intrusion originated externally via stolen third-party vendor credentials, indicating an external adversary rather than an insider.
Threat actors are categorized by their origin point (internal vs. external) and vector of entry.
2
Evaluate the primary objective and target asset
The target was point-of-sale financial data specifically collected for monetary monetization.
Adversary intent directly maps to threat actor classifications and profile attributes.
3
Correlate attributes to threat actor profiles
External origin, sophisticated target selection (POS systems), and financial motivation directly match the profile of organized cybercrime groups.
Organized crime threat actors systematically seek financial exfiltration using well-resourced tools.

Key Concept

Threat Actor Profiling and Attributes
Question 673Question

A cloud-native financial services company is updating the security architecture of its containerized microservices platform, which handles real-time payment transactions. The security team must limit lateral movement across internal workloads, enforce zero trust principles for internal service communication, and ensure continuous traffic inspection. Which of the following technical controls should the security team implement to achieve this network segmentation design? (Select TWO).

Select all that apply

Show answer & explanation

Answer: Deploy host-level microsegmentation policies via a service mesh to enforce mutual TLS (mTLS) authentication and application-layer authorization for pod-to-pod communications.; Implement internal layer 7 firewalls and deep packet inspection between internal service tiers to continuously inspect and control East-West network flows.

Answer

The security team should deploy service mesh host-level microsegmentation with mutual TLS (mTLS) and implement internal layer 7 firewalls to inspect East-West network traffic continuously.
Implementing service mesh microsegmentation with mutual TLS enforces cryptographically verified identity and application-layer policies between container workloads. Pairwise layer 7 internal firewalling ensures continuous deep packet inspection of East-West traffic, directly stopping unauthorized lateral movement within the cloud environment.

Step-by-Step Solution

1
Analyze the requirements for limiting lateral movement and enforcing zero trust within microservice workloads.
Identified that microservice environments require workload-centric identity and granular East-West traffic controls rather than edge-only defenses.
Containerized workloads share underlying network infrastructure, making traditional perimeter security insufficient.
2
Evaluate microsegmentation and cryptographic access options.
Selected service mesh microsegmentation with mTLS to enforce endpoint identity and application-layer access controls between individual pods.
mTLS guarantees cryptographically validated service identities and encrypts internal traffic.
3
Evaluate traffic inspection mechanisms for internal flows.
Selected internal layer 7 deep packet inspection firewalls for continuous monitoring and filtering of East-West microservice communication.
Layer 7 inspection detects payload threats and protocol anomalies traversing internal segments.

Key Concept

Microsegmentation and East-West Traffic Protection in Zero Trust Architecture
Question 674Question

During a technical security assessment of an enterprise cloud environment, a security engineer discovers that a process running within a containerized workload executed a host kernel exploit to access memory allocated to neighboring containers on the same host. To mitigate this risk, the organization must implement an architecture that prevents shared-kernel vulnerability exploitation by providing an independent kernel and hardware-enforced separation for each workload. Which of the following solutions should the engineer recommend?

Show answer & explanation

Answer: Type-1 hypervisor virtual machines

Answer

Type-1 hypervisor virtual machines provide hardware-enforced isolation and separate OS kernels for each workload, eliminating shared-kernel vulnerabilities inherent to containers.
Implementing Type-1 hypervisor virtual machines guarantees that each workload operates within its own virtualized hardware environment and runs its own isolated kernel. Because virtual machines do not share a kernel with the host or neighboring workloads, a kernel compromise in one VM cannot directly reach another VM.

Step-by-Step Solution

1
Analyze the security breach vector presented in the scenario.
Identified that the vulnerability exploited the shared kernel model of standard application containers.
Containers share the underlying host operating system kernel, making all co-located containers vulnerable if a kernel-level exploit occurs.
2
Evaluate the architectural requirements specified by the organization.
Determined that the target architecture requires dedicated OS kernels and hardware-backed isolation boundaries.
Eliminating shared-kernel exploits requires moving from OS-level virtualization (containers) to hardware virtualization (virtual machines).
3
Select the appropriate technology component.
Type-1 hypervisors manage virtual machines directly on bare-metal hardware, supplying separate kernels and strong isolation for each instance.
Virtual machines running on a bare-metal hypervisor maintain completely independent kernel spaces.

Key Concept

Virtual Machine Isolation vs. Shared-Kernel Container Architecture
Question 675Question

A security engineer auditing an enterprise cloud microservices environment identifies two specific architectural design choices: internal microservice-to-microservice traffic relies solely on network IP address allowlists without identity verification, and database backup files are encrypted using AES operating in Electronic Codebook (ECB) mode. Which of the following statements correctly describe the cryptographic and security control weaknesses present in this environment? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Electronic Codebook (ECB) mode encrypts identical plaintext blocks into identical ciphertext blocks, preserving structural data patterns in the encrypted output.; Exclusive reliance on IP address allowlists relies on perimeter network location rather than cryptographic identity, violating Zero Trust continuous verification principles.

Answer

The weaknesses are that Electronic Codebook (ECB) mode reveals structural data patterns because identical plaintext blocks produce identical ciphertext blocks, and exclusive reliance on IP allowlists creates an outdated perimeter trust model that violates Zero Trust architecture principles.
The correct statements correctly identify the core weaknesses of ECB mode and implicit network trust. ECB mode encrypts identical plaintext blocks into identical ciphertext blocks because it lacks initialization vectors or chaining mechanism, exposing patterns in stored database files. Furthermore, relying solely on IP allowlists creates an implicit perimeter trust model, failing to enforce Zero Trust principles such as mutual TLS (mTLS) authentication and continuous verification.

Step-by-Step Solution

1
Analyze the cryptographic cipher mode flaw (AES-ECB).
Identified that ECB lacks initialization vectors and block chaining, meaning identical 128-bit plaintext blocks yield identical ciphertext blocks, leaking structural information.
Cryptographic modes like CBC or GCM must be used for confidentiality and data pattern hiding.
2
Analyze the access control weakness (IP allowlisting without mutual authentication).
Identified that trusting requests based on IP address alone assumes network position implies legitimacy.
Modern enterprise security requires Zero Trust architecture (ZTA) where identity is explicitly validated regardless of network location.

Key Concept

Cryptographic Block Cipher Modes and Zero Trust Access Control Weaknesses
Question 676Question

A security analyst reviews the following web server access log entry:

192.168.1.45 - - [27/Jul/2026:14:32:10 +0000] "GET /products.php?id=1%20UNION%20SELECT%20username,password%20FROM%20users-- HTTP/1.1" 200 4523

Which of the following attack types is indicated by this log entry?

Show answer & explanation

Answer: SQL Injection (SQLi)

Answer

SQL Injection (SQLi)
The option identifying SQL Injection (SQLi) is correct because the URL parameter contains explicit SQL command structures ('UNION SELECT') designed to query backend database tables.

Step-by-Step Solution

1
Inspect the requested URL parameters in the log entry
The parameter id contains '%20UNION%20SELECT%20username,password%20FROM%20users--'
URL decoding reveals SQL query syntax appended to the input parameter.
2
Identify the underlying attack mechanism
SQL keywords like UNION SELECT attempt to extract data directly from backend database tables
Manipulating backend database SQL queries via unsanitized parameter inputs defines a SQL Injection attack.

Key Concept

Identifying SQL Injection attack signatures in web access logs
Estimated Time:45s
Question 677Question

An enterprise organization is deploying a centralized storage architecture hosting high-value transactional databases. Compliance regulations require that all storage volumes maintain encryption at rest, and master cryptographic keys must be generated, safeguarded, and offloaded to dedicated hardware isolated from host OS administrators to prevent unauthorized key extraction. Which of the following solutions should the security architect integrate into the storage architecture to fulfill this key management requirement?

Show answer & explanation

Answer: Hardware Security Module (HSM)

Answer

Hardware Security Module (HSM)
A Hardware Security Module (HSM) is a hardened, physical computing device that safeguards and manages digital keys, performs encryption and decryption functions, and generates strong random cryptographic keys. By storing master keys inside an HSM, key extraction by host operating system administrators or malware is prevented.

Step-by-Step Solution

1
Analyze the enterprise security requirement
Identified the core requirement: isolating cryptographic key generation and management into dedicated hardware separate from the host OS.
Host operating systems and hypervisors can be compromised by privilege escalation or unauthorized administrative key extraction.
2
Evaluate potential storage protection and key management solutions
Determined that a Hardware Security Module (HSM) provides physical isolation, tamper resistance, and secure key lifecycle management.
HSMs meet regulatory standards (such as FIPS 140-2/140-3) for key isolation and offloaded cryptographic processing.

Key Concept

Hardware-Based Key Protection and Storage Security Architecture
Question 678Question

A regional financial institution migrates its customer ticketing platform to a public cloud provider under a Software as a Service (SaaS) model. During an architectural security review, the team evaluates operational duties under the cloud shared responsibility model. Which of the following security controls remains the sole responsibility of the financial institution?

Show answer & explanation

Answer: Managing user identity lifecycles, access role assignments, and data classification policies

Answer

Managing user identity lifecycles, access role assignments, and data classification policies remains the sole responsibility of the institution.
Under the cloud shared responsibility model for Software as a Service (SaaS), the cloud service provider manages all lower-tier components including physical security, infrastructure hardware, hypervisors, operating systems, and application code. The customer maintains full responsibility for managing their own data, classifying sensitivity levels, and configuring identity and access management (IAM) policies.

Step-by-Step Solution

1
Identify the cloud deployment and service model
The scenario specifies a Software as a Service (SaaS) model.
Service models dictate how control responsibilities are divided between provider and subscriber.
2
Delineate responsibilities for SaaS environments
The Cloud Service Provider (CSP) manages physical facilities, hardware, hypervisors, OS patching, and application runtime code.
SaaS abstracts all underlying infrastructure and application maintenance away from the customer.
3
Determine customer-owned operational boundaries
The customer is always responsible for data governance, data classification, device security, and user access management regardless of service model.
Identity and data remain customer responsibilities across IaaS, PaaS, and SaaS.

Key Concept

Cloud Shared Responsibility Model in SaaS
Estimated Time:1m 15s
Question 679Question

A system administrator notices that several virtualized database servers are experiencing sustained 100% CPU utilization during off-peak hours. Outbound network logs show persistent, encrypted connections on TCP port 3333 transmitting data structured with the Stratum communication protocol. An endpoint inspection reveals an unauthorized process masquerading as a system executable (`svchost.exe`) running under a compromised service account. Which of the following malware types is most likely responsible for this activity?

Show answer & explanation

Answer: Cryptominer

Answer

Cryptominer
The combination of sustained maximum CPU utilization, process disguise via spoofed system executable names (`svchost.exe`), and outbound network traffic using the Stratum mining protocol specifically defines cryptomining malware (cryptojacking).

Step-by-Step Solution

1
Analyze resource utilization indicators
Identify sustained 100% CPU usage during off-peak hours, pointing to intensive processing tasks.
Cryptocurrency mining algorithms rely heavily on system hardware resource consumption.
2
Evaluate network telemetry protocol artifacts
Confirm outbound traffic using the Stratum mining protocol on TCP port 3333.
Stratum is the standard protocol for mining pool communication.
3
Synthesize indicators to classify malware type
Match high CPU load and Stratum pool communications to a unauthorized cryptominer masquerading as a legitimate Windows system process.
Cryptojacking malware frequently hides behind system process names while consuming hardware resources.

Key Concept

Cryptominer / Cryptojacking Indicators of Compromise
Question 680Question

A regional health insurance organization is migrating its claims processing engine to a cloud provider using a Serverless Function-as-a-Service (FaaS) execution model connected to a managed Database-as-a-Service (DBaaS) backend. During a compliance audit, the security team is asked to document control ownership across the deployment layers. Which of the following statements correctly identifies the customer's operational responsibility in this deployment architecture?

Show answer & explanation

Answer: Managing application source code security, data classification, and fine-grained identity and access policies.

Answer

The customer is responsible for managing application source code security, data classification, and fine-grained identity and access policies.
Under the cloud shared responsibility model for serverless (FaaS) and managed database (PaaS) architectures, the cloud service provider manages all underlying hardware, hypervisors, OS patching, and engine runtimes. The customer retains full responsibility for securing their application logic/code, classifying their data, and configuring identity and access management permissions.

Step-by-Step Solution

1
Analyze the specified cloud service models in the scenario
The architecture utilizes Serverless (FaaS) and Database-as-a-Service (DBaaS), both falling under Platform as a Service (PaaS) abstract execution models.
Determining the exact service model dictates the boundary line in the Cloud Shared Responsibility Model.
2
Evaluate cloud service provider (CSP) responsibilities for PaaS/FaaS
The CSP manages physical data centers, hardware, hypervisors, OS patching, database software engine maintenance, and runtime environments.
Abstracted environments offload infrastructure and host maintenance away from the customer.
3
Identify non-transferable customer responsibilities
Regardless of cloud abstraction, data ownership, identity management, access control configurations, and application code security always remain the responsibility of the cloud customer.
The customer owns customer data and the code deployed onto provider platforms.

Key Concept

Cloud Shared Responsibility Model in Serverless and PaaS Environments
Estimated Time:1m 40s
PreviousPage 34 / 112Next
All practice questions — CompTIA Security+ | Examkin