Security Architecture

405 questions

Question 381Question

A network security administrator is enhancing default gateway availability for a critical transaction processing subnet. The design mandates that if the active border router suffers a hardware crash, internal client endpoints must maintain outbound connectivity automatically without requiring manual IP reconfiguration or workstation restarts. Which of the following controls best achieves this fault-tolerant requirement?

Show answer & explanation

Answer: Implement a First Hop Redundancy Protocol to share a virtual IP and MAC address across the routers.

Answer

Implementing a First Hop Redundancy Protocol (FHRP) allows redundant routers to share a single virtual IP and MAC address, allowing transparent gateway failover for client endpoints.
First Hop Redundancy Protocols allow two or more physical routers to present a shared virtual IP address and virtual MAC address to local endpoints. If the active master router fails, a backup router assumes responsibility for traffic sent to the virtual IP without requiring changes to client network settings.

Step-by-Step Solution

1
Analyze the technical requirement.
The requirement calls for automatic layer 3 default gateway failover for endpoint clients without manual endpoint reconfiguration.
Host computers configured with a static default gateway IP address cannot dynamically switch to a second router IP address unless a virtual gateway abstraction is used.
2
Evaluate candidate high availability protocols.
First Hop Redundancy Protocols (such as VRRP or HSRP) group physical routers into a logical unit assigned a virtual IP address used by endpoints as their default gateway.
When the primary router fails, a standby router immediately assumes the virtual IP address and virtual MAC address, continuing traffic forwarding seamlessly.

Key Concept

First Hop Redundancy Protocols (FHRP)
Question 382Question

An organization is deploying a cluster of database servers that require continuous network connectivity at the host level. The infrastructure team must configure host network interfaces to survive an individual cable or switch port failure while simultaneously aggregating bandwidth across two interconnected access switches during normal operations. Which of the following networking mechanisms should the administrator implement to meet these requirements?

Show answer & explanation

Answer: NIC teaming configured for IEEE 802.3ad Link Aggregation Control Protocol (LACP) using a switch-stacking topology

Answer

NIC teaming configured for IEEE 802.3ad Link Aggregation Control Protocol (LACP) using a switch-stacking topology
NIC teaming with 802.3ad LACP directly satisfies the requirement for both network interface fault tolerance and active-active bandwidth aggregation. Connecting the bonded links to a switch-stacking architecture ensures that if a single network port, cable, or switch fails, network traffic immediately fails over to the remaining active link without interrupting database connectivity.

Step-by-Step Solution

1
Analyze the operational requirements
The requirement specifies host-level network link resilience against cable/switch port failure combined with active-active bandwidth aggregation across interconnected switches.
Identifying the target domain (network availability and link redundancy) separates host networking controls from storage or power controls.
2
Evaluate network interface resilience options
NIC teaming (bonding) allows multiple physical network adapters to function as a unified logical interface. IEEE 802.3ad LACP dynamically manages link aggregation to combine throughput while providing fault tolerance.
When connected to a switch stack or MCLAG arrangement, LACP enables active-active link load balancing across separate physical switches.
3
Differentiate correct network fault-tolerance controls from non-network redundancy mechanisms
Disqualify storage redundancy (RAID 1), power infrastructure redundancy (dual PDUs/UPS), and disaster recovery techniques (cold-site snapshots).
Only NIC teaming with LACP directly addresses network link aggregation and port failure resilience.

Key Concept

NIC Teaming and Link Aggregation (LACP)
Estimated Time:1m 30s
Question 383Question

A security architect is designing an enterprise Network Access Control (NAC) architecture to secure corporate wired and wireless infrastructure. The design requires mutual authentication between client devices and the network, along with centralized authentication and authorization against the enterprise identity store. Which of the following components or protocols should be integrated to meet these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: A centralized RADIUS server integrated with the enterprise directory service to evaluate network access requests.; Extensible Authentication Protocol-TLS (EAP-TLS) configured across endpoints and network devices to enable certificate-based mutual authentication.

Answer

The correct architecture requires a centralized RADIUS server integrated with enterprise directory services and EAP-TLS protocol configuration for mutual certificate-based authentication.
Implementing a centralized RADIUS server provides the AAA infrastructure required to evaluate access policies and connect to corporate directory services. Combining RADIUS with EAP-TLS satisfies the mutual authentication constraint through two-way X.509 certificate validation during network admission.

Step-by-Step Solution

