Security Architecture

405 questions

Question 281Question

A logistics enterprise is integrating automated freight crane telemetry sensors with its centralized monitoring dashboard. The crane control systems run legacy industrial software that cannot be patched, whereas the monitoring dashboard resides on the corporate administrative network. Which network design control best mitigates the risk of lateral threat movement from the corporate network to the crane controllers while continuing to permit automated telemetry collection?

Show answer & explanation

Answer: Deploying microsegmentation with strict firewall stateful rules that enforce unidirectional traffic flow from the crane network zone to the monitoring dashboard

Answer

Deploying microsegmentation with strict firewall stateful rules that enforce unidirectional traffic flow from the crane network zone to the monitoring dashboard.
Microsegmentation paired with unidirectional stateful filtering allows data to be sent from the critical operational zone to the dashboard zone while blocking any inbound access requests initiated from the administrative network toward the vulnerable legacy crane controllers.

Step-by-Step Solution

1
Analyze the functional requirements and security constraints of the operational environment.
Real-time telemetry data must flow out from the crane controllers to the corporate dashboard, but legacy controllers must be shielded from incoming connections.
Legacy systems are vulnerable to exploit attempts if reachable over the network.
2
Evaluate network architecture controls against threat vectors.
Microsegmentation establishes granular control boundaries around the industrial controllers, allowing outbound telemetry traffic while blocking inbound connections from the corporate network.
Restricting session initiation prevents compromised corporate workstations from moving laterally into the industrial control environment.

Key Concept

Microsegmentation and zone isolation for operational technology (OT) systems
Estimated Time:1m 30s
Question 282Question

A security team is implementing an access control model that evaluates contextual variables—such as user location, device security compliance, time of request, and resource sensitivity—before granting access. Which access control architecture model natively uses these dynamic characteristics to make authorization decisions?

Show answer & explanation

Answer: Attribute-Based Access Control (ABAC)

Answer

Attribute-Based Access Control (ABAC)
Attribute-Based Access Control (ABAC) evaluates specific characteristics (attributes) belonging to the user, resource, action, and environment—such as IP address, device health, time of day, and data classification—to dynamically determine access permissions.

Step-by-Step Solution

1
Analyze the access control requirement in the scenario.
The requirement specifies making authorization decisions based on dynamic contextual factors such as location, device health, time of request, and data sensitivity.
Understanding the input parameters used for access decisions helps distinguish between static and dynamic access control models.
2
Evaluate the architectural characteristics of Attribute-Based Access Control (ABAC).
ABAC grants access rights through policies that combine subject, resource, action, and environmental attributes.
ABAC is specifically designed to support fine-grained, dynamic, and context-aware authorization policies in modern security architectures.

Key Concept

Attribute-Based Access Control (ABAC)
Estimated Time:45s
Question 283Question

An organization is deploying a multi-tenant cloud platform where microservices processing sensitive financial records will run alongside third-party analytics services on the same physical host node. The software engineering team proposes relying solely on standard Linux container runtime features, claiming that container namespaces provide security boundary isolation identical to dedicated virtual machines on a Type-1 hypervisor. Which of the following statements best describes the primary security risk associated with this deployment architecture?

Show answer & explanation

Answer: Containers share the underlying host operating system kernel, so a privilege escalation or kernel vulnerability could allow a compromise of one container to break isolation and impact adjacent tenant workloads.

Answer

Container workloads share the underlying host operating system kernel, meaning a kernel flaw or container escape vulnerability could allow an attacker to bypass isolation and access adjacent tenant microservices on the host node.
The correct answer highlights that containers virtualize at the operating system level and share the host kernel. If an attacker exploits a flaw in the kernel or container runtime, they can escalate privileges to the host and access other containers sharing that host kernel.

Step-by-Step Solution

1
Analyze the isolation mechanism of containers versus virtual machines.
Containers share the host operating system kernel and use kernel features (namespaces, cgroups) for isolation, while virtual machines run separate guest operating systems on virtualized hardware managed by a hypervisor.
Understanding the fundamental architectural difference determines the blast radius of a security compromise.
2
Evaluate the risk of running untrusted third-party microservices on a shared container host.
A vulnerability in the shared host kernel or container runtime can be exploited to achieve a container escape.
Because the host kernel is shared across all containers on that host, breaking the kernel boundary compromises all co-located container workloads.

Key Concept

Shared Kernel Isolation Risks in Containerization
Question 284Question

Match each storage security technology on the left with its primary enterprise implementation role on the right.

Click a left item, then click its matching right item

Items

