Examkin

Security Architecture

405 questions

All types405Multiple choice207Multiple select87Matching93Ordering18
Question 341Question →

An organization experiences an unexpected municipal power grid failure at its primary data center. Although the rack-mounted Uninterruptible Power Supply (UPS) units immediately supplied emergency battery power to critical servers, all systems abruptly shut down 15 minutes later when the batteries depleted. An investigation revealed that the facility's backup diesel generator successfully started, but utility power was never switched over to generator power. Which of the following components should the security architect install to automate switching between primary utility power and secondary generator power?

Show answer & explanation

Answer: Automatic Transfer Switch (ATS)

Answer

The Automatic Transfer Switch (ATS) is the correct component because it automatically detects a loss of primary utility power and transfers the electrical load to the backup generator.
An Automatic Transfer Switch (ATS) monitors incoming utility power feeds. When primary power drops, the ATS signals the generator to start (if not already running) and automatically switches the electrical load from the dead utility feed to the operational generator feed, preventing UPS battery exhaustion.

Step-by-Step Solution

1
Analyze the incident details
Identified that UPS battery power functioned properly and the backup generator started, but grid power failed to transition to generator power.
The failure occurred at the power transition layer between grid utility and generator.
2
Evaluate power resilience controls
An Automatic Transfer Switch (ATS) is specifically designed to sense utility power loss and toggle electrical feeds to the emergency generator.
Installing an ATS automates the changeover process without human intervention before UPS batteries drain.

Key Concept

Power Resiliency and Environmental Redundancy Controls
Estimated Time:1m 15s
Question 342Question →

A security architect is designing hardware-level protections for unattended retail payment kiosks deployed in public environments. To protect payment encryption keys against physical memory extraction and ensure that only authenticated firmware executes during startup, which of the following hardware security controls should be implemented? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Integrate a Cryptographic Co-processor equipped with active physical tamper detection and key zeroization capabilities.; Establish a hardware Root of Trust using a Trusted Platform Module to measure and validate each stage of the bootloader.

Answer

The correct controls are integrating a Cryptographic Co-processor with active physical tamper detection and key zeroization, and establishing a hardware Root of Trust using a Trusted Platform Module to measure and validate boot phases.
Protecting unattended hardware requires physical and firmware-level controls. Active physical tamper detection circuitry automatically zeroizes stored cryptographic keys when physical intrusion occurs. Concurrently, a hardware Root of Trust combined with a Trusted Platform Module provides Measured Boot and Secure Boot verification to ensure that only digitally signed, verified firmware is loaded at boot time.

Step-by-Step Solution

1
Analyze physical memory protection requirements
Identify that physical tamper detection and hardware zeroization are required to protect cryptographic keys when hardware is physically breached.
Unattended field hardware is susceptible to decapsulation and direct probe attacks.
2
Analyze firmware boot integrity requirements
Identify that a hardware Root of Trust and TPM are required to validate firmware signatures prior to execution.
Secure Boot prevents unauthorized or malicious code execution during system startup.

Key Concept

Hardware-Based Root of Trust and Physical Tamper Resistance
Estimated Time:1m 30s
Question 343Question →

A network architect is designing a high-availability edge network infrastructure for a regional operational facility. The architecture must ensure continuous default gateway availability for local internal hosts and dynamic, redundant routing across two independent upstream Internet Service Providers (ISPs). Which of the following resilience mechanisms should the architect deploy to fulfill these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Virtual Router Redundancy Protocol (VRRP) to present a shared virtual default gateway address across redundant local routers; Border Gateway Protocol (BGP) multi-homing to dynamically announce routes and balance traffic across both ISP links

Answer

The architect should deploy Virtual Router Redundancy Protocol (VRRP) to supply a virtual default gateway for local hosts and Border Gateway Protocol (BGP) multi-homing to manage dynamic path redundancy across external ISP connections.
High availability at the network layer requires redundancy at both the internal first-hop gateway level and the external WAN routing level. Virtual Router Redundancy Protocol (VRRP) groups local physical routers together under a virtual IP address, providing immediate gateway failover for clients on the subnet. Meanwhile, BGP multi-homing negotiates dynamic routing across separate service providers, enabling path failover and traffic distribution over external connections.

Step-by-Step Solution

