Security Architecture

405 soru

Soru 221Soru

An enterprise security architect is refining the organization's data protection and storage security architecture. Match each enterprise storage security objective on the left with the primary storage control or mechanism on the right that best satisfies the requirement.

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

Öğeler

Preventing unauthorized access to SAN block volumes by restricting visibility to specific Host Bus Adapter (HBA) World Wide Names (WWNs) at the storage controller layer.
Offloading cryptographic key generation, lifecycle management, and secure key storage to dedicated hardware compliant with FIPS 140-3 Level 3 requirements.
Ensuring hardware-level full disk encryption that transparently encrypts data at rest directly on disk controllers without OS overhead.
Replacing sensitive account numbers with surrogate values of identical length and character type before writing to database storage.

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

The correct pairings are: 1) Preventing unauthorized SAN volume access pairs with LUN Masking and Zoning. 2) Offloading key generation and lifecycle management to tamper-resistant hardware pairs with Hardware Security Module (HSM). 3) Hardware-level disk block encryption without OS reliance pairs with Self-Encrypting Drives (SED). 4) Replacing account numbers with format-matched surrogate tokens pairs with Format-Preserving Tokenization.
Each requirement directly aligns with a foundational storage security architectural control: LUN Masking/Zoning isolates SAN storage access; HSMs secure key management infrastructure; SEDs deliver hardware-based encryption at rest; and Format-Preserving Tokenization protects structured sensitive data while maintaining system schema constraints.

Adım Adım Çözüm

1
Analyze SAN block volume visibility control requirements
Identify LUN Masking and SAN Fabric Zoning as the mechanisms configured at the storage network layer to restrict volume presentation based on HBA WWN addresses.
LUN masking operates at the storage controller/target level to hide logical units from unauthorized initiator host HBAs.
2
Analyze tamper-resistant key lifecycle management requirements
Identify Hardware Security Module (HSM) as the hardware appliance designed for centralized, FIPS-certified key storage and cryptographic operations.
HSMs isolate root keys and cryptographic processing within physical tamper-evident physical boundaries.
3
Analyze controller-level transparent storage encryption at rest
Identify Self-Encrypting Drives (SED) as self-contained storage media equipped with onboard ASIC encryption controllers.
SEDs implement full disk encryption transparently at hardware speeds without processor overhead from the host operating system.
4
Analyze schema-preserving surrogate data replacement requirements
Identify Format-Preserving Tokenization as the database/application control that maps original sensitive data to tokens of identical structure.
Tokenization removes real sensitive values from the storage backend while maintaining length and field data type formatting.

Anahtar Kavram

Storage Architecture Security Controls & Encryption Mechanisms
Soru 222Soru

An organization is migrating sensitive financial API workloads from traditional virtual machines to an unmanaged container orchestration cluster hosted on bare-metal servers. During a security architecture review, the security team expresses concern that a container compromise could lead to host kernel exploitation or unauthorized lateral movement between isolated tenant containers. Which TWO of the following technical controls directly mitigate these runtime isolation risks at the host level?

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

Cevabı ve açıklamayı göster

Cevap: Configuring user namespaces (userns) on the container daemon to map container root permissions to an unprivileged non-root UID on the host host system; Enforcing secure computing mode (seccomp) profiles to restrict the specific system calls containerized processes can make to the host kernel

Cevap

The correct controls are mapping container root accounts to unprivileged host users via user namespaces and restricting system calls via seccomp profiles.
Containers share the host kernel. To protect the host operating system from container-based threats, security controls must restrict host-level privileges and kernel access. User namespaces prevent a containerized root user from possessing administrative access on the host, while seccomp restricts the syscalls that container processes can issue to the kernel.

Adım Adım Çözüm

1
Analyze container privilege risks
Containers share the underlying host operating system kernel, meaning container root privileges could default to host root access if an escape occurs.
Mapping container UID 0 to an unprivileged user ID on the host using user namespaces ensures that escalated container privileges do not translate to host root control.
2
Analyze host kernel attack surface reduction
Restricting available Linux system calls minimizes the attack surface against host kernel vulnerabilities.
Applying seccomp profiles blocks unnecessary or dangerous system calls (such as ptrace or reboot), preventing compromised microservices from executing exploits against the shared kernel.

Anahtar Kavram

Container Security and Host Kernel Isolation Mechanisms
Soru 223Soru

A manufacturer of medical IoT devices wants to permanently disable hardware debug interfaces, such as JTAG, prior to shipping devices to customers. This control must be executed at the silicon level so that hardware debugging cannot be re-enabled through software or firmware modifications. Which of the following hardware security mechanisms should the manufacturer use?

Cevabı ve açıklamayı göster

Cevap: Blowing an electronic fuse (eFuse) on the System-on-Chip during post-manufacturing provisioning.

Cevap