1
Determine the protocol capable of performing mutual authentication at the network layer using digital certificates.
EAP-TLS is selected because it requires both client and server X.509 certificates to complete the TLS handshake over IEEE 802.1X.
EAP-TLS fulfills the requirement for mutual cryptographic verification between endpoints and the authentication framework.
2
Identify the architectural server role needed to centralize access requests and interface with the enterprise identity store.
A RADIUS server is selected as the central Authentication, Authorization, and Accounting (AAA) server.
RADIUS acts as an intermediary that evaluates authentication requests from network devices against enterprise directory policies.

Key Concept

Network Access Control and AAA Architecture (EAP-TLS & RADIUS)
Question 384Question

An organization is updating its enterprise Identity and Access Management (IAM) architecture to reduce credential exposure and prevent lateral movement across server environments. The security architect needs to eliminate static, long-lived administrator credentials and ensure that elevated privileges are granted only on-demand for specific tasks and automatically revoked upon task completion. Which of the following IAM architectural strategies best fulfills this requirement?

Show answer & explanation

Answer: Implementing Privileged Access Management (PAM) integrated with Just-In-Time (JIT) access and ephemeral credential provisioning.

Answer

Implementing Privileged Access Management (PAM) integrated with Just-In-Time (JIT) access and ephemeral credential provisioning.
The solution advocating Privileged Access Management (PAM) with Just-In-Time (JIT) access and ephemeral credential provisioning directly meets the objective. JIT access eliminates standing privileges by generating temporary, scoped credentials or elevating access rights strictly during an approved session window and revoking them automatically afterward.

Step-by-Step Solution

1
Analyze the core architectural requirement described in the enterprise scenario.
The requirement calls for eliminating static, long-lived administrator credentials and replacing them with temporary privilege elevation that expires automatically upon completion of administrative tasks.
Persistent high-privilege credentials present a high-value target for attackers attempting lateral movement.
2
Evaluate candidate IAM mechanisms against the requirement of dynamic, temporary elevation.
Privileged Access Management (PAM) solutions supporting Just-In-Time (JIT) access issue short-lived or ephemeral credentials specifically for authorized workflows and revoke them immediately after the designated window.
JIT access reduces standing privilege attack surface to zero when no administrative task is active.
3
Distinguish PAM JIT solutions from static authentication or network isolation controls.
Controls like MFA, jump hosts, or static RBAC directory groups enhance security but leave permanent privileged memberships intact.
Only PAM with JIT access specifically addresses the lifecycle and ephemeral nature of administrator privilege elevation.

Key Concept

Privileged Access Management (PAM) and Just-In-Time (JIT) Access Architecture
Question 385Question

A security administrator is establishing a high-availability disaster recovery plan for a mission-critical web application. During an unrecoverable primary data center outage, administrative staff must execute a site failover to the secondary site. Place the following failover operational steps in the correct chronological sequence from first to last.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct operational sequence is: 1) Detect primary site failure and initiate failover, 2) Isolate the primary site to prevent split-brain condition, 3) Promote the secondary database to primary active read-write mode, and 4) Update GSLB DNS records to direct user traffic to the secondary site.
In high-availability and disaster recovery architectures, site failover must follow a strict dependencies-first operational sequence. Detecting failure precedes all administrative actions. Fencing the primary node must occur next to prevent split-brain data corruption caused by simultaneous active nodes. Subsequently, backend state stores (databases) must be promoted to read-write mode before front-end services can handle transactions. Finally, GSLB/DNS redirection is updated to send live client traffic to the secondary location.

Step-by-Step Solution

1
Identify system status
Automated monitoring flags primary site unavailability and triggers the failover routine.
Monitoring and detection must precede any operational state changes.
2
Enforce fencing and isolation
Primary nodes are isolated to ensure they do not attempt to process writes concurrently.
Fencing prevents split-brain scenarios where both data centers attempt to write to shared or replicated databases simultaneously.
3
Promote secondary data tier
Secondary standby database is converted to primary read-write status.
Application services cannot function correctly until the backend data layer is capable of processing state modifications.
4
Redirect traffic ingress
GSLB endpoints update DNS records to point to the secondary site IP infrastructure.
Traffic routing is updated last to ensure users land on fully configured and operational services.

Key Concept

Disaster Recovery Failover Sequencing and Split-Brain Prevention
Question 386Question

An organization is designing an automated identity lifecycle architecture to synchronize user identity state between its cloud-based HR system and its central Identity Provider (IdP). Which of the following requirements must be implemented within this architecture to support secure automated user provisioning and real-time deprovisioning? (Select TWO).