1
Analyze local gateway availability requirements.
Identified that local hosts require a single resilient gateway IP address that remains reachable if a router fails.
First-hop redundancy protocols like VRRP enable multiple physical routers to share a single virtual IP and MAC address, facilitating seamless failover.
2
Analyze external WAN path redundancy requirements.
Identified that outbound traffic needs dynamic failover across two separate upstream ISPs.
BGP multi-homing maintains active routing tables with both service providers, dynamically redirecting traffic away from an unresponsive ISP link.
3
Evaluate invalid options based on scope mismatch.
Eliminated disk array mirroring (RAID 10) and offsite tape backups.
Local disk redundancy protects against drive crashes on a single host, and offline backups support disaster recovery restoration, but neither provides active high-availability network path redundancy.

Key Concept

First-hop router redundancy and dynamic multi-homing routing protocols for network-level resilience and high availability.
Estimated Time:1m 30s
Question 344Question →

An enterprise security architecture team is categorizing identity standards and protocols for a multi-cloud infrastructure deployment. Match each Identity and Access Management (IAM) protocol or standard on the left to its corresponding architectural use case on the right.

Click a left item, then click its matching right item

Items

SAML 2.0
OpenID Connect (OIDC)
OAuth 2.0
RADIUS

Matches

Show answer & explanation

Answer

SAML 2.0 matches XML-based web SSO federation; OpenID Connect matches the JWT identity layer for user authentication; OAuth 2.0 matches the delegated authorization API token framework; RADIUS matches the centralized network access control protocol.
Each IAM protocol is paired with its exact architectural design pattern: SAML 2.0 uses XML for web SSO federation, OpenID Connect uses JWT ID tokens for user identity verification, OAuth 2.0 delivers token-based authorization delegated access for APIs, and RADIUS supplies UDP-based AAA network connection management.

Step-by-Step Solution

1
Identify the primary architectural transport and payload structure for web federation
Matched SAML 2.0 with XML-based web single sign-on federation.
SAML 2.0 relies on XML security assertions transferred via browser HTTP bindings for enterprise web SSO.
2
Differentiate delegated access from user authentication in modern API-driven architectures
Matched OAuth 2.0 with delegated API authorization access tokens, and OpenID Connect with JWT-based user identity authentication.
OAuth 2.0 strictly governs API resource authorization using tokens, whereas OpenID Connect adds an identity authentication layer on top using ID tokens.
3
Categorize network-level AAA protocols
Matched RADIUS to centralized network device and remote access authentication over UDP.
RADIUS is a legacy AAA protocol operating over UDP, dedicated to network perimeter access controls like 802.1X and VPNs.

Key Concept

Identity and Access Management Architecture and Protocol Selection
Question 345Question →

A software enterprise is redesigning access controls for its third-party developer API integration portal. Currently, after external developers authenticate through a legacy VPN connection, their sessions are implicitly trusted across internal staging systems. The enterprise wants to modernize this architecture to align with Zero Trust Architecture (ZTA) principles. Which of the following strategies best implements Zero Trust for these third-party developer connections?

Show answer & explanation

Answer: Deploy a Policy Decision Point (PDP) to continuously evaluate context and device posture, instructing a Policy Enforcement Point (PEP) to grant explicit, minimal access to specific API resources.

Answer

Deploying a Policy Decision Point (PDP) to continuously evaluate context and device posture, instructing a Policy Enforcement Point (PEP) to grant explicit, minimal access to specific API resources.
Zero Trust Architecture relies on explicit verification, continuous dynamic evaluation, and least privilege access. Decoupling access control into a Policy Decision Point (PDP) that dynamically evaluates context (such as identity, threat intelligence, and device health) and directs a Policy Enforcement Point (PEP) to gate resource access embodies core NIST SP 800-207 Zero Trust principles.

Step-by-Step Solution

1
Analyze current access model limitations
Identified implicit trust after initial VPN authentication as a violation of Zero Trust architecture.
Zero Trust assumes the network is hostile and rejects implicit trust based on network location or past authentication.
2
Identify core Zero Trust control components required for access governance
Determined that access decisions must be separated into a Policy Decision Point (PDP) and enforced via a Policy Enforcement Point (PEP).
NIST SP 800-207 specifies that the PDP evaluates policies continuously while the PEP gates actual resource access.
3
Select the option enforcing continuous verification and least privilege
The architecture using PDP and PEP for continuous contextual authorization fulfills Zero Trust principles.
This strategy ensures every request is explicitly authenticated, authorized, and dynamically evaluated based on risk.

Key Concept

Zero Trust Architecture Control Plane Decoupling and Continuous Explicit Verification
Question 346Question →