Blowing an electronic fuse (eFuse) on the System-on-Chip during post-manufacturing provisioning.
Blowing an eFuse provides a permanent, irreversible hardware-level change on the silicon itself. Because blowing a fuse physically breaks electrical traces inside the integrated circuit, it guarantees that debug interfaces such as JTAG cannot be re-enabled through subsequent firmware updates or software attacks.

Adım Adım Çözüm

1
Identify the primary constraint specified in the scenario.
The requirement demands a permanent, irreversible silicon-level hardware control that prevents software from re-enabling debug ports.
Software controls or re-programmable memory can be tampered with if firmware is compromised.
2
Evaluate candidate hardware features against the requirement.
Electronic fuses (eFuses) write One-Time Programmable (OTP) bit states by permanently opening an internal electrical circuit on the chip.
Once an eFuse is blown, the physical link is severed forever, preventing any future firmware or software from re-enabling the debug interface.

Anahtar Kavram

eFuse and One-Time Programmable (OTP) Hardware Security Controls
Tahmini Süre:45s
Soru 224Soru

A security administrator must securely access an internal database server located within a restricted database zone from a remote management workstation. Place the following connection and transit steps in the correct sequential order from initial external access to final database session establishment according to secure network design principles.

Öğeleri doğru sıraya koymak için sürükleyin

Cevabı ve açıklamayı göster

Cevap

The correct sequence starts with authenticating to the DMZ bastion host using MFA, passing posture and AAA checks on the bastion, traversing the internal stateful firewall via restrictive bastion-to-database rules, and finally establishing the privileged database session.
Secure network design dictates that administrative access to sensitive internal zones (such as a database subnet) must pass through a jump server located within a DMZ or management zone. First, the administrator must authenticate to the bastion host using MFA. Second, device posture and AAA authorization controls evaluate the session on the bastion host. Third, the connection traverses the internal stateful firewall, which uses tight microsegmentation rules to permit transit only from the bastion host IP address to the database server port. Finally, the user establishes the authenticated session on the internal target database.

Adım Adım Çözüm

1
Initiate connection to the perimeter management DMZ
Administrator successfully authenticates to the jump box via MFA at the network boundary.
Direct connections from remote devices into internal secure zones are prohibited by network segmentation policies.
2
Perform posture and access authorization validation on the jump box
The bastion gateway verifies device health and confirms administrative permissions.
Zero trust microsegmentation requires verifying identity and device security posture before allowing transit deeper into the network.
3
Pass through internal stateful firewall microsegmentation controls
Network traffic is permitted through the internal boundary filter specifically targeting the database zone.
Internal firewalls should enforce strict firewall policies allowing DB ports only from the specific IP address of the jump box.
4
Authenticate to the internal target database server
Privileged database administration session begins inside the target subnet.
This is the final destination node requiring database-level credential verification.

Anahtar Kavram

Bastion Host Transit & Secure Network Segmentation
Soru 225Soru

A cloud security architect is establishing isolation and resource protection mechanisms for a hybrid deployment containing both virtualized workloads and containerized microservices. Match each security mechanism to its primary isolation function.

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

Öğeler

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

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Linux Namespaces match with restricting a process's view of system resources; Linux Control Groups (cgroups) match with enforcing resource allocation limits (CPU, memory, I/O); Secure Computing Mode (seccomp) matches with filtering and restricting kernel system calls; Type-1 Hypervisor matches with providing hardware-level abstraction running directly on bare-metal host hardware.
Each technology provides a distinct security and isolation boundary layer within enterprise virtualization and containerization architectures: Namespaces isolate visibility into host resources, Control Groups enforce resource consumption limits, Seccomp restricts syscall surface area exposed to the shared kernel, and Type-1 hypervisors provide hardware-assisted bare-metal guest isolation.

Adım Adım Çözüm

1
Analyze container kernel isolation and view boundary mechanisms.
Identify that Linux Namespaces restrict process visibility into PIDs, network stacks, and filesystems, while seccomp restricts the system calls executable against the kernel.
Namespaces govern visibility boundaries whereas seccomp governs host syscall attack surface.
2
Analyze container resource governance mechanisms.
Identify that Linux Control Groups (cgroups) regulate compute, memory, and I/O consumption.
cgroups prevent individual microservices from consuming excessive host capacity.
3
Analyze virtualization layer boundaries.
Identify that Type-1 hypervisors execute on physical hardware to partition virtual machines.
Bare-metal hypervisors enforce hardware-level virtual machine boundary isolation.

Anahtar Kavram

Virtualization and Containerization Security Mechanisms
Tahmini Süre:1m 30s
Soru 226Soru

Match each advanced hardware security mechanism or embedded architecture component to its primary operational security function.

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

Öğeler