Self-Encrypting Drive (SED)
Hardware Security Module (HSM)
Storage Area Network (SAN) LUN Masking
Endpoint Data Loss Prevention (DLP)

Matches

Show answer & explanation

Answer

Self-Encrypting Drive pairs with transparent hardware-based disk encryption at the drive controller level. Hardware Security Module pairs with tamper-resistant hardware storage for securing key lifecycles. SAN LUN Masking pairs with restricting host access to specific logical volumes based on HBA identifiers. Endpoint DLP pairs with inspecting data write operations to prevent unencrypted sensitive data transfers to removable media.
Each technology fulfills a distinct role within enterprise storage architecture: SEDs provide transparent drive controller-level hardware encryption; HSMs secure key storage in hardened modules; SAN LUN masking restricts volume access by host identifier; and endpoint DLP enforces data content protection policies on endpoint write actions.

Step-by-Step Solution

1
Analyze storage encryption controls
Identify that Self-Encrypting Drives execute transparent encryption at the drive controller level, avoiding host CPU performance hits.
SEDs rely on dedicated hardware inside the drive casing rather than host OS crypto modules.
2
Evaluate key management architecture
Match Hardware Security Module to centralized, tamper-evident master key storage.
HSMs protect master keys and perform cryptoprocessing in secure physical boundaries.
3
Analyze block storage isolation mechanisms
Associate LUN Masking with restricting access to specific SAN storage volumes by checking host bus adapter WWNs/identifiers.
LUN masking acts as access control on storage arrays to prevent unauthorized servers from mounting raw storage volumes.
4
Analyze data exfiltration prevention tools
Link Endpoint Data Loss Prevention to real-time content inspection blocking writes to external storage devices.
DLP evaluates file content against classification rules before allowing write operations to endpoint peripherals.

Key Concept

Data Protection and Storage Security Architecture
Question 285Question

A healthcare organization is deploying a patient engagement application using virtual machine instances hosted on an Infrastructure as a Service (IaaS) cloud platform. The security architect is defining the operational security responsibilities between the organization and the cloud service provider (CSP). According to the cloud shared responsibility model, which of the following tasks is the sole responsibility of the customer?

Show answer & explanation

Answer: Configuring security baselines and applying security patches to the guest operating systems

Answer

Configuring security baselines and applying security patches to the guest operating systems
In Infrastructure as a Service (IaaS) cloud deployments, operational responsibility for everything built above the hypervisor belongs to the customer. This includes configuring guest operating systems, installing OS patches, managing installed applications, and implementing network access control lists on virtual interfaces.

Step-by-Step Solution

1
Identify the cloud service model referenced in the scenario.
The scenario specifies an Infrastructure as a Service (IaaS) deployment model.
Operational responsibility boundaries vary depending on whether IaaS, PaaS, or SaaS is deployed.
2
Differentiate customer duties from cloud service provider duties under IaaS.
The provider manages the physical infrastructure, facilities, hardware, and hypervisor layer. The customer manages the guest OS, middleware, applications, network firewall rules, and data.
The shared responsibility model defines ownership of security controls across cloud service tiers.
3
Evaluate the listed tasks against the customer's operational boundary.
Hardening and patching virtual machine guest operating systems falls directly within the customer's domain of control.
The CSP does not have administrative access or ownership of tenant-provisioned guest operating systems.

Key Concept

Cloud Shared Responsibility Model in Infrastructure as a Service (IaaS)
Question 286Question

A systems administrator is configuring a critical database server to eliminate single points of failure at both the power source and internal storage levels. Which of the following hardware and physical redundancy solutions directly satisfy these resilience requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Dual power supplies connected to independent Uninterruptible Power Supply (UPS) units; RAID 1 mirrored disk configuration

Answer

The correct solutions are installing dual power supplies connected to independent Uninterruptible Power Supply (UPS) units and utilizing a RAID 1 mirrored disk configuration.
High availability and hardware resilience require immediate, real-time failover mechanisms for physical components. Dual power supplies connected to separate UPS circuits ensure continuous electrical power if one power path fails. A RAID 1 mirrored drive setup maintains real-time data access and system operation if a physical hard drive fails.

Step-by-Step Solution

1
Identify the power redundancy requirement
Dual power supplies plugged into separate UPS units ensure continuous power delivery even if one circuit or power module fails.
Eliminates power supply unit and utility circuit failures as single points of failure.
2
Identify the storage redundancy requirement
RAID 1 duplicates data across two drives in real time, maintaining system availability if one disk fails.
Provides real-time storage fault tolerance without interrupting system operations.

Key Concept