A healthcare organization is updating its enterprise Identity and Access Management (IAM) architecture to support dynamic, fine-grained access control across decoupled microservices. The security team requires a centralized component that evaluates contextual attributes—such as user role, device posture, time of day, and resource sensitivity—against security policies to issue an authorization decision for each access request. Which architectural component directly performs this policy evaluation to determine whether access should be granted?

Show answer & explanation

Answer: Policy Decision Point (PDP)

Answer

Policy Decision Point (PDP)
The Policy Decision Point (PDP) is the architectural entity in Attribute-Based Access Control (ABAC) and Zero Trust architectures responsible for receiving authorization requests, evaluating them against configured access policies and environmental attributes, and issuing a definitive permit or deny decision.

Step-by-Step Solution

1
Analyze the architectural requirements stated in the scenario.
The requirement calls for a component that evaluates access policies against context attributes to issue an authorization decision.
Decoupling policy evaluation from enforcement allows centralized management of fine-grained authorization rules.
2
Differentiate between XACML/ABAC architecture roles (PDP vs. PEP vs. IdP).
The Policy Decision Point (PDP) performs logic processing and rule evaluation, while the Policy Enforcement Point (PEP) intercepts and enforces the decision.
The question specifically asks for the component that evaluates policies and issues the decision.

Key Concept

Attribute-Based Access Control (ABAC) and Policy Decision Point (PDP) Architecture
Question 347Question →

A logistics company is deploying telemetry edge devices on freight vehicles. To protect against unauthorized firmware tampering, the systems engineer must guarantee that the microcontroller only executes cryptographically signed boot code during power-on. Which hardware security control serves as the immutable foundation to perform this initial integrity verification?

Show answer & explanation

Answer: A hardware Root of Trust (RoT) embedded within read-only memory (ROM) on the system-on-chip

Answer

A hardware Root of Trust (RoT) embedded within read-only memory (ROM) on the system-on-chip
A hardware Root of Trust (RoT) stored in immutable ROM on the system-on-chip provides the essential cryptographic anchor. Because code stored in ROM cannot be altered after manufacture, it reliably verifies the digital signature of the initial bootloader before execution, establishing a secure chain of trust.

Step-by-Step Solution

1
Identify the primary requirement
The scenario requires an immutable hardware-based anchor to verify cryptographic signatures of boot code at power-on.
Preventing unauthorized firmware execution requires an unalterable trust foundation prior to running any soft code.
2
Evaluate hardware vs software security controls
Software-based storage in flash memory or network filtering can be bypassed or overwritten, whereas hardware ROM cannot be modified after manufacturing.
An immutable foundation must exist in read-only hardware to validate subsequent stages in the secure boot chain.

Key Concept

Hardware Root of Trust and Secure Boot
Question 348Question →

Match each core Zero Trust Architecture (ZTA) functional component to its primary operational responsibility within an enterprise security infrastructure.

Click a left item, then click its matching right item

Items

Policy Engine (PE)
Policy Administrator (PA)
Policy Enforcement Point (PEP)
Continuous Diagnostics and Mitigation (CDM)

Matches

Show answer & explanation

Answer

Policy Engine pairs with evaluating security policies and context to render access decisions. Policy Administrator pairs with issuing control commands and managing session tokens. Policy Enforcement Point pairs with intercepting traffic and enforcing data plane connections. Continuous Diagnostics and Mitigation pairs with gathering asset posture and vulnerability telemetry.
Zero Trust Architecture explicitly separates control plane operations from data plane execution. The Policy Engine determines access authorization, the Policy Administrator handles control signaling and session token distribution, the Policy Enforcement Point gates data plane traffic, and Continuous Diagnostics and Mitigation feeds real-time posture intelligence to inform ongoing access evaluations.

Step-by-Step Solution

1
Differentiate between policy decision logic and control plane session management.
Identify that the Policy Engine evaluates policy rules to make the access decision, while the Policy Administrator acts on that decision to manage session controls.
Decoupling decision logic (PE) from execution signals (PA) ensures strict separation of duties within the control plane.
2
Identify the operational boundary component handling active user traffic.
Associate the Policy Enforcement Point with direct data plane traffic inspection, gating, and session termination.
The PEP acts as the perimeter-less gatekeeper directly between the requester and enterprise workload.
3
Identify the supporting telemetry system providing contextual state data.
Associate Continuous Diagnostics and Mitigation with tracking endpoint compliance, patch levels, and device integrity.
Zero Trust demands explicit, continuous verification supported by ongoing threat and posture monitoring systems.

Key Concept