Select all that apply

Show answer & explanation

Answer: Implementation of standardized System for Cross-domain Identity Management (SCIM) service endpoints to automate identity schema operations between systems.; Deployment of centralized session revocation mechanisms to invalidate active tokens and application access upon user status change signals.

Answer

Standardized System for Cross-domain Identity Management (SCIM) endpoints must be implemented for automated identity schema operations, along with centralized session revocation mechanisms to invalidate active application tokens upon deprovisioning.
Automating identity provisioning between HR platforms and centralized Identity Providers requires SCIM service endpoints to standardize user schema updates and deprovisioning calls across multi-tenant applications. Furthermore, to prevent unauthorized access via active sessions after account suspension, the architecture must incorporate centralized token and session revocation capabilities across all downstream relying parties.

Step-by-Step Solution

1
Analyze identity lifecycle architecture requirements for cloud HR to IdP integration.
Identified the requirement for automated, standardized provisioning and deprovisioning protocols.
SCIM is the industry standard protocol built explicitly for exchange of user identity information across independent domains.
2
Evaluate deprovisioning security controls to prevent orphaned account exploitation.
Determined that session revocation mechanisms must propagate status changes immediately.
Deprovisioning an account in the IdP is insufficient if active OAuth tokens or SAML sessions remain valid on target applications.
3
Distinguish correct architectural solutions from misconfigurations and conceptual errors.
Selected SCIM and session revocation while eliminating perimeter-only defenses and authentication/authorization confusion.
Perimeter firewalls do not protect cloud-hosted resources, and credential prompts handle identity verification rather than authorization rights.

Key Concept

Automated Identity Lifecycle & Provisioning Architecture
Estimated Time:1m 30s
Question 387Question

Match each enterprise identity and access management (IAM) architectural component on the left to its primary functional responsibility on the right.

Click a left item, then click its matching right item

Items

SAML Assertion Consumer Service (ACS)
OAuth 2.0 Authorization Server
SCIM Provisioning Service
Kerberos Key Distribution Center (KDC)

Matches

Show answer & explanation

Answer

SAML Assertion Consumer Service (ACS) matches receiving and validating signed XML assertions from an external IdP; OAuth 2.0 Authorization Server matches authenticating resource owners and issuing scoped access tokens; SCIM Provisioning Service matches automating identity account creation and de-provisioning via RESTful APIs; Kerberos Key Distribution Center (KDC) matches granting Ticket Granting Tickets and service tickets for internal domain authentication.
Each IAM component performs a specific architectural role in identity lifecycle management, federated web single sign-on, API authorization delegation, or local domain ticket authentication.

Step-by-Step Solution

1
Identify SAML Assertion Consumer Service (ACS) function
Matches XML assertion processing at the Service Provider endpoint during federated SSO.
SAML reliance on XML signatures and HTTP posts to the ACS endpoint is characteristic of web-based SP-initiated or IdP-initiated federation.
2
Identify OAuth 2.0 Authorization Server function
Matches issuing scoped tokens for API authorization access.
OAuth 2.0 delegates authority through token issuance without sharing credentials with the client application.
3
Identify SCIM Provisioning Service function
Matches automated lifecycle management across external application identity stores.
SCIM defines schema models and HTTP operations for syncing user identity lifecycles.
4
Identify Kerberos Key Distribution Center (KDC) function
Matches issuing Ticket Granting Tickets (TGT) within a local Active Directory domain.
Kerberos relies on a trusted KDC to grant ticket-based mutual authentication on internal networks.

Key Concept

Enterprise IAM Architecture Components and Protocols
Question 388Question

A security administrator is reviewing high-availability cluster resilience and failover mechanisms for mission-critical enterprise services. Match each clustering component or condition on the left with its corresponding operational definition or control mechanism on the right.

Click a left item, then click its matching right item

Items

Split-brain condition
Quorum
STONITH (Fencing)
Heartbeat link

Matches

Show answer & explanation

Answer

Split-brain condition matches the state where isolated partitions simultaneously claim active role; Quorum matches the minimum voting node requirement for authority; STONITH matches the automated node power-down/isolation mechanism; Heartbeat link matches the dedicated keep-alive telemetry path.
Each clustering concept represents a specific mechanism essential for maintaining cluster integrity and high availability: the heartbeat link continuously monitors peer health; quorum requires a majority vote before changing active status; split-brain occurs when lost communication causes dual active nodes; and STONITH forcibly isolates or powers down problematic nodes to prevent split-brain write corruption.