Real-Time Hardware Fault Tolerance and Redundancy
Question 287Question

An organization is updating its enterprise security architecture to streamline user access across external cloud applications. The security team needs to implement standards that support federated single sign-on (SSO) and automated account lifecycle management between the corporate identity provider and SaaS platforms. Which TWO of the following open standards should the team integrate into the IAM architecture to fulfill these specific requirements?

Select all that apply

Show answer & explanation

Answer: Security Assertion Markup Language (SAML); System for Cross-domain Identity Management (SCIM)

Answer

Security Assertion Markup Language (SAML) and System for Cross-domain Identity Management (SCIM) are the two open standards designed for federated single sign-on and cross-domain user provisioning.
Security Assertion Markup Language (SAML) provides the XML framework required to federate identity assertions between an Identity Provider and cloud Service Providers for single sign-on. System for Cross-domain Identity Management (SCIM) works alongside federated SSO by providing a standardized REST API payload format to automatically create, update, and remove user identity records across external cloud services.

Step-by-Step Solution

1
Identify the requirement for federated single sign-on across third-party SaaS services.
Recognize that Security Assertion Markup Language (SAML) enables secure exchange of authentication assertions between an Identity Provider (IdP) and Service Providers (SP).
Federated SSO relies on standard protocols like SAML or OIDC to pass identity tokens securely.
2
Identify the requirement for automated user lifecycle and account provisioning.
Recognize that System for Cross-domain Identity Management (SCIM) automates creating, updating, and deprovisioning user accounts across distinct identity domains.
SCIM uses RESTful APIs to sync user store changes automatically.

Key Concept

Federated Identity and Automated Provisioning Standards
Estimated Time:1m 0s
Question 288Question

A security architect is establishing high availability and resilience specifications for a mission-critical infrastructure deployment. Match each resiliency requirement or architectural challenge on the left with its corresponding technical mechanism or metric on the right.

Click a left item, then click its matching right item

Items

Eliminating single points of failure across web servers while seamlessly preserving active user sessions during node outages
Defining the maximum tolerable duration of data loss measured in time prior to an unplanned service disruption
Preventing data corruption caused by concurrent writes when heartbeat communication fails between cluster nodes
Providing storage-level disk redundancy allowing continuous operations despite a single drive failure

Matches

Show answer & explanation

Answer

The correct pairings are: 1. Preserving active user sessions across web server outages matches with Stateful Load Balancing with VIP failover; 2. Maximum tolerable duration of data loss matches with Recovery Point Objective (RPO); 3. Preventing data corruption during heartbeat failure matches with Node Fencing / STONITH; 4. Disk redundancy for continuous operation matches with RAID 5 / RAID 1 array configuration.
Each requirement directly aligns with its corresponding architectural control: RPO defines acceptable data loss interval; stateful load balancing preserves persistent connections across redundant nodes; STONITH node fencing prevents split-brain corruption in active-active/active-passive clusters; and RAID provides local disk fault tolerance.

Step-by-Step Solution

1
Analyze session-handling and network redundancy requirements.
Matched session preservation during server outage to Stateful Load Balancing with VIP failover.
Stateful load balancers track session state tables across cluster nodes, ensuring users remain logged in when traffic shifts.
2
Evaluate availability metrics for data recovery.
Matched data loss time threshold to Recovery Point Objective (RPO).
RPO measures acceptable data loss currency in units of time, whereas RTO measures acceptable duration of service disruption.
3
Analyze high-availability clustering split-brain safeguards.
Matched split-brain data corruption prevention to Node Fencing / STONITH.
When heartbeat lines fail, automated fencing mechanisms disable the disconnected node to guarantee exclusive write lock on shared storage.
4
Identify hardware-level redundancy controls.
Matched single-drive failure protection to RAID configurations.
RAID 1 (mirroring) and RAID 5 (striping with parity) provide hardware fault tolerance for storage volumes.

Key Concept

Resilience, High Availability, and Redundancy Mechanisms
Question 289Question

An enterprise security architect is evaluating modern Identity and Access Management (IAM) controls to enforce Zero Trust principles and streamline federated access across a multi-cloud enterprise. Match each identity architecture protocol or mechanism on the left to its corresponding architectural implementation on the right.

Click a left item, then click its matching right item

Items

Continuous Access Evaluation Protocol (CAEP)
System for Cross-domain Identity Management (SCIM)
Privileged Access Management (PAM) with Ephemeral Credentials
OAuth 2.0 Demonstration of Proof-of-Possession (DPoP)

Matches

Show answer & explanation

Answer