Zero Trust Architecture Functional Component Roles (NIST SP 800-207)
Estimated Time:1m 30s
Question 349Question →

A cloud security architect is evaluating a high-availability strategy for a critical online payment application. The application requires near-zero Recovery Time Objective (RTO) and real-time transaction consistency across two distinct cloud regions. A system administrator proposes using asynchronous database replication paired with automated failover via DNS routing, but without implementing a third-site witness or quorum node. Which of the following risks is MOST likely to occur if a network partition isolates the primary region while servers in both regions remain fully operational?

Show answer & explanation

Answer: A split-brain scenario where database nodes in both regions assume the primary role and accept writes concurrently, causing severe data inconsistency.

Answer

A split-brain scenario where database nodes in both regions assume the primary role and accept writes concurrently, causing severe data inconsistency.
In high-availability multi-region cluster design, a split-brain condition occurs when a network partition breaks communication between nodes while both remain powered on. Without a third-site witness or odd-numbered quorum cluster to establish majority consensus, both nodes believe the other has failed and simultaneously assume the active role, accepting conflicting data writes.

Step-by-Step Solution

1
Analyze the architecture components and failure condition.
Two cloud regions are connected via asynchronous replication without a quorum/witness server, and a network partition breaks inter-region communication while both sites stay online.
When the heartbeat/replication link between two isolated sites drops, each site must determine whether the other site is down or simply unreachable.
2
Evaluate how active-passive high availability systems behave without a quorum mechanism.
Because neither site can communicate with the other and there is no third-party witness to break the tie, both nodes assume the peer is dead.
Without quorum or majority voting, both nodes promote themselves to active status.
3
Determine the impact of dual active nodes accepting concurrent writes.
Both instances accept user transactions independently, creating divergent database states that lead to data corruption when connectivity is restored (split-brain condition).
Split-brain is the primary high-availability failure mode when heartbeats fail across isolated active-passive nodes without quorum.

Key Concept

High Availability Quorum and Split-Brain Conditions
Estimated Time:1m 30s
Question 350Question →

A systems engineer is hardening enterprise endpoints, embedded controllers, and server infrastructure. Match each hardware security feature on the left with its primary operational function on the right.

Click a left item, then click its matching right item

Items

Trusted Platform Module (TPM)
Hardware Security Module (HSM)
Physically Unclonable Function (PUF)
eFuse

Matches

Show answer & explanation

Answer

Trusted Platform Module (TPM) pairs with local endpoint integrity measurements and host key storage. Hardware Security Module (HSM) pairs with centralized high-volume cryptographic processing. Physically Unclonable Function (PUF) pairs with deriving unique device keys from silicon manufacturing variations. eFuse pairs with permanently locking hardware configurations via one-time programmable physical blown traces.
Each hardware security feature corresponds strictly to its targeted operational profile: TPM provides endpoint host boot measurement; HSM handles centralized server cryptographic acceleration; PUF generates unique chip keys based on physical silicon variations; and eFuse permanently alters chip capabilities by burning physical internal fuses.

Step-by-Step Solution

1
Differentiate endpoint-focused hardware roots of trust from server-centric cryptographic appliances.
TPM is identified as an endpoint-level crypto microcontroller for boot integrity, whereas HSM is identified as an enterprise device for server key management.
TPMs are deployed locally on client systems, while HSMs serve high-availability, multi-tenant server infrastructure.
2
Distinguish between silicon fingerprint generation and permanent circuit path modification.
PUF relies on intrinsic silicon variations to derive secret keys, whereas eFuse physically alters internal micro-wiring to permanently set configurations.
PUF yields dynamic identity evaluation without stored keys, while eFuses act as irreversible state controls.

Key Concept

Hardware-based security controls and roots of trust
Question 351Question →

A regional healthcare network is redesigning its infrastructure to align with Zero Trust Architecture (ZTA) principles for biomedical IoT equipment, such as infusion pumps and vital sign monitors. Historically, once a biomedical device successfully completed initial 802.1X authentication on an internal switch port, it was granted persistent trust and unmonitored network access to servers containing electronic health records (EHR). Which of the following implementations best fulfills the Zero Trust requirement for resource access control in this scenario?

Show answer & explanation

Answer: Positioning a Policy Enforcement Point (PEP) to gate all access requests and dynamically enforce decisions made by the Policy Engine based on continuous assessment of device state and context.

Answer