Step-by-Step Solution

1
Identify the primary functions of node monitoring, partition consensus, and conflict resolution in high-availability clusters.
Determined that heartbeat links monitor health, quorum establishes state consensus, split-brain describes dual-active partition conflicts, and fencing (STONITH) enforces physical node isolation.
Clustering resilience relies on distinguishing health signaling from decision consensus and active fencing controls.
2
Pair each clustering concept on the left with its matching definition on the right.
Mapped Split-brain condition to dual active assumption, Quorum to voting node threshold, STONITH to automated power down, and Heartbeat link to dedicated monitoring path.
Accurate pairing aligns cluster design terminology with concrete resilience and failover controls.

Key Concept

High-Availability Clustering Controls and Partition Fault Tolerance Mechanisms
Estimated Time:1m 30s
Question 389Question

A security architect is designing an authentication and authorization framework for a newly developed microservices-based web application. The architectural design requires a lightweight, stateless mechanism to securely transport identity claims and delegated authorization scopes between independent API endpoints without maintaining server-side session state or performing repeated directory database lookups for each call. Which of the following IAM standards should the architect implement?

Show answer & explanation

Answer: OpenID Connect (OIDC) combined with OAuth 2.0 using JSON Web Tokens (JWT)

Answer

The architect should implement OpenID Connect (OIDC) combined with OAuth 2.0 using JSON Web Tokens (JWT).
OpenID Connect (OIDC) built on top of OAuth 2.0 issues JSON Web Tokens (JWT) containing cryptographically signed claims and scopes. Microservices can independently verify these lightweight tokens using public key cryptography, eliminating the need to maintain server session state or query a central database for every API request.

Step-by-Step Solution

1
Analyze the microservices requirement for stateless identity and authorization propagation.
Identified the need for self-contained, digitally signed tokens that carry claims without requiring server-side session lookup databases.
Microservice architectures scale best when services do not maintain centralized session state.
2
Evaluate candidate protocols against REST/API performance and statelessness criteria.
OAuth 2.0 provides delegated authorization, OIDC adds an identity layer, and JWT provides lightweight JSON payload structures ideal for HTTP headers.
JSON Web Tokens can be validated independently by microservices using public key cryptography without calling back to the identity provider.

Key Concept

Stateless API Authentication and Authorization via OIDC/OAuth 2.0 JWTs
Estimated Time:1m 30s
Question 390Question

An enterprise organization is deploying a native mobile application that connects to cloud-hosted REST APIs. The mobile client runs in an untrusted environment where embedded client secrets cannot be kept confidential. Which of the following identity and access management architecture components should the security architect implement to securely authorize the mobile application while mitigating authorization code interception attacks?

Show answer & explanation

Answer: OAuth 2.0 Authorization Code Grant with Proof Key for Code Exchange (PKCE)

Answer

OAuth 2.0 Authorization Code Grant with Proof Key for Code Exchange (PKCE)
OAuth 2.0 Authorization Code Grant with PKCE is specifically designed to secure public clients (such as mobile apps and single-page apps) that cannot safely maintain a confidential client secret. By creating a unique code verifier and transformed code challenge for each request, the authorization server verifies that the entity redeeming the code is the exact client instance that requested it.

Step-by-Step Solution

1
Analyze client constraints
The target application is a public native mobile client, meaning embedded client secrets cannot be securely stored.
Public clients can be decompiled or inspected by attackers to extract static credentials.
2
Evaluate risk profile for authorization code flow
Standard Authorization Code Grant requires a client secret, making public clients vulnerable to code interception attacks if secrets are omitted or exposed.
Malicious applications on the mobile device can register custom URI schemes and intercept the authorization code returned by the authorization server.
3
Select appropriate IAM protocol extension
Proof Key for Code Exchange (PKCE) replaces static secrets with a dynamically generated secret key pair (code_verifier and code_challenge) per request.
This guarantees that only the application instance that initiated the request can exchange the intercepted authorization code for an access token.

Key Concept

Public Client Token Exchange and PKCE Architecture
Estimated Time:1m 30s
Question 391Question

Match each enterprise identity and access management (IAM) protocol or standard on the left with its primary architectural function on the right.

Click a left item, then click its matching right item

Items

OAuth 2.0
OpenID Connect (OIDC)
SAML 2.0
SCIM

Matches