Continuous Access Evaluation Protocol (CAEP) matches real-time session state and posture event sharing; System for Cross-domain Identity Management (SCIM) matches automated identity lifecycle provisioning across SaaS applications; Privileged Access Management (PAM) with Ephemeral Credentials matches eliminating static administrative credentials via short-lived access rights; and OAuth 2.0 Demonstration of Proof-of-Possession (DPoP) matches cryptographically binding tokens to client key pairs to prevent replay attacks.
Continuous Access Evaluation Protocol (CAEP) allows identity providers and relying parties to exchange real-time security events such as session revocation or risk score changes. System for Cross-domain Identity Management (SCIM) standardizes user provisioning workflows to automate account lifecycle events between identity stores and SaaS applications. Privileged Access Management (PAM) with ephemeral credentials reduces attack surfaces by dynamically issuing short-lived administrative credentials on demand rather than maintaining standing privileges. OAuth 2.0 Demonstration of Proof-of-Possession (DPoP) secures API access by binding OAuth tokens to a client's private key, preventing intercepted bearer tokens from being replayed.

Step-by-Step Solution

1
Analyze the functional scope of each identity architecture protocol and component listed on the left.
CAEP provides real-time event-driven access evaluation; SCIM handles automated user account lifecycle management; PAM with ephemeral credentials handles short-lived privileged access; DPoP enforces token sender-constraining.
Determining the primary architectural boundary addressed by each standard is required to pair them correctly.
2
Correlate each architectural component to its matching enterprise use case on the right.
CAEP correlates to real-time posture event sharing for immediate session revocation; SCIM correlates to identity provisioning across cloud SaaS platforms; PAM ephemeral credentials correlate to eliminating standing credentials with just-in-time access; DPoP correlates to binding tokens to client private keys to stop token replay.
Each mechanism addresses a specific aspect of modern IAM architecture, including session security, identity lifecycle, privilege management, and API token security.

Key Concept

Enterprise IAM Architecture Protocols and Control Frameworks
Question 290Question

An enterprise security architect is designing a modern Identity and Access Management (IAM) architecture to support a hybrid enterprise workforce. The solution must provide phishing-resistant, passwordless authentication for corporate users accessing cloud services, while automatically synchronizing user onboarding, role updates, and offboarding privileges from the central Identity Provider (IdP) to external Software as a Service (SaaS) platforms in near real-time. Which of the following protocols or standards should the architect integrate into the IAM architecture to fulfill these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: WebAuthn / FIDO2 framework to establish challenge-response authentication using asymmetric key pairs bound to origin domains; System for Cross-domain Identity Management (SCIM) RESTful API schema to automate cloud account provisioning and lifecycle attribute sync

Answer

The architect must integrate the WebAuthn / FIDO2 framework for passwordless phishing-resistant authentication and the System for Cross-domain Identity Management (SCIM) standard for automated user provisioning.
WebAuthn / FIDO2 supplies passwordless, origin-bound public key authentication that inherently resists social engineering and phishing attacks. System for Cross-domain Identity Management (SCIM) provides the standardized REST API specifications necessary to push real-time user creation, modifications, and revocations from the IdP to cloud SaaS services.

Step-by-Step Solution

1
Analyze the requirement for phishing-resistant, passwordless authentication across cloud services.
Identify WebAuthn / FIDO2 as the standard architectural specification that uses hardware-bound public-key cryptography to prevent phishing and credential harvest attacks.
WebAuthn binds credentials directly to the website origin, preventing relay attacks common in legacy MFA.
2
Analyze the requirement for automated cross-domain identity lifecycle synchronization (onboarding, role changes, offboarding) to cloud SaaS platforms.
Identify System for Cross-domain Identity Management (SCIM) as the industry standard protocol designed for managing user identity lifecycles across distinct domains via HTTP REST APIs.
SCIM standardizes user object schemas and endpoints so IdPs can push automated creation, update, and deprovisioning events to SaaS targets.
3
Evaluate and eliminate non-viable architectural choices.
Reject direct internal LDAPS exposures due to network perimeter risks and reject OAuth 2.0 Implicit Grant due to security deprecation and its functional focus on access delegation rather than provisioning.
Ensures adherence to modern Zero Trust architecture and secure IAM protocol separation.

Key Concept

Identity and Access Management Architecture: Phishing-Resistant Authentication and Automated Lifecycle Provisioning
Estimated Time:2m 0s
Question 291Question

A security engineer is establishing defense-in-depth security controls for an enterprise cloud platform hosting both application containers and virtual machines. Match each security control mechanism to its primary protective function.