Positioning a Policy Enforcement Point (PEP) to gate all access requests and dynamically enforce decisions made by the Policy Engine based on continuous assessment of device state and context.
The core tenets of Zero Trust Architecture (as defined in NIST SP 800-207) mandate that all communication is secured regardless of network location, access to resources is granted on a per-session basis, and access rights are determined dynamically by a Policy Engine and enforced by a Policy Enforcement Point (PEP). Implementing a PEP to gate resource requests based on continuous evaluation of device health and context fulfills these requirements.

Step-by-Step Solution

1
Analyze the legacy architecture vulnerability in the scenario.
The current model relies on implicit trust following an initial port-level authentication check.
Zero Trust assumes breach and dictates that no device or traffic flow should be implicitly trusted based on its network location or prior authentication.
2
Evaluate Zero Trust Architecture architectural components (NIST SP 800-207).
Access decisions must be evaluated by a Policy Engine/Policy Administrator (Policy Decision Point) and enforced per request by a Policy Enforcement Point (PEP).
Every resource request must be explicitly verified, evaluating device posture, user context, and transaction threat level before granting access.
3
Identify the option that enforces continuous explicit verification and PEP placement.
The approach placing a PEP to gate requests based on dynamic evaluation by the Policy Engine directly aligns with ZTA requirements.
This guarantees microsegmentation, explicit verification, and continuous risk assessment.

Key Concept

Zero Trust Policy Decision Point (PDP) and Policy Enforcement Point (PEP) Architecture
Question 352Question →

An organization is updating its enterprise access architecture to grant external partner employees access to web applications hosted in a private cloud. The security team requires a federated identity solution that allows partners to authenticate using their own Identity Provider (IdP) and transmit digitally signed XML security assertions to the relying application without syncing credentials or exposing internal directory endpoints. Which of the following identity standards should the security team implement?

Show answer & explanation

Answer: Security Assertion Markup Language (SAML)

Answer

Security Assertion Markup Language (SAML) is the correct selection because it uses digitally signed XML tokens transmitted over HTTP to establish cross-organizational web single sign-on without sharing account passwords.
Security Assertion Markup Language (SAML) is the standard protocol for web-based federated single sign-on (SSO). It allows an Identity Provider (IdP) to authenticate a user and securely pass digitally signed XML security assertions to a Service Provider (SP) via standard HTTP browser redirections, enabling secure cross-organizational access without sharing or synchronizing user credentials.

Step-by-Step Solution

1
Analyze the functional requirements of the identity architecture scenario.
The scenario requires cross-organizational federation, web application support, use of digitally signed XML assertions, and zero user credential synchronization.
Identifying protocol requirements filters out legacy network AAA and centralized directory query protocols.
2
Evaluate candidate protocols against XML assertion and web federation criteria.
SAML (Security Assertion Markup Language) specifically uses XML formatted security assertions generated by an IdP to authorize user sessions at a Service Provider.
SAML is the standard open format for browser-based federated SSO utilizing XML payloads.

Key Concept

Federated Identity Architecture and Web Single Sign-On (SAML)
Estimated Time:1m 0s
Question 353Question →

A global telecommunications enterprise is migrating its remote network maintenance infrastructure to align with Zero Trust Architecture (ZTA) principles. Field engineers require frequent administrative access to edge router control planes located across dispersed datacenters. Which of the following architectural requirements must be satisfied to uphold core Zero Trust tenets? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Continuous verification of user identity, device posture, and contextual risk factors throughout the duration of each administrative session.; Microsegmentation and least-privilege policy enforcement applied strictly at the individual resource boundary.

Answer

The correct requirements are continuous verification of user identity, device posture, and contextual risk factors throughout each session, as well as microsegmentation and least-privilege policy enforcement applied strictly at the individual resource boundary.
Zero Trust Architecture mandates explicit, continuous verification of identity, device health, and environmental context throughout the duration of a session, combined with microsegmentation and least-privilege access to minimize lateral movement.

Step-by-Step Solution

1
Analyze the scenario against Zero Trust Architecture core principles.
Zero Trust requires explicit verification, assumed breach mindset, continuous evaluation, and least-privilege access regardless of network location.
Traditional perimeter security models that implicitly trust internal network traffic fail to mitigate lateral threat movement.
2
Evaluate the requirement for continuous authentication and contextual authorization.
Session access must be continually evaluated using identity, endpoint posture, and contextual risk signals.
Initial authentication alone is insufficient because device risk posture or user context can change during an active session.
3
Evaluate the requirement for network control boundaries.
Enforcing microsegmentation and resource-level access control limits blast radius and enforces least privilege.
Granular resource-level boundaries prevent lateral movement across enterprise segments.

Key Concept