Show answer & explanation

Answer

OAuth 2.0 matches API authorization delegation; OpenID Connect matches the OAuth 2.0 identity/authentication layer; SAML 2.0 matches XML-based federated Web SSO; SCIM matches automated identity provisioning.
Each protocol serves a distinct architectural purpose in modern enterprise IAM systems: OAuth 2.0 handles delegated API access control, OIDC provides modern OAuth-based user authentication, SAML 2.0 delivers traditional XML-based federated web SSO, and SCIM automates identity lifecycle management and provisioning across cloud and on-premises directories.

Step-by-Step Solution

1
Differentiate authentication vs. authorization frameworks.
Identify OAuth 2.0 as strictly authorization/delegation, and OIDC as the identity authentication extension.
OAuth 2.0 alone provides access tokens for API authorization, whereas OIDC adds ID tokens for user authentication.
2
Identify web federation formats.
Match SAML 2.0 to XML-based security assertions.
SAML 2.0 is the legacy enterprise XML standard for cross-domain SSO federations between IdPs and SPs.
3
Identify identity lifecycle management standards.
Match SCIM to automated cross-domain user provisioning.
SCIM uses standardized REST endpoints and JSON payloads to sync user account states across systems.

Key Concept

Enterprise IAM Architectural Protocols & Standards
Question 392Question

An enterprise security architect is designing an Identity and Access Management (IAM) architecture for a hybrid enterprise environment. To align with modern Zero Trust principles, the system must evaluate real-time context—such as user risk score, device compliance state, and access location—before granting access to sensitive cloud databases, rather than trusting users based on network location. Which architectural component in this framework is directly responsible for evaluating these dynamic context attributes against enterprise security policies to render an access decision?

Show answer & explanation

Answer: Policy Decision Point (PDP)

Answer

Policy Decision Point (PDP)
In Zero Trust identity architectures, the Policy Decision Point (PDP) examines subject attributes, requested resources, and real-time environmental context against security policies to produce authorization decisions.

Step-by-Step Solution

1
Identify the core requirement in the scenario.
The requirement specifies evaluating dynamic context (device posture, user risk score, location) against security policies to make authorization decisions.
Distinguishing policy evaluation logic from policy enforcement and credential storage isolates the responsible component.
2
Map the requirement to standard Zero Trust IAM architectural roles.
The component that executes policy rules to yield a grant/deny outcome is the Policy Decision Point (PDP).
In Zero Trust architecture, the PDP acts as the centralized engine responsible for rendering access decisions before passing them to enforcement mechanisms.

Key Concept

Zero Trust IAM Architecture and Policy Decision Points (PDP)
Question 393Question

An organization is upgrading its access control infrastructure to allow third-party contractors temporary access to cloud-hosted management portals and APIs. The security team mandates that credentials must not be statically stored on client devices, identity assertions must be centralized via modern web standards, and access decisions must not rely on internal network perimeter position. Which of the following security mechanisms should be incorporated into this Identity and Access Management (IAM) architecture? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Deploying OpenID Connect (OIDC) with OAuth 2.0 to handle federated authentication and short-lived scoped token issuance; Implementing a Privileged Access Management (PAM) system configured for Just-In-Time (JIT) access and ephemeral credential generation

Answer

The architectural requirement is met by combining OpenID Connect (OIDC) with OAuth 2.0 for federated web/API authentication and a Privileged Access Management (PAM) system utilizing Just-In-Time (JIT) ephemeral credentials.
Combining OpenID Connect (OIDC) with OAuth 2.0 provides standard, federated identity assertions and scoped access tokens for modern cloud portals and APIs. Integrating Privileged Access Management (PAM) configured for Just-In-Time (JIT) access ensures credentials are generated dynamically on demand and automatically invalidated, satisfying the prohibition against static credentials.

Step-by-Step Solution

1
Analyze requirement for centralized, web-standard identity assertions and token access
Identify OpenID Connect (OIDC) and OAuth 2.0 as the standard federated identity and token-based framework for web portals and APIs
OIDC provides modern identity verification over HTTP/HTTPS while OAuth 2.0 issues temporary scoped tokens instead of static API keys.
2
Analyze requirement to eliminate statically stored client credentials for temporary contractors
Select Just-In-Time (JIT) provisioning within a Privileged Access Management (PAM) architecture
JIT PAM dynamically provisions temporary access and auto-expires credentials, satisfying the constraint against static credential storage.
3
Evaluate and eliminate distractors relying on perimeter boundary trust or improper control types
Reject RADIUS/MAB perimeter mechanisms and static IP firewall rules
Perimeter controls fail to verify identity dynamically at the application level and conflict with zero-trust architectural principles.