Click a left item, then click its matching right item

Items

Rootless Container Execution
Microsegmentation
Hypervisor Hardening
Secrets Management Daemon

Matches

Show answer & explanation

Answer

Rootless Container Execution pairs with preventing host root compromise by running under unprivileged accounts; Microsegmentation pairs with restricting internal east-west traffic between microservices; Hypervisor Hardening pairs with mitigating VM escape risks by minimizing hypervisor attack surface; Secrets Management Daemon pairs with dynamically injecting sensitive runtime credentials into memory.
Rootless container execution restricts the container engine daemon to an unprivileged user ID, limiting damage if the container sandbox fails. Microsegmentation enforces policy-driven network boundaries between microservices to prevent unauthorized lateral movement inside the cluster. Hypervisor hardening reduces the attack surface of the virtualization layer to block guest-to-host VM escape exploits. Secrets management daemons dynamically deliver runtime tokens and API keys, ensuring sensitive credentials are never baked into container images.

Step-by-Step Solution

1
Analyze host account privileges for container runtimes
Identified Rootless Container Execution as the control preventing root-level host access during a runtime breach.
If a container runs as non-root on the host OS, a process escape inherits only restricted user rights on the host.
2
Evaluate internal network traffic controls across virtualized workloads
Matched Microsegmentation to granular east-west traffic restrictions between container instances.
Microsegmentation applies policy-based network separation directly to workload interfaces independent of physical VLAN boundaries.
3
Examine hypervisor security boundaries separating guest VMs from host resources
Associated Hypervisor Hardening with mitigation of VM escape vulnerabilities.
Removing unneeded virtual devices and patching the hypervisor prevents guests from interacting directly with underlying hardware or hypervisor host memory.
4
Assess secret storage and injection practices for containerized applications
Paired Secrets Management Daemon with dynamic runtime credential injection.
Storing credentials inside container image layers creates persistent exposure; external secret management ensures ephemeral dynamic delivery.

Key Concept

Virtualization and Containerization Security Mechanisms
Question 292Question

A security engineer is configuring a high-availability perimeter firewall pair using Virtual Router Redundancy Protocol (VRRP) to eliminate single points of failure at the default gateway. During failover testing, when the primary firewall is forcibly rebooted, downstream clients experience dropped sessions and must re-authenticate and re-establish all TCP connections, even though the standby appliance immediately claims the virtual IP address. Which mechanism must be implemented alongside virtual IP redundancy to preserve established network sessions during an unexpected failover?

Show answer & explanation

Answer: Stateful connection table synchronization across cluster nodes

Answer

Stateful connection table synchronization across cluster nodes is required to preserve live connections during failover.
Stateful connection table synchronization continuously mirrors transient firewall session states (such as TCP connection tracking and NAT translation tables) from the active node to the passive node. When the virtual IP shifts via VRRP, the secondary appliance already possesses the full session context, allowing active client connections to continue uninterrupted without requiring re-authentication.

Step-by-Step Solution

1
Analyze the failure symptom in the scenario
Virtual IP failover works correctly (layer 3 IP address transfer), but active TCP sessions are dropped.
VRRP only manages virtual IP address ownership and network routing; it does not replicate layer 4-7 state memory between firewall appliances.
2
Identify the missing high-availability component
Stateful connection table synchronization (e.g., conntrackd or pfsync) is required.
Without state synchronization, the new active firewall views existing client connections as invalid or unrecognized state transitions and drops them.
3
Evaluate candidate options against requirements
Stateful connection table synchronization fulfills the zero-session-drop requirement.
Hardware disk mirroring (RAID 1), DHCP scopes, and configuration backups address local disk storage fault tolerance, IP leasing resilience, and disaster recovery configuration management respectively, not live session persistence.

Key Concept

High-Availability Stateful Session Synchronization vs Virtual IP Failover
Estimated Time:2m 0s
Question 293Question

An IT administrator is deploying a centralized log server that must remain operational without downtime if an individual hard drive suffers a physical failure. Which of the following technologies should the administrator implement to provide this real-time storage fault tolerance?

Show answer & explanation

Answer: Redundant Array of Independent Disks (RAID)

Answer

Redundant Array of Independent Disks (RAID) should be implemented because it provides real-time disk redundancy and storage fault tolerance, enabling the system to sustain a hard drive failure without server downtime.
Redundant Array of Independent Disks (RAID) mirrors or stripes data with parity across multiple physical drives. This ensures that if a single drive fails, the system continues functioning without loss of availability or data.

Step-by-Step Solution