Hardware Root of Trust (RoT) / eFuse
Physical Unclonable Function (PUF)
Bus Encryption Engine
Hardware Security Module (HSM)

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Hardware Root of Trust / eFuse pairs with the unalterable hardware baseline for boot signature validation; Physical Unclonable Function (PUF) pairs with deriving cryptographic keys from semiconductor manufacturing variations; Bus Encryption Engine pairs with encrypting data traversing physical PCB traces; Hardware Security Module (HSM) pairs with offloading and managing enterprise cryptographic keys within tamper-evident hardware enclosures.
The correct pairings directly correspond to each technology's foundational architectural design: Hardware Root of Trust (eFuse) provides an unchangeable anchor for boot chain verification; Physical Unclonable Function (PUF) derives keys from physical silicon variances; Bus Encryption Engine protects data in transit over physical board traces; and Hardware Security Module (HSM) manages high-volume enterprise cryptographic keys in dedicated tamper-resistant enclosures.

Adım Adım Çözüm

1
Analyze the role of immutable hardware primitives in secure system startup.
Link Hardware Root of Trust (RoT) and eFuses to the permanent, write-once validation mechanism for initial boot signatures.
Software integrity must be rooted in unmodifiable hardware primitives to prevent low-level firmware tampering.
2
Evaluate key generation mechanisms that avoid static key storage on embedded chips.
Associate Physical Unclonable Functions (PUFs) with generating keys directly from silicon physical variations upon device power-up.
Static flash storage of cryptographic keys exposes system secrets to physical reverse engineering, whereas PUFs dynamically reconstruct keys.
3
Identify protection controls designed for physical system interconnects and memory buses.
Connect Bus Encryption Engines to real-time encryption of physical trace data paths between CPU and RAM.
Physical attacks like memory bus sniffing or logic analyzer probing target plaintext data passing across hardware interconnects.
4
Differentiate endpoint hardware security primitives from centralized infrastructure appliances.
Match Hardware Security Modules (HSMs) to centralized enterprise key lifecycle protection and dedicated cryptographic processing.
HSMs function as enterprise-grade hardware appliances engineered specifically for robust key lifecycle management and high-volume operations.

Anahtar Kavram

Hardware primitives, embedded system hardening, and cryptographic boundary protection
Soru 227Soru

A commercial logistics enterprise is migrating its legacy cargo tracking application to an Infrastructure as a Service (IaaS) environment hosted by a public cloud service provider. During the architecture review, the chief information security officer (CISO) requests clarification on operational security boundaries under the shared responsibility model. Which of the following best describes the security responsibility allocation for this deployment?

Cevabı ve açıklamayı göster

Cevap: The enterprise retains responsibility for guest operating system patching and host-based firewall configurations, while the cloud provider manages physical hardware maintenance and hypervisor updates.

Cevap

The enterprise retains responsibility for guest operating system patching and host-based firewall configurations, while the cloud provider manages physical hardware maintenance and hypervisor updates.
In Infrastructure as a Service (IaaS), the cloud provider is responsible for securing and maintaining the underlying physical facilities, host hardware, storage subsystems, and hypervisor virtualization layer. The cloud customer remains responsible for everything running on top of the hypervisor, including guest operating system installation and patching, host firewalls, middleware, data encryption, and access management.

Adım Adım Çözüm

1
Identify the cloud service model referenced in the scenario.
The scenario specifies an Infrastructure as a Service (IaaS) deployment model.
Security boundaries shift depending on whether the service model is IaaS, PaaS, or SaaS.
2
Apply the Cloud Shared Responsibility Model to the IaaS framework.
The CSP manages physical assets, storage infrastructure, network hardware, and the hypervisor layer. The customer manages guest OS, application security, middleware, network configuration (firewalls/subnets), and identity governance.
In IaaS, virtualized hardware resources are delivered to the customer, leaving software stack maintenance to the subscriber.
3
Evaluate the options against the derived responsibility boundaries.
The option stating the enterprise manages guest OS patching while the CSP manages hypervisors accurately delineates IaaS duties.
This alignment matches CompTIA Security+ standards for cloud security architecture.

Anahtar Kavram

Shared Responsibility Model in IaaS Cloud Deployments
Soru 228Soru

A healthcare enterprise is architecting a storage and data security solution for its electronic health record (EHR) database environment. The design must ensure bulk data at rest remains cryptographically secured without causing significant performance overhead on database queries, while also preventing unauthorized exfiltration of sensitive patient records across endpoint storage interfaces and removable media. Which of the following security controls should the architect integrate to satisfy these requirements? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Deploy symmetric envelope encryption or hardware-accelerated volume encryption (such as AES-256) for the underlying storage subsystem.; Implement endpoint Data Loss Prevention (DLP) software agents to inspect, classify, and enforce contextual blocking on local storage transfers.

Cevap

The correct architecture controls are deploying symmetric encryption (such as AES-256) for bulk storage volume protection and implementing endpoint Data Loss Prevention (DLP) agents for endpoint storage exfiltration control.
Protecting bulk data at rest efficiently requires high-speed symmetric ciphers (such as AES-256) at the storage volume level, which ensures strong confidentiality without computational performance degradation. Preventing data exfiltration to endpoint storage devices requires endpoint Data Loss Prevention (DLP) agents that monitor and enforce policy rules on data in use and local storage interfaces.