Zero Trust Architecture Principles (Continuous Verification & Microsegmentation)
Question 354Question →

An enterprise data center security team is deploying new high-density rack servers equipped with Baseboard Management Controllers (BMCs). To protect against persistent firmware-level compromise, the security architect must ensure that the BMC initial boot code cannot be altered and that attackers cannot downgrade the firmware to a previously signed version containing known security vulnerabilities. Which of the following hardware security mechanisms should the architect specify to fulfill these requirements?

Show answer & explanation

Answer: Hardware Root of Trust anchored in One-Time Programmable (OTP) eFuses with anti-rollback version tracking

Answer

Hardware Root of Trust anchored in One-Time Programmable (OTP) eFuses with anti-rollback version tracking
Establishing a hardware Root of Trust (RoT) anchored in One-Time Programmable (OTP) eFuses ensures that the initial boot code validation key is burned directly into silicon during manufacturing and cannot be altered. When combined with eFuse-backed anti-rollback version counters, the processor compares the version number of any incoming firmware against the hardware counter. If an attacker attempts to flash an older, vulnerable firmware version (even if validly signed by the vendor in the past), the hardware anti-rollback check fails and halts execution.

Step-by-Step Solution

1
Analyze the scenario requirements
Identified two primary hardware protection needs: immutable boot integrity verification and protection against firmware version downgrade attacks on out-of-band controllers.
Baseboard Management Controllers run low-level microcode that requires hardware-backed verification to prevent rootkits.
2
Evaluate hardware security mechanisms for boot integrity and anti-rollback
One-Time Programmable (OTP) eFuses store cryptographically hashed keys permanently in silicon, establishing an unalterable Root of Trust (RoT). eFuse counters are blown during firmware updates to enforce anti-rollback.
Software-based or flash-based storage can be overwritten, whereas eFuses cannot be reversed once blown.
3
Differentiate correct hardware control from network, detective, or symmetric crypto alternatives
Select the option that combines hardware Root of Trust via OTP eFuses with anti-rollback logic.
Network controls (NIPS), detective controls (SIEM), and symmetric keys in flash do not provide immutable hardware boot chain validation.

Key Concept

Hardware Root of Trust and Anti-Rollback Protection
Estimated Time:1m 30s
Question 355Question →

An organization is redesigning its database architecture to maintain continuous uptime for a critical online transaction system. The system requires continuous availability even if an entire database server experiences a hardware controller or motherboard failure. The infrastructure team suggests installing a hardware RAID 10 array on a single database server, claiming this will meet the high availability requirement without needing additional server nodes. Which of the following best explains why this proposed solution fails to satisfy the requirement?

Show answer & explanation

Answer: RAID 10 provides storage disk fault tolerance on a single system, but it cannot prevent system downtime caused by a total server hardware failure.

Answer

RAID 10 provides storage disk fault tolerance on a single system, but it cannot prevent system downtime caused by a total server hardware failure.
High availability requires removing single points of failure across all infrastructure components. While RAID 10 protects against the failure of individual hard drives or solid-state drives within a chassis, the server itself remains a single point of failure. If the server motherboard, power supply, or RAID controller fails, the database becomes completely unavailable. To achieve host-level resilience, the architecture must include multi-node redundancy, such as a high-availability database cluster.

Step-by-Step Solution

1
Analyze the availability requirement in the scenario.
The system must survive a total host hardware failure (e.g., motherboard or power supply crash) without system downtime.
High availability at the host level requires multi-node clustering or failover redundancy.
2
Evaluate the capabilities and limits of RAID 10.
RAID 10 combines disk mirroring and striping to tolerate individual drive failures within a single server chassis.
RAID operates strictly at the local storage layer and cannot keep services online if the host machine itself powering the RAID controller crashes.
3
Select the option that correctly identifies the single point of failure.
Highlighting that local drive redundancy does not eliminate server-level single points of failure directly addresses the gap in the proposal.
True high availability against server outages requires redundant physical nodes, such as active-active or active-passive database clustering.

Key Concept

High Availability vs. Storage Redundancy
Estimated Time:1m 15s
Question 356Question →

A software engineering team is developing a backend service that must automatedly transmit sensitive transaction audit logs to an external analytics vendor's endpoint. The security team specifies that the integration must eliminate static, long-lived API keys in application configuration files and support short-lived, cryptographically verifiable tokens for machine-to-machine authentication. Which of the following identity and access management architecture solutions should be implemented to satisfy these requirements?

Show answer & explanation