1
Identify the system requirement from the scenario
The server requires immediate storage-level fault tolerance to maintain continuous uptime during a single hard drive failure.
Hardware fault tolerance at the storage layer prevents service interruption.
2
Evaluate the technical redundancy controls available
RAID mirrors or stripes data with parity across multiple physical hard drives, allowing the server to operate continuously despite a single disk failure.
RAID directly addresses physical storage media redundancy.

Key Concept

Redundant Array of Independent Disks (RAID) storage fault tolerance
Question 294Question

An enterprise aerospace contractor is modernizing its IT infrastructure across diverse cloud environments. Match each enterprise workload scenario on the left with the corresponding cloud service or deployment model on the right that best represents its architecture.

Click a left item, then click its matching right item

Items

Custom telemetry processing engine requiring direct operating system kernel configuration and virtual machine root administrative control.
Customer service ticketing application maintained completely by an external vendor, where internal IT only manages user access and support workflows.
Event-driven backend component that executes lightweight data transformation code triggered by file uploads without persistent server instances.
Shared threat intelligence platform co-owned and accessed exclusively by member defense organizations operating under identical regulatory frameworks.

Matches

Show answer & explanation

Answer

The correct pairings match each workload requirement to its underlying operational model: virtual machine and OS administrative control maps to Infrastructure as a Service (IaaS); complete vendor application management maps to Software as a Service (SaaS); event-triggered serverless code execution maps to Function as a Service (FaaS); and infrastructure shared exclusively among organizations with common mission objectives maps to Community Cloud.
Each workload scenario correctly aligns with the scope of responsibility and deployment boundaries defined by the respective cloud models: IaaS grants OS-level control; SaaS abstracts application infrastructure; FaaS provides event-driven serverless execution; and Community Cloud serves a closed group of organizations with shared security requirements.

Step-by-Step Solution

1
Analyze the workload requiring OS kernel tuning and root administrative control over virtual machines.
Identify that managing the OS layer while relying on the provider for virtualization and physical hardware defines Infrastructure as a Service (IaaS).
IaaS provides raw compute infrastructure where the consumer maintains control over operating systems, storage, and deployed applications.
2
Evaluate the customer support application managed end-to-end by an external vendor.
Identify that consuming a fully hosted application while managing only application-level user access defines Software as a Service (SaaS).
SaaS abstracts all infrastructure, operating system, and application maintenance from the consumer.
3
Assess the short-lived event-driven data transformation execution.
Identify that running microservice logic on demand without provisioning infrastructure defines Function as a Service (FaaS) / Serverless.
FaaS executes ephemeral code units on demand, shifting server provisioning and scaling responsibility entirely to the cloud provider.
4
Examine the shared threat feed infrastructure restricted to specific vetted defense partner organizations.
Identify that a multi-tenant environment limited to distinct member organizations with shared regulatory needs defines a Community Cloud.
Community Cloud deployment models pool infrastructure specifically to support a specific community that shares common requirements or compliance mandates.

Key Concept

Cloud Service and Deployment Model Taxonomy
Question 295Question

A security administration team needs to centralize management for administrative console logins across enterprise network routers and switches. The architectural requirements specify that authentication must be decoupled from authorization to enforce granular per-command permissions, and the entire transmission packet body must be encrypted. Which protocol should the team implement?

Show answer & explanation

Answer: Terminal Access Controller Access-Control System Plus (TACACS+)

Answer

Terminal Access Controller Access-Control System Plus (TACACS+) is the correct protocol as it encrypts the full packet payload and completely separates authentication and authorization operations.
Terminal Access Controller Access-Control System Plus (TACACS+) fulfills all architectural criteria by encrypting the full payload of every packet and modularizing AAA functions, allowing administrators to restrict and audit specific commands executed on network hardware.

Step-by-Step Solution

1
Analyze the technical requirements in the stem
Identified two primary requirements: full packet encryption and separation of authentication from command-level authorization for administrative network access.
Selecting an appropriate IAM architecture protocol requires matching key operational features to explicit requirements.
2
Compare protocol capabilities against security requirements
TACACS+ uses TCP port 49, encrypts all packet contents after the header, and separates AAA functions. RADIUS uses UDP, encrypts only passwords, and combines authentication with authorization.
Determines which AAA architectural protocol fulfills both granular authorization and packet protection specifications.

Key Concept

TACACS+ vs RADIUS Architecture in Device Management
Estimated Time:45s
Question 296Question

An organization is modernizing its deployment architecture by hosting multiple containerized microservices on a shared host operating system. During a technical audit, a security analyst discovers that microservices run with standard system privileges, exposing the host operating system kernel to potential privilege escalation via unauthorized system calls if a container is compromised. Which of the following controls should the security team implement on the container host to restrict the specific system calls available to container processes?