Adım Adım Çözüm

1
Analyze storage encryption at rest requirements for high-performance database workloads.
Bulk encryption requires fast, hardware-accelerated symmetric ciphers like AES-256 to avoid severe query latency.
Symmetric ciphers use a single secret key and process bulk data efficiently compared to asymmetric ciphers.
2
Evaluate data exfiltration protection across endpoint storage and removable media.
Host/endpoint DLP agents inspect content and context on the local machine to block unauthorized transfers to removable storage.
Network-based controls cannot see or restrict local device bus transfers like USB writes.

Anahtar Kavram

Data Protection and Storage Security Architecture
Soru 229Soru

A healthcare organization is refactoring its data architecture to secure sensitive patient diagnostic records stored on a Network Attached Storage (NAS) array. The security requirements dictate that data must be encrypted at rest, key lifecycle operations must be centrally managed and audited, and storage administrators must not have direct access to root cryptographic keys or store them on the local NAS hardware. Which of the following data protection solutions best fulfills these architectural requirements?

Cevabı ve açıklamayı göster

Cevap: Integrate the NAS array with a centralized Key Management Interoperability Protocol (KMIP) server backed by a Hardware Security Module (HSM).

Cevap

Integrate the NAS array with a centralized Key Management Interoperability Protocol (KMIP) server backed by a Hardware Security Module (HSM).
Integrating a storage array with a Key Management Interoperability Protocol (KMIP) server backed by a Hardware Security Module (HSM) ensures bulk data at rest is encrypted using symmetric keys managed through a standardized enterprise protocol. The HSM provides dedicated, tamper-resistant hardware to generate, store, and audit root keys independently of the NAS array and administrators.

Adım Adım Çözüm

1
Analyze storage encryption and key management requirements.
Identified the need for bulk encryption at rest, centralized key lifecycle administration, and secure key storage isolated from the NAS device.
Storing keys locally on storage arrays introduces security risks and management overhead.
2
Evaluate key management standards and hardware security controls.
KMIP enables standardized communication between storage devices and centralized key management systems, while HSMs provide tamper-resistant hardware protection for root keys.
Combining KMIP and HSM satisfies both centralized management and secure key storage demands.
3
Compare against incorrect alternatives.
Asymmetric bulk encryption is computationally impractical, firewall segmentation only addresses network boundary security, and HMACs provide integrity rather than confidentiality.
Only the KMIP and HSM integration meets all requirements for data at rest encryption and secure key management.

Anahtar Kavram

Centralized Storage Key Management and HSM Integration
Soru 230Soru

A global healthcare organization requires a federated access solution allowing external medical specialists from partner hospitals to query patient diagnostic APIs hosted in its cloud environment. The architecture must ensure partner organizations maintain control over their own user credentials, support identity assertion, enable fine-grained attribute-based access decisions at the API gateway without exposing internal directory services, and avoid establishing persistent network-level perimeter trust. Which architectural combination of identity and authorization frameworks best satisfies these security requirements?

Cevabı ve açıklamayı göster

Cevap: OpenID Connect (OIDC) for user identity assertion combined with OAuth 2.0 access tokens evaluated at the API gateway for authorization

Cevap

OpenID Connect (OIDC) for user identity assertion combined with OAuth 2.0 access tokens evaluated at the API gateway for authorization
Combining OpenID Connect (OIDC) with OAuth 2.0 directly satisfies federated access, decentralized credential management, and Zero Trust API protection. OIDC acts as the identity layer enabling external Identity Providers (IdPs) to assert user identity using signed JSON Web Tokens (JWTs). OAuth 2.0 provides delegated authorization, passing access tokens containing scopes and claims to the cloud API gateway for fine-grained enforcement without exposing legacy internal directory services or relying on perimeter network connectivity.

Adım Adım Çözüm

1
Analyze identity federation and credential boundary requirements
External partner organizations must manage their own credentials, requiring an external Identity Provider (IdP) capable of issuing standardized identity assertions.
Direct credential sharing or internal directory registration violates federation architecture principles.
2
Evaluate API authorization enforcement mechanics
OAuth 2.0 access tokens containing JSON Web Token (JWT) scopes and user claims allow the API gateway to enforce fine-grained attribute-based access control (ABAC).
Application programming interfaces (APIs) require stateless token verification at the gateway layer rather than legacy session cookies or network-level checks.
3
Synthesize OIDC and OAuth 2.0 roles into the final architecture
OIDC handles the authentication ('who the specialist is') via ID tokens from the partner IdP, while OAuth 2.0 handles authorization ('what APIs the specialist can access') via access tokens.
Combining OIDC for identity assertion with OAuth 2.0 for API access control meets all security, cloud compatibility, and Zero Trust requirements.

Anahtar Kavram

Federated Identity and API Authorization Architecture (OIDC & OAuth 2.0)
Tahmini Süre:3m 0s
Soru 231Soru