Key Concept

Privileged Access Management (PAM) with Just-In-Time (JIT) Provisioning and OIDC/OAuth2 Federated Architecture
Question 394Question

A financial enterprise is integrating a legacy on-premises web application—which natively authenticates internal users via Kerberos tickets—with a modern cloud-based Identity Provider (IdP) to support federated single sign-on (SSO) for remote workers. The architecture must enable remote users to authenticate against the cloud IdP while ensuring internal domain controllers and Kerberos Key Distribution Centers (KDCs) are not directly exposed to external network traffic. Which IAM architectural solution best meets these requirements?

Show answer & explanation

Answer: Deploy an Identity-Aware Reverse Proxy in a demilitarized zone that validates cloud IdP assertions and utilizes Kerberos Constrained Delegation to impersonate authenticated users to the backend application

Answer

Deploying an Identity-Aware Reverse Proxy that validates cloud IdP assertions and performs Kerberos Constrained Delegation (KCD) is the correct architectural solution.
Deploying an Identity-Aware Proxy equipped with Kerberos Constrained Delegation (KCD) bridges the gap between modern cloud single sign-on assertions (such as SAML or OIDC) and legacy internal ticket-based authentication. The proxy validates external user identities with the cloud Identity Provider and subsequently requests a Kerberos ticket on behalf of the user to access the legacy application, all while keeping internal domain controllers isolated from direct internet access.

Step-by-Step Solution

1
Analyze the IAM architectural requirements
Identified the need to bridge modern web federation protocols (used by the cloud IdP) with legacy ticket-based protocols (Kerberos used by internal applications) without exposing internal domain infrastructure to the internet.
Remote users authenticate externally using web tokens (SAML/OIDC), whereas the legacy application expects internal Kerberos tickets.
2
Evaluate protocol translation and gateway components
An Identity-Aware Reverse Proxy operating at the network perimeter can authenticate the external user assertion from the cloud IdP and perform Kerberos Constrained Delegation (KCD) on the internal side.
KCD allows the gateway to securely request a Kerberos service ticket on behalf of the authenticated user to grant access to backend legacy applications.
3
Verify security boundary compliance
Domain Controllers and KDCs remain isolated in the internal network segment behind the proxy layer.
Prevents direct external exposure of core enterprise identity services.

Key Concept

Protocol Transition and Gateway Integration in IAM Architecture
Question 395Question

A healthcare enterprise is deploying a Zero Trust Architecture (ZTA) across its clinical telemetry systems. During an active diagnostic data transmission session, an endpoint compliance agent reports that a workstation's local security baseline has been modified unexpectedly, though the clinician's multi-factor authentication (MFA) token remains valid and unexpired. Which of the following operations executed by the Zero Trust control plane best demonstrates the principle of continuous verification?

Show answer & explanation

Answer: The Policy Decision Point (PDP) recalculates the session's dynamic trust score based on telemetry metrics and instructs the Policy Enforcement Point (PEP) to terminate the connection despite valid user credentials.

Answer

The Policy Decision Point (PDP) recalculates the session's dynamic trust score based on telemetry metrics and instructs the Policy Enforcement Point (PEP) to terminate the connection despite valid user credentials.
Under Zero Trust Architecture (ZTA) principles, explicitly verifying every request requires continuous authentication and contextual evaluation. When device telemetry indicates baseline configuration tampering, the Policy Decision Point (PDP) dynamically re-evaluates the contextual risk score and signals the Policy Enforcement Point (PEP) to sever the data plane session. Valid user credentials do not override compromised endpoint security posture.

Step-by-Step Solution

1
Analyze the change in security posture during an active session
The workstation's endpoint integrity baseline degraded mid-session due to unauthorized local modification.
Zero Trust requires continuous monitoring of device hygiene alongside identity state.
2
Evaluate the architectural responsibilities of the control plane (PDP and PEP)
The Policy Decision Point (PDP) processes incoming risk signals and computes a dynamic trust score, while the Policy Enforcement Point (PEP) executes the policy enforcement by dropping or allowing data plane traffic.
Separation of control plane logic from data plane enforcement allows real-time adaptive access controls.
3
Determine the proper Zero Trust operational response
The PDP must immediately invalidate session access rights based on reduced trust score and order the PEP to drop the connection.
Implicit trust is never granted based solely on unexpired identity tokens or initial authentication.