Show answer & explanation

Answer: Apply custom Secure Computing Mode (seccomp) profiles to filter syscall access for container processes.

Answer

Apply custom Secure Computing Mode (seccomp) profiles to filter syscall access for container processes.
Applying Secure Computing Mode (seccomp) profiles allows administrators to define explicit whitelist filters for system calls (syscalls). Since containers share the underlying host kernel, restricting unneeded syscalls effectively mitigates kernel privilege escalation and container escape attacks.

Step-by-Step Solution

1
Analyze the container risk environment
Containers execute directly on the host host operating system and share the host Linux kernel.
Because kernel code is shared across all containers running on the host, a kernel vulnerability or unrestrained system call execution could allow container escape.
2
Evaluate system call restriction mechanisms
Seccomp acts as a kernel-level system call filter that limits which syscalls a container process can make.
Restricting available syscalls via seccomp profiles prevents containers from calling unnecessary or high-risk kernel routines.

Key Concept

Kernel System Call Filtering (Seccomp) in Container Security
Question 297Question

A security architect is designing an identity and access management (IAM) infrastructure for an enterprise microservices environment. The organization requires that OAuth 2.0 access tokens issued to client applications are sender-constrained, ensuring that if a token is intercepted in transit, it cannot be replayed by an unauthorized third party to access downstream APIs. Which of the following architectural solutions best satisfies this security requirement?

Show answer & explanation

Answer: Implement Demonstration of Proof-of-Possession (DPoP) to cryptographically bind access tokens to a client-generated key pair.

Answer

Demonstration of Proof-of-Possession (DPoP) cryptographically binds access tokens to a client-generated key pair to prevent token replay attacks.
Demonstration of Proof-of-Possession (DPoP) is an extension to OAuth 2.0 that binds access tokens to a specific cryptographic key pair owned by the client. When making API requests, the client must generate and sign a fresh DPoP proof header using its private key. Because an attacker intercepting the token lacks the corresponding private key, they cannot generate a valid signature, effectively neutralizing token replay attacks.

Step-by-Step Solution

1
Analyze the architectural requirement.
The scenario requires sender-constraining OAuth 2.0 access tokens so that stolen or intercepted tokens cannot be reused by an adversary (preventing bearer token replay).
Standard bearer tokens can be used by any party holding them, making sender-binding essential for Zero Trust API security architectures.
2
Evaluate potential cryptographic token binding mechanisms.
Demonstration of Proof-of-Possession (DPoP) forces the client to present a unique signed DPoP proof header containing a public key matched to the issued token.
This binds the access token explicitly to the client's private key, rendering intercepted tokens useless to an attacker without access to that private key.
3
Differentiate from incorrect IAM standards and perimeter controls.
SCIM manages user account provisioning, SAML POST handles web browser single sign-on, and perimeter WAFs rely on network edge inspection rather than end-to-end client-bound token proofs.
None of these alternatives provide cryptographic sender-constraining of API access tokens.

Key Concept

OAuth 2.0 Token Binding and Sender-Constrained Tokens (DPoP)
Question 298Question

A cloud security architect is designing a resilient infrastructure for a critical financial transaction service deployed across two geographically distant cloud regions. To satisfy business requirements, the architecture must achieve a Recovery Point Objective (RPO) of zero (zero data loss) and a Recovery Time Objective (RTO) of near-zero in the event of an entire regional failure. Which TWO of the following architectural mechanisms must be deployed together to meet these strict availability and resilience targets?

Select all that apply

Show answer & explanation

Answer: Active-active multi-region application deployment utilizing synchronous database replication across regions; Global Server Load Balancing (GSLB) configured with real-time health monitoring and dynamic latency/failover routing

Answer

The correct architecture requires combining an active-active multi-region deployment utilizing synchronous database replication with Global Server Load Balancing (GSLB) featuring real-time health monitoring.
Achieving RPO = 0 (zero data loss) requires synchronous replication so that every write operation is committed in real time across geographically distributed database nodes. Achieving RTO = near-zero requires an active-active deployment supported by Global Server Load Balancing (GSLB), which continuously probes service health and instantly reroutes ingress traffic away from an impaired region to the surviving active region.

Step-by-Step Solution