A financial enterprise is deploying a third-party reporting server into a virtualized datacenter. The reporting server requires outbound internet access to fetch external market data, but corporate security policy dictates that it must be strictly prevented from initiating lateral connections to any other internal virtual machines, even those within the same subnet. Which of the following network architecture design solutions best satisfies this requirement?

Cevabı ve açıklamayı göster

Cevap: Implement microsegmentation policies using a software-defined network or host-based firewall rules to control east-west traffic at the hypervisor level.

Cevap

Implementing microsegmentation policies using software-defined networking or granular host/hypervisor firewall rules provides the necessary east-west traffic control to prevent lateral movement within the same subnet while maintaining required internet connectivity.
Microsegmentation applies granular, software-defined security policies at the individual workload or hypervisor level. This enables strict filtering of east-west traffic, preventing the reporting server from initiating connections to adjacent internal virtual machines regardless of network topology, while allowing specific outbound north-south internet traffic.

Adım Adım Çözüm

1
Analyze the operational and security requirements
The server needs outbound internet connectivity (north-south traffic), but must not initiate lateral connections to adjacent internal systems (east-west traffic), including hosts on its local subnet.
Security controls must enforce granular isolation without severing required external communications.
2
Evaluate segmentation methodologies against lateral traffic control
Traditional subnets and perimeter DMZs permit uninspected traffic between hosts within the same VLAN/subnet. Air-gapping severs all connectivity including required internet access.
Microsegmentation abstracts security policies down to individual workloads or hypervisors, enabling zero-trust east-west filtering.
3
Select the optimal architecture control
Microsegmentation policies effectively isolate the host from lateral peers while permitting intended outbound paths.
This satisfies both PCI/enterprise compliance rules and functional requirements.

Anahtar Kavram

Microsegmentation and East-West Traffic Isolation
Soru 232Soru

A storage administrator is configuring security mechanisms for sensitive database volumes hosted on an enterprise Storage Area Network (SAN). The administrator needs to protect data at rest with hardware-accelerated bulk encryption and ensure that top-level encryption keys are managed in a tamper-resistant environment. Which of the following technologies should the administrator deploy? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Self-Encrypting Drives (SEDs) to perform automatic hardware-based disk encryption; Hardware Security Modules (HSMs) to generate and securely store root keying material

Cevap

The administrator should deploy Self-Encrypting Drives (SEDs) for hardware bulk encryption and Hardware Security Modules (HSMs) for root key management.
Deploying Self-Encrypting Drives (SEDs) ensures bulk data on physical media is transparently encrypted at rest with minimal performance impact. Utilizing Hardware Security Modules (HSMs) ensures master encryption keys are generated, stored, and managed inside dedicated, tamper-resistant cryptographic hardware.

Adım Adım Çözüm

1
Identify the requirement for hardware-accelerated bulk data encryption at rest.
Self-Encrypting Drives (SEDs) handle transparent, high-speed symmetric encryption at the drive controller level.
Bulk storage requires symmetric hardware ciphers like AES to maintain performance without host CPU overhead.
2
Identify the key management requirement for securing top-level encryption keys.
Hardware Security Modules (HSMs) isolate and safeguard key generation and key protection operations.
Centralized, tamper-resistant HSM devices ensure encryption keys are protected outside system memory.

Anahtar Kavram

Storage Security Architecture: Data at Rest Encryption and Key Management
Soru 233Soru

A financial enterprise is decommissioning a multi-tenant cloud storage array containing sensitive personally identifiable information (PII) stored across encrypted block volumes. The architecture relies on envelope encryption where unique Data Encryption Keys (DEKs) are wrapped by Key Encryption Keys (KEKs) managed inside a Key Management Interoperability Protocol (KMIP)-compliant Hardware Security Module (HSM). The compliance team mandates immediate, verifiable data sanitization before the physical storage media is recycled by the provider, but traditional multi-pass disk overwriting would exceed bandwidth limits and disrupt SAN performance. Which of the following storage security architectural approaches best satisfies these operational and compliance constraints?

Cevabı ve açıklamayı göster

Cevap: Perform cryptographic erasure by zeroizing and securely deleting the wrapping Key Encryption Keys from the central Hardware Security Module.

Cevap

Perform cryptographic erasure by zeroizing and securely deleting the wrapping Key Encryption Keys from the central Hardware Security Module.
Cryptographic erasure (crypto-shredding) is the process of deliberately deleting or zeroizing the cryptographic keys (specifically the KEKs or DEKs) used to protect encrypted data. In an envelope encryption architecture backed by an HSM, destroying the wrapping Key Encryption Key makes it mathematically impossible to recover the Data Encryption Keys or the block storage ciphertext, satisfying standards such as NIST SP 800-88 without generating heavy disk I/O.

Adım Adım Çözüm