Answer: Implement OAuth 2.0 Client Credentials Grant to request short-lived JSON Web Tokens (JWTs) directly from the vendor's authorization server.

Answer

Implementing OAuth 2.0 Client Credentials Grant with short-lived JSON Web Tokens (JWTs) issued by the vendor's authorization server provides secure, automated machine-to-machine authentication without static credentials.
The correct solution uses the OAuth 2.0 Client Credentials grant, which allows a client service to authenticate directly with an authorization server using its client credentials and obtain a short-lived JSON Web Token (JWT). This satisfies both the machine-to-machine automation requirement and the security policy prohibiting static long-lived keys.

Step-by-Step Solution

1
Analyze the authentication context requirements
Identified a machine-to-machine (M2M) automated interaction requirement without human user interaction.
Different IAM flows are tailored for interactive user authentication versus automated backend service authorization.
2
Evaluate token management and credential life-cycle constraints
Determined that static API keys must be replaced with short-lived, cryptographically signed tokens.
Short-lived tokens limit the exposure window if a credential is compromised and remove stored secrets from application source files.
3
Select the appropriate IAM protocol for non-interactive backend authorization
Chose OAuth 2.0 Client Credentials grant generating short-lived JWTs.
Client Credentials grant is the industry-standard IAM architecture pattern for service-to-service access control.

Key Concept

Machine-to-Machine (M2M) Authentication and OAuth 2.0 Client Credentials Grant
Question 357Question →

An enterprise security architect is designing an Identity and Access Management (IAM) framework to address several distinct security requirements across a hybrid cloud environment. Match each IAM architectural mechanism on the left with its corresponding enterprise use case on the right.

Click a left item, then click its matching right item

Items

Ephemeral Credential Broker (Just-In-Time Access)
Vaulted Credential Session Proxy
SCIM-Based Dynamic Provisioning Engine
Certificate-Based Workload mTLS Architecture

Matches

Show answer & explanation

Answer

Ephemeral Credential Broker matches short-lived cloud permissions. Vaulted Credential Session Proxy matches isolating administrative sessions and obfuscating root passwords. SCIM-Based Dynamic Provisioning Engine matches user lifecycle identity synchronization. Certificate-Based Workload mTLS Architecture matches service-to-service authentication for zero-trust microsegments.
Each IAM architecture mechanism directly addresses its respective enterprise design goal: Ephemeral Brokers enable short-lived Just-In-Time access; Session Proxies secure and audit legacy administrator credentials without revealing passwords; SCIM automates account lifecycle management across external platforms; and Workload mTLS enforces mutual cryptographic authentication in microservice networks.

Step-by-Step Solution

1
Analyze the IAM architectural mechanisms to determine their functional capabilities.
Categorized mechanisms into short-lived authorization (ephemeral broker), privileged account proxying (session proxy), user identity lifecycle management (SCIM), and machine identity authentication (mTLS).
Evaluating core capabilities allows proper mapping to security requirements.
2
Match each control mechanism to the enterprise scenario that explicitly requires its technical implementation.
Aligned temporary permissions with JIT brokers, legacy session recording with vault proxies, identity synchronization with SCIM, and zero-trust workload traffic security with mTLS.
Ensures architectural alignment between IAM security controls and specific enterprise operational requirements.

Key Concept

Identity and Access Management Architecture Controls and Protocols
Question 358Question →

A security architect is establishing high availability guidelines for enterprise infrastructure. Which architectural control specification best matches each resilience technology?

Click a left item, then click its matching right item

Items

NIC Teaming
Geographic Dispersal
Active-Passive Clustering
Multipath I/O (MPIO)

Matches

Show answer & explanation

Answer

NIC Teaming matches adapter-level link aggregation; Geographic Dispersal matches distribution across geographically separate facilities; Active-Passive Clustering matches a primary active node with an idle standby node; Multipath I/O matches redundant physical paths between server hardware and storage arrays.
Each high-availability control is mapped to its appropriate architectural scope: NIC Teaming operates at the network interface layer, Geographic Dispersal mitigates site-level operational risks, Active-Passive Clustering manages compute failover using a dedicated standby node, and Multipath I/O ensures continuous storage fabric availability.

Step-by-Step Solution