Key Concept

Continuous verification and dynamic policy decision making (PDP/PEP) in Zero Trust Architecture
Question 396Question

An organization is migrating its customer relationship management operations to a Software as a Service (SaaS) cloud solution. Under the cloud shared responsibility model, which of the following tasks remains the primary responsibility of the organization?

Show answer & explanation

Answer: Configuring access permissions and identity management for organizational user accounts

Answer

Configuring access permissions and identity management for organizational user accounts
Under the cloud shared responsibility model for Software as a Service (SaaS), the cloud service provider (CSP) takes on responsibility for physical infrastructure, hardware, operating systems, hypervisors, and application maintenance. The cloud customer remains responsible for data classification, user identity management, and configuring account access permissions.

Step-by-Step Solution

1
Identify the cloud service model provided in the scenario.
The scenario specifies a Software as a Service (SaaS) model.
Responsibility boundaries vary depending on whether the service model is IaaS, PaaS, or SaaS.
2
Evaluate the shared responsibility division for SaaS.
The Cloud Service Provider manages hardware, network infrastructure, host operating systems, hypervisors, and software maintenance.
SaaS abstracts all underlying infrastructure and application source code away from the customer.
3
Identify the customer-managed domain in SaaS.
Managing user identity, account provisioning, and data access permissions remains with the cloud customer.
Regardless of the cloud deployment model, data ownership and user access control always remain the responsibility of the cloud tenant.

Key Concept

Cloud Shared Responsibility Model in SaaS
Estimated Time:45s
Question 397Question

A global logistics organization migrates its freight tracking platform to a cloud provider's managed container orchestration service (PaaS). Under the contract, the cloud service provider maintains the physical host infrastructure, hypervisor layer, and control plane nodes. To maintain regulatory compliance, the organization's security architect must establish the operational control boundaries for the deployment. Which of the following security responsibilities rests exclusively with the organization in this managed cloud model?

Show answer & explanation

Answer: Configuring container workload security policies, application data encryption keys, and pod access boundaries.

Answer

Configuring container workload security policies, application data encryption keys, and pod access boundaries.
In PaaS and managed container orchestration environments, the cloud service provider abstracts and manages the underlying hardware, hypervisors, and control plane. The customer retains full ownership and responsibility for application-level security, container workload policies, access control rules, and key management for data encryption.

Step-by-Step Solution

1
Analyze the cloud service model presented in the scenario.
The scenario describes a managed container service (PaaS) where the cloud service provider (CSP) manages the physical infrastructure, hypervisor, and control plane.
Determining the service model establishes the baseline division of duties under the Shared Responsibility Model.
2
Differentiate CSP responsibilities from customer responsibilities.
The CSP manages host security, physical facilities, and control plane uptime. The customer retains ownership of data classification, container configuration, runtime security, and access rules.
Customers operating in PaaS retain full control over data and application-level security.
3
Identify the option that correctly reflects exclusive customer responsibility.
Managing container security configurations, pod access controls, and application encryption keys is strictly a customer duty.
Application layer controls and customer-managed keys cannot be managed by the CSP.

Key Concept

Shared Responsibility Model in Platform as a Service (PaaS)
Estimated Time:2m 0s
Question 398Question

An enterprise financial organization is redesigning its network architecture for a cloud-hosted payment gateway platform. While perimeter Next-Generation Firewalls (NGFW) currently inspect all North-South ingress traffic from external clients, recent audit logs revealed that compromised web application nodes in the public presentation subnet attempted unauthorized lateral movement (East-West traffic) to internal database clusters within the same virtual private network. The security team requires a design that enforces granular, application-centric access controls between internal workloads without requiring major subnet re-addressing or causing latency bottlenecks associated with hairpinning internal traffic through a central hardware appliance. Which of the following architectural strategies best satisfies these requirements?

Show answer & explanation

Answer: Deploy a software-defined microsegmentation architecture utilizing service mesh network policies and mutual TLS (mTLS) between application workload endpoints.

Answer

Deploying a software-defined microsegmentation architecture utilizing service mesh network policies and mutual TLS (mTLS) between application workload endpoints is the optimal solution.
The correct strategy involves software-defined microsegmentation paired with a service mesh enforcing mTLS. Microsegmentation divides networks into granular security zones down to individual workload instances. By applying policy at the hypervisor or container sidecar level, East-West traffic between web nodes and database clusters is strictly controlled and encrypted regardless of underlying IP subnet structures, eliminating latency from traffic hairpinning through edge firewalls.