1
Analyze operational and compliance requirements for storage media sanitization
Determined that physical overwrite operations (such as NIST 800-88 Clear/Purge via multi-pass zeroing) are unfeasible due to SAN throughput constraints.
Sanitization must be executed instantly at the cryptographic boundary.
2
Evaluate the key hierarchy within the envelope encryption model
DEKs encrypt the raw data blocks, while KEKs protect the DEKs within the HSM. Without access to the KEK, wrapped DEKs cannot be decrypted.
Destroying the root KEK permanently breaks the cryptographic trust chain.
3
Select Cryptographic Erasure (Crypto-Shredding) as the target control
Zeroizing key material in the KMIP HSM renders the data mathematically unrecoverable, fulfilling media sanitization requirements.
Crypto-shredding guarantees sanitization even if the physical media is later repurposed or retained by a third-party cloud provider.

Anahtar Kavram

Cryptographic Erasure (Crypto-Shredding) and Key Management Architecture
Soru 234Soru

A security administrator is documenting high-availability and business continuity metrics for an organization's core infrastructure. Match each availability metric on the left with its corresponding description on the right.

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

Öğeler

Recovery Time Objective (RTO)
Recovery Point Objective (RPO)
Mean Time Between Failures (MTBF)
Mean Time to Repair (MTTR)

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Recovery Time Objective (RTO) matches the maximum targeted duration to restore a system; Recovery Point Objective (RPO) matches the maximum acceptable amount of data loss measured in time; Mean Time Between Failures (MTBF) matches the average expected operational time between breakdowns; Mean Time to Repair (MTTR) matches the average duration required to troubleshoot and repair a failed component.
Recovery Time Objective (RTO) represents the target time to bring systems back online. Recovery Point Objective (RPO) defines maximum tolerated data loss measured in time. Mean Time Between Failures (MTBF) measures system component reliability and expected operational runtime between crashes. Mean Time to Repair (MTTR) quantifies the average duration needed to repair and restore a failed item.

Adım Adım Çözüm

1
Identify metrics measuring service recovery speed and acceptable data loss.
RTO focuses on duration until service availability is restored, while RPO focuses on acceptable data loss window.
Differentiating time-to-restore (RTO) from data loss tolerance (RPO) is essential for disaster recovery planning.
2
Identify metrics measuring hardware/system reliability and repair time.
MTBF measures expected operational uptime between failures, while MTTR measures the duration required to fix a failure.
Understanding hardware reliability metrics helps establish realistic availability baselines and SLA expectations.

Anahtar Kavram

Business Impact and High Availability Metrics
Tahmini Süre:1m 0s
Soru 235Soru

A biomedical engineering department at a regional hospital plans to integrate networked smart infusion pumps into the facility's network. To minimize the threat of malware spreading laterally from compromised medical devices to critical electronic health record (EHR) databases while still allowing automated telemetry collection by central servers, which network architecture control should the security team implement?

Cevabı ve açıklamayı göster

Cevap: Place the medical devices into an isolated network segment enforced by firewalls that restrict traffic solely to authorized telemetry collector endpoints.

Cevap

Place the medical devices into an isolated network segment enforced by firewalls that restrict traffic solely to authorized telemetry collector endpoints.
Placing the medical devices into a dedicated, firewall-enforced network segment (such as a restricted VLAN or microsegment) isolates potentially vulnerable hardware while permitting explicitly defined, unidirectional or limited telemetry traffic to monitoring servers. This enforces the principle of least privilege at the network level and contains lateral threat propagation.

Adım Adım Çözüm

1
Analyze the operational and security requirements
The medical devices require network connectivity for automated telemetry collection, but lateral access to sensitive EHR databases must be strictly prevented.
Security controls must balance operational availability with risk mitigation against lateral movement.
2
Evaluate segmentation strategies
Network segmentation via dedicated VLANs and stateful firewall policies isolates high-risk medical IoT equipment while allowing controlled East-West communications strictly to designated telemetry servers.
Proper zone isolation limits breach blast radiuses and prevents unauthorized lateral network traversal.

Anahtar Kavram

Secure Network Design and Segmentation
Soru 236Soru

A enterprise security architect is configuring an automated cross-region database failover workflow between two active-passive data centers to maintain zero Recovery Point Objective (RPO) and minimal Recovery Time Objective (RTO) during an ungraceful outage. Arrange the operational steps of the automated failover sequence in the correct chronological order from first step executed to final step completed.

Öğeleri doğru sıraya koymak için sürükleyin

Cevabı ve açıklamayı göster

Cevap

The correct operational sequence for automated database failover is: 1) Evaluate cluster quorum consensus via an independent witness site; 2) Execute node fencing (STONITH) to forcibly isolate the failed primary database; 3) Verify write-ahead log sequence numbers (LSN) on the standby node; 4) Promote the standby database instance to read-write state; 5) Update Global Server Load Balancing (GSLB) health checks and DNS records.
The sequence follows standard high-availability resiliency protocols: Cluster quorum must first be established to prevent split-brain, followed immediately by STONITH fencing of the legacy node. Once fenced, data consistency (LSN sync) must be verified on the target node before promoting it to primary. Finally, global network routing (GSLB/DNS) is updated to steer client traffic to the newly active environment.