1
Analyze RPO requirements for zero data loss
Identified that synchronous replication across active nodes is mandatory so that transactions are committed to both sites simultaneously prior to transaction confirmation.
Asynchronous replication or periodic snapshots allow data gaps between write intervals, failing the RPO = 0 mandate.
2
Analyze RTO requirements for near-zero downtime
Identified that active-active processing coupled with automated dynamic traffic distribution (GSLB) is necessary.
Both regions must actively process traffic or stand ready with live synchronized state so traffic rerouting occurs seamlessly without provisioning delays.
3
Evaluate and eliminate non-compliant disaster recovery approaches
Rejected point-in-time snapshots (causes data loss) and cold standby provisioning (causes service downtime).
Disaster recovery backups and cold sites are recovery controls, not continuous high-availability or zero-loss fault-tolerant controls.

Key Concept

High Availability, Synchronous Replication, and Global Load Balancing
Question 299Question

A maritime shipping container logistics terminal is modernizing its operational technology (OT) network and port management systems. The security architecture team is adopting Zero Trust Architecture (ZTA) principles to prevent unauthorized access between automated gantry crane control systems, IoT tracking sensors, and cloud management consoles. Which of the following architectural requirements represent core tenets of Zero Trust Architecture that must be implemented in this design? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Treat all network traffic as inherently untrusted regardless of whether the source originates from inside or outside the physical enterprise perimeter.; Dynamically evaluate and continuously verify trust factors and security posture throughout the entirety of an active session.

Answer

The core tenets of Zero Trust Architecture include assuming no implicit trust based on network location (treating all traffic as untrusted regardless of origin) and continuously re-evaluating trust and posture dynamically throughout active sessions.
Zero Trust Architecture relies on the tenets of 'never trust, always verify' and 'assume breach'. Traffic originating from internal subnets must be treated with the same scrutiny as external traffic. Furthermore, access decisions are dynamic and subjected to continuous verification during active sessions rather than relying on a single login event.

Step-by-Step Solution

1
Analyze core principles of Zero Trust Architecture (NIST SP 800-207)
Identified that Zero Trust mandates explicit verification, assumed breach, least privilege access, and continuous monitoring regardless of network location.
Traditional perimeter-based security models fail when internal networks are assumed to be safe.
2
Evaluate the requirement for perimeter-independent trust management
Selecting the requirement to treat all traffic as untrusted regardless of origin aligns directly with the 'assume breach' and 'explicit verification' tenets.
Location within an enterprise network does not guarantee security or non-malicious behavior.
3
Evaluate continuous authentication vs. static initial checks
Selecting continuous dynamic posture evaluation ensures sessions are reassessed continuously as contextual risk attributes change.
Initial authentication checks cannot detect mid-session compromises or device posture degradation.

Key Concept

Zero Trust Architecture Principles
Question 300Question

A pharmaceutical research organization is updating its storage architecture to host confidential genomic sequencing datasets. The security architect must satisfy two primary requirements: guarantee bulk data encryption at rest on storage area network (SAN) arrays without degrading host processing performance, and prevent research data from being copied to unauthorized physical media or unapproved endpoints. Which of the following technical security solutions should the architect select to meet these requirements? (Select TWO)

Select all that apply

Show answer & explanation

Answer: Deploy Self-Encrypting Drives (SEDs) utilizing hardware-based cryptographic controllers on the SAN storage arrays; Deploy an enterprise Data Loss Prevention (DLP) solution configured with endpoint and storage monitoring policies

Answer

The architect should deploy Self-Encrypting Drives (SEDs) on the SAN storage arrays and implement an enterprise Data Loss Prevention (DLP) solution with endpoint monitoring policies.
Deploying Self-Encrypting Drives (SEDs) satisfies the requirement for transparent, hardware-accelerated bulk data encryption without imposing software encryption overhead on host CPUs. Implementing Data Loss Prevention (DLP) directly controls data movements on endpoints, enforcing rules to inspect content and block unauthorized file transfers to removable media.

Step-by-Step Solution

1
Evaluate the requirement for high-performance bulk data encryption at rest.
Determine that hardware-based encryption using Self-Encrypting Drives offloads crypto operations from the CPU, maintaining storage performance.
Software bulk encryption adds heavy computational overhead on host processors.
2
Evaluate the requirement to prevent unauthorized copying of sensitive datasets to removable drives or unapproved endpoints.
Determine that an enterprise Data Loss Prevention (DLP) agent on endpoints can monitor and block unauthorized egress and USB copying.
DLP specifically monitors data in use and data on endpoints to enforce compliance rules against data exfiltration.

Key Concept

Data Protection and Storage Security Architecture
PreviousPage 15 / 21Next
Security Architecture Practice Questions — CompTIA Security+ — Page 15 | Examkin