1
Identify network interface redundancy controls
Match NIC Teaming to the aggregation of physical network interfaces for adapter failover.
NIC Teaming specifically handles network interface card and link redundancy.
2
Identify site-level resilience mechanisms
Associate Geographic Dispersal with distributing assets across separate physical regions.
Physical separation protects against wide-area site outages.
3
Evaluate high-availability cluster failover modes
Map Active-Passive Clustering to the configuration where a standby secondary node waits for primary node failure.
Active-passive nodes do not process active workloads simultaneously.
4
Analyze storage bus interface redundancy mechanisms
Link Multipath I/O (MPIO) to redundant hardware channels between host servers and SAN storage controllers.
MPIO protects against storage bus, Fibre Channel HBA, or cable disruptions.

Key Concept

High Availability and Infrastructure Redundancy Controls
Estimated Time:1m 30s
Question 359Question →

An agricultural engineering team is deploying autonomous field-monitoring drones that operate in remote, unmonitored locations. To protect the drone flight control systems against unauthorized firmware modifications and ensure hardware-isolated cryptographic key security, which of the following hardware security controls should the engineers implement? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Secure Boot integrated with a hardware Root of Trust (RoT) to cryptographically verify bootloader signatures prior to execution.; A hardware-based Trusted Platform Module (TPM) to securely store encryption keys and perform hardware-isolated cryptographic operations.

Answer

The engineers should implement Secure Boot integrated with a hardware Root of Trust (RoT) and incorporate a Trusted Platform Module (TPM).
Implementing Secure Boot backed by a hardware Root of Trust guarantees bootloader and firmware integrity by verifying digital signatures before code execution. Additionally, using a Trusted Platform Module (TPM) isolates key generation, measurement, and key storage within tamper-resistant hardware cryptoprocessors.

Step-by-Step Solution

1
Evaluate boot integrity requirements against physical firmware tampering.
Secure Boot backed by an immutable hardware Root of Trust (RoT) ensures that only cryptographically signed, verified bootloaders and OS binaries execute during startup.
Prevents unauthorized or malicious firmware modifications from executing on the hardware.
2
Evaluate cryptographic key storage and hardware isolation requirements.
A Trusted Platform Module (TPM) or Secure Element acts as a tamper-resistant cryptoprocessor dedicated to generating and protecting cryptographic keys.
Protects keys from extraction even if the system storage is physically accessed.
3
Analyze distractor options for misapplied controls.
RSA asymmetric encryption is misapplied for bulk storage logging, and software firewalls cannot block physical hardware debug interfaces like JTAG.
Confirms the selection of hardware-level controls.

Key Concept

Hardware Root of Trust and TPM Cryptoprocessor Integration
Question 360Question →

An enterprise organization is deploying Zero Trust Architecture (ZTA) across its cloud and on-premises infrastructure. Match each core Zero Trust principle on the left with its corresponding operational security mechanism on the right.

Click a left item, then click its matching right item

Items

Explicit Verification
Least Privilege Access
Assume Breach
Continuous Adaptive Monitoring

Matches

Show answer & explanation

Answer

Explicit Verification corresponds to evaluating identity, location, device compliance, and context before granting access. Least Privilege Access corresponds to restricting rights using Just-In-Time and Just-Enough-Access models. Assume Breach corresponds to limiting lateral movement using microsegmentation and internal network encryption. Continuous Adaptive Monitoring corresponds to re-evaluating risk and adjusting access dynamically during active sessions.
Zero Trust Architecture principles establish explicit enforcement boundaries: Explicit Verification validates identity and posture upfront; Least Privilege Access applies JIT/JEA controls to restrict permission scope; Assume Breach utilizes microsegmentation and encryption to limit blast radius; and Continuous Adaptive Monitoring dynamically re-evaluates active session telemetry.

Step-by-Step Solution

1
Analyze Explicit Verification operational controls
Identify controls requiring multi-factor contextual validation (identity, device compliance, location) before granting access.
Explicit Verification mandates that no request is trusted implicitly based on network location alone.
2
Analyze Least Privilege Access operational controls
Identify controls utilizing JIT and JEA to restrict permissions.
Least privilege limits user capabilities to the bare minimum required for their immediate job role.
3
Analyze Assume Breach operational controls
Identify containment controls such as network microsegmentation and ubiquitous transport encryption.
Assuming an internal intruder requires architectural controls that prevent unimpeded lateral movement.
4
Analyze Continuous Adaptive Monitoring operational controls
Identify controls that inspect live telemetry to adjust active session risk scores dynamically.
Zero Trust treats trust as ephemeral, requiring continuous posture assessment throughout a session.

Key Concept

Core Zero Trust Architectural Principles and Tenets
PreviousPage 18 / 21Next
Security Architecture Practice Questions — CompTIA Security+ — Page 18 | Examkin