Adım Adım Çözüm

1
Quorum Validation
Cluster consensus confirmed via witness node.
Prevents split-brain scenarios where both nodes concurrently assume primary role.
2
Node Fencing
Unresponsive primary node isolated and write privileges revoked.
Guarantees data integrity and prevents corrupting writes from a flapping primary server.
3
Log Sequence Synchronization Audit
Standby database confirms all synchronous transactions are committed.
Ensures adherence to the zero Recovery Point Objective (RPO) requirement before promotion.
4
Node Promotion
Secondary database becomes active write target.
Establishes a functional database primary capable of accepting new application transactions.
5
Traffic Redirection
GSLB points application requests to the newly promoted site.
Completes failover by restoring service availability to end clients.

Anahtar Kavram

High-Availability Failover & Fencing Sequences
Soru 237Soru

An enterprise organization operates two data centers connected via a low-latency dark fiber link. The business continuity requirement mandates a strict Recovery Point Objective of zero (RPO=0RPO = 0) for transactional database records during a primary site outage, while simultaneously preventing split-brain conditions during automated failover. Which of the following high-availability storage configurations best satisfies these requirements?

Cevabı ve açıklamayı göster

Cevap: Synchronous storage replication configured with an independent quorum witness node

Cevap

Synchronous storage replication configured with an independent quorum witness node provides real-time zero data loss (RPO = 0) across sites while avoiding split-brain split scenarios during automated failovers.
Synchronous storage replication guarantees that data is written to both storage systems before completing the transaction, satisfying the strict requirement of zero data loss (RPO=0RPO = 0). Adding a quorum witness node located outside the main data path provides cluster state verification, preventing split-brain conditions where both sites attempt to take control independently.

Adım Adım Çözüm

1
Analyze the RPO requirement
An RPO of zero (RPO=0RPO = 0) requires zero data loss, necessitating synchronous replication where write acknowledgments occur only after data is written to both primary and secondary storage targets.
Asynchronous methods acknowledge writes before secondary persistence, allowing data loss gaps.
2
Evaluate high availability and failover mechanism constraints
Automated multi-site failover requires a third-party witness or quorum device outside the two replication endpoints.
Without a quorum witness, network interruptions between sites cause both nodes to assume primary status, leading to data corruption via split-brain state.
3
Select the optimal architectural control
Synchronous replication with a quorum witness satisfies both zero data loss and safe failover constraints.
It addresses both the data preservation requirement (RPO=0RPO = 0) and the operational failover constraint.

Anahtar Kavram

Synchronous Replication and Quorum Clustering for Zero RPO High Availability
Soru 238Soru

An aerospace security architecture team is designing a satellite communications (SATCOM) avionics gateway for autonomous aircraft. The gateway will operate in environments susceptible to physical interception, probe attacks, and firmware tampering. To meet stringent safety standards, the hardware must establish an immutable boot verification chain and prevent physical extraction of secret keys stored in memory. Which TWO of the following hardware security controls should the team implement to satisfy these architecture requirements? (Select TWO)

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

Cevabı ve açıklamayı göster

Cevap: Integrating a hardware Root of Trust (RoT) backed by a Trusted Platform Module (TPM) to validate cryptographic measurements during every stage of the boot sequence.; Leveraging Physically Unclonable Functions (PUFs) to dynamically derive cryptographic keys from silicon micro-structure variations rather than storing static key material in non-volatile memory.

Cevap

The correct controls to implement are integrating a hardware Root of Trust backed by a Trusted Platform Module (TPM) for boot validation and leveraging Physically Unclonable Functions (PUFs) for tamper-resistant key generation.
Establishing a hardware Root of Trust (RoT) using a cryptoprocessor such as a Trusted Platform Module (TPM) ensures that every stage of boot firmware is verified against cryptographically secure measurement hashes before execution. Furthermore, Physically Unclonable Functions (PUFs) leverage unique semiconductor manufacturing variations to generate cryptographic keys dynamically, preventing attackers from physically extracting static keys from non-volatile memory via chip decapsulation or microprobing.

Adım Adım Çözüm

1
Identify the core security requirements established in the scenario.
The requirements are establishing an immutable boot verification chain and protecting cryptographic keys from physical memory extraction and reverse engineering.
Hardware security architecture requires aligning specific physical mechanisms with their corresponding threat vectors.
2
Evaluate mechanisms for establishing an immutable boot verification chain.
A Trusted Platform Module (TPM) providing a hardware Root of Trust (RoT) measures and validates each stage of the boot sequence (Secure Boot / Measured Boot).
Hardware-level cryptoprocessors enforce trust starting at power-on before any untrusted software runs.
3
Evaluate mechanisms for securing cryptographic key storage against physical extraction.
Physically Unclonable Functions (PUFs) generate unique cryptographic keys on the fly using tiny manufacturing variations in the silicon chip, eliminating the need to store static keys in flash or EEPROM memory.
If physical keys are never stored at rest in memory circuits, physical probing or decap attacks cannot extract them.