Step-by-Step Solution

1
Analyze the architectural challenge and network traffic vectors.
Identified unauthorized lateral movement (East-West traffic) between compromised web containers and database workloads located within internal network boundaries.
Traditional perimeter firewalls only filter North-South traffic crossing the network boundary and cannot effectively isolate workloads residing inside the same broadcast domain or subnet.
2
Evaluate constraint parameters.
The solution must avoid network hairpinning, IP re-addressing overhead, and performance bottlenecks.
Routing intra-datacenter microservice traffic through a centralized hardware appliance causes latency degradation and scalable failure points.
3
Select the appropriate segmentation model.
Software-defined microsegmentation via service mesh / host network policies enforces identity-based zero-trust isolation directly at the software workload layer.
Microsegmentation isolates individual workloads down to the single container or VM level regardless of physical network topology or shared subnets.

Key Concept

Microsegmentation and East-West Traffic Isolation
Estimated Time:2m 0s
Question 399Question

A system administrator needs to configure a mission-critical web server to ensure continuous operation even if a single network interface card (NIC) or power circuit fails. Which of the following hardware resilience controls should the administrator implement to eliminate these specific single points of failure? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: NIC teaming configured across separate physical switches; Redundant power supplies connected to independent Power Distribution Units (PDUs)

Answer

The administrator should implement NIC teaming configured across separate physical switches and redundant power supplies connected to independent PDUs.
The combination of NIC teaming and dual power supplies connected to separate PDUs ensures component-level fault tolerance for both network connectivity and electrical power, satisfying the goal of removing single points of failure.

Step-by-Step Solution

1
Identify the network interface single point of failure requirement.
Combine multiple network interface cards using NIC teaming connected to distinct switch paths to ensure continuous connectivity upon link failure.
NIC teaming provides adapter fault tolerance at the network layer.
2
Identify the power infrastructure single point of failure requirement.
Equip the server with redundant power supply units (PSUs) plugged into independent electrical circuits via separate PDUs.
Dual PSUs on separate PDUs ensure uninterrupted power delivery if a PSU or power feed drops out.

Key Concept

Hardware Fault Tolerance and Link Redundancy
Question 400Question

A digital media broadcasting corporation stores petabytes of high-definition video archives within an enterprise object storage platform. To fulfill compliance mandates from content licensors, the security team must implement a data protection solution that enforces hardware-rooted key protection, strict audit logging of key access requests, and annual key rotation. Crucially, the key rotation process must not require re-encrypting the underlying multi-terabyte static data objects. Which of the following storage security architectures best meets these combined requirements?

Show answer & explanation

Answer: Implement envelope encryption using Data Encryption Keys (DEKs) wrapped by Key Encryption Keys (KEKs) stored within a Hardware Security Module (HSM).

Answer

Envelope encryption using Data Encryption Keys (DEKs) wrapped by Key Encryption Keys (KEKs) inside a Hardware Security Module (HSM) satisfies all requirements.
Envelope encryption utilizes a symmetric Data Encryption Key (DEK) to encrypt bulk data objects and a Key Encryption Key (KEK) managed inside a Hardware Security Module (HSM) to encrypt the DEKs. When key rotation occurs, only the KEK wrapping the DEKs needs to be updated, enabling instant key rotation without reading or re-writing petabytes of static video files. This fulfills hardware-rooted security, access auditing, and zero-downtime key rotation requirements.

Step-by-Step Solution

1
Analyze storage encryption scale and constraints
Re-encrypting petabytes of static video data during annual key rotation is computationally prohibitive and operationally unfeasible.
Direct bulk data re-encryption requires reading and re-writing all stored data objects.
2
Evaluate key management architectures
Envelope encryption separates data payload encryption (symmetric DEK) from root key protection (KEK).
Rotating the KEK only requires re-wrapping the DEK, leaving the underlying encrypted data payload untouched.
3
Integrate compliance requirements for hardware protection and auditing
Housing the KEK in a Hardware Security Module (HSM) fulfills hardware-rooted security and centralized audit logging requirements.
HSMs provide tamper-resistant key storage and detailed access trail generation.

Key Concept

Envelope Encryption and HSM Integration for Storage Security
PreviousPage 20 / 21Next
Security Architecture Practice Questions — CompTIA Security+ — Page 20 | Examkin