Anahtar Kavram

Hardware Root of Trust & Silicon-Level Key Protection
Tahmini Süre:2m 0s
Soru 239Soru

An enterprise security team is upgrading its data protection and storage security architecture to protect sensitive databases and block storage volumes across on-premises SAN and cloud environments. The architect needs to implement controls that ensure centralized key governance for encrypted storage, isolate storage network traffic to authorized hosts, and prevent unauthorized exfiltration of sensitive files from endpoints. Which of the following technical controls should the architect implement to meet these storage security requirements? (Select THREE)

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

Cevabı ve açıklamayı göster

Cevap: Deploy dedicated Hardware Security Modules (HSMs) to manage master encryption keys and secure volume envelope encryption key hierarchies.; Configure Storage Area Network (SAN) LUN masking and Fibre Channel zoning to restrict logical unit access strictly to authorized servers.; Deploy endpoint Data Loss Prevention (DLP) agents to monitor, detect, and block unauthorized copying of sensitive storage data to removable media or cloud shares.

Cevap

The enterprise must deploy Hardware Security Modules (HSMs) for centralized encryption key governance, configure SAN LUN masking and Fibre Channel zoning for storage access isolation, and implement endpoint Data Loss Prevention (DLP) agents to prevent unauthorized data exfiltration.
Hardware Security Modules (HSMs) safeguard master cryptographic keys used in envelope encryption for storage volumes. SAN LUN masking and Fibre Channel zoning provide network and logical isolation ensuring only authorized servers mount specific storage drives. Endpoint Data Loss Prevention (DLP) inspects file actions and blocks unauthorized data exfiltration.

Adım Adım Çözüm

1
Identify key management requirements for storage encryption
Deploying an HSM provides secure, centralized storage and lifecycle management for volume encryption keys.
Bulk storage encryption relies on robust master key management to prevent key exposure.
2
Determine storage network segmentation and access control mechanisms
Configuring Fibre Channel zoning and SAN LUN masking restricts host connectivity to explicitly assigned storage logical units.
Without isolation, unauthorized SAN hosts could access sensitive block storage volumes.
3
Select data exfiltration prevention controls for endpoints
Deploying endpoint DLP monitors and enforces policy rules on sensitive files stored on endpoints.
DLP inspects data contents and prevents unauthorized transfers to external media or network locations.

Anahtar Kavram

Data Protection and Storage Security Architecture Controls
Soru 240Soru

An enterprise security architecture team is evaluating cloud deployment and service models for a multi-cloud initiative. Match each operational requirement on the left with the most appropriate cloud architecture or service model on the right.

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

Öğeler

Deploying a highly customized legacy database requiring direct control over hypervisor settings, hardware isolation, and dedicated host resources.
Developing customer-facing web services where the cloud provider maintains the underlying runtime, operating system patching, and web server framework.
Executing transient, event-driven payment processing code that scales automatically without maintaining active server instances.
Sharing a specialized regional threat intelligence pool co-hosted and governed by several partner financial institutions under common regulatory compliance standards.

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

1. Custom legacy database requiring physical host isolation -> Private Cloud (IaaS); 2. Web services with provider-managed runtime and OS patching -> Platform as a Service (PaaS); 3. Transient event-driven code execution -> Serverless (FaaS); 4. Co-hosted platform shared by partner financial institutions -> Community Cloud.
Matching each requirement accurately aligns business demands with cloud service abstraction boundaries. Private Cloud (IaaS) provides dedicated hardware control; PaaS offloads OS/runtime maintenance while hosting persistent apps; Serverless (FaaS) executes code transiently without server management; and Community Cloud serves multi-organizational groups sharing specific compliance and functional goals.

Adım Adım Çözüm

1
Analyze the hardware and control requirements for the database scenario.
Identified direct hardware control, hypervisor management, and physical isolation as characteristics of Private Cloud (IaaS).
IaaS provides maximum architectural control to the organization, while private deployment guarantees dedicated isolation.
2
Evaluate the management boundary for web services with managed runtime and OS patching.
Identified abstraction of OS and runtime environment as characteristics of PaaS.
Under PaaS, the provider handles infrastructure maintenance and middleware, leaving application code to the consumer.
3
Examine the operational mechanics of transient event-triggered microservices.
Matched zero-server management and event execution to Serverless (FaaS).
FaaS abstracts server instances completely, executing logic on demand in response to events.
4
Determine the cloud deployment model for joint industry collaboration under common compliance standards.
Matched shared infrastructure between partner institutions to Community Cloud.
Community clouds are designed for multi-tenant access restricted to organizations bound by shared mission goals or compliance standards.

Anahtar Kavram

Cloud Deployment Models and Shared Responsibility Boundaries
ÖncekiSayfa 12 / 21Sonraki
Security Architecture Alıştırma Soruları — CompTIA Security+ — Sayfa 12 | Examkin