Security Architecture

405 questions

Question 101Question

An enterprise organization is migrating a mission-critical web service to a public cloud Infrastructure as a Service (IaaS) environment utilizing customer-managed virtual machines behind a cloud provider's network load balancer. Under the cloud Shared Responsibility Model, which of the following security functions remain the explicit responsibility of the enterprise security team? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Configuring guest operating system security patches and host-based firewall policies on the deployed virtual machines.; Defining application data access controls and configuring customer-managed encryption for data stored within cloud volumes.

Answer

The enterprise security team is responsible for configuring guest operating system patches and host firewalls, as well as managing application data access controls and storage volume encryption.
Under Infrastructure as a Service (IaaS), the cloud service provider manages the underlying physical facilities, hardware, and hypervisor abstraction layer. The customer retains explicit responsibility for configuring, patching, and securing everything above the hypervisor layer, including guest operating systems, host-based firewalls, identity permissions, and data encryption.

Step-by-Step Solution

1
Identify the cloud service model specified in the scenario
The scenario explicitly describes Infrastructure as a Service (IaaS) using customer-managed virtual machines.
Establishing the cloud service model (IaaS vs. PaaS vs. SaaS) defines the baseline operational division between the cloud provider and the enterprise.
2
Differentiate provider duties from customer duties in an IaaS architecture
The Cloud Service Provider (CSP) manages physical facilities, host hardware, power, physical networking, and hypervisors. The customer manages guest OS instances, network configuration within the virtual network, application code, data security, and IAM.
IaaS provides raw virtualized compute and storage, delegating everything above the hypervisor layer to the cloud customer.
3
Evaluate the candidate security duties against customer obligations
Guest OS patching, host firewalls, access permission definitions, and storage volume encryption are customer responsibilities.
Hypervisor management belongs to the provider, while relying solely on edge perimeters violates modern defense-in-depth and Zero Trust principles.

Key Concept

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

A biomedical research organization is implementing an event-driven serverless (Function-as-a-Service) workflow to process sensitive genomic datasets. The solution operates within a community cloud model shared among research partners and integrates with an on-premises data repository via a secure hybrid connection. The security architecture team must define strict operational responsibilities in accordance with the cloud shared responsibility model. Which of the following security management tasks remain the direct responsibility of the biomedical research organization? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Configuring function-level identity authorization policies and managing data classification rules for the genomic datasets; Managing customer-managed encryption keys (CMEK) and defining API gateway access token validation logic

Answer

The research organization is directly responsible for configuring function-level authorization policies with data classification rules, as well as managing customer-managed encryption keys (CMEK) alongside API gateway access token validation logic.
In serverless architecture (FaaS), the Cloud Service Provider manages the underlying hardware, hypervisors, server OS, and runtime infrastructure. However, the customer retains sole responsibility for data governance (classification and encryption key management) and identity control (API access token rules and function authorization policies).

Step-by-Step Solution

1
Analyze the cloud service model
Identified Function-as-a-Service (FaaS / Serverless) architecture.
Serverless abstracts away server management, shifting OS, runtime, and hypervisor patching entirely to the Cloud Service Provider.
2
Evaluate data and identity security responsibilities
Customer retains 100% control over data classification, encryption key governance, and identity access rules.
Regardless of deployment model (Public, Private, Hybrid, Community), data security and identity management belong strictly to the tenant.
3
Select correct customer responsibilities
Configuring function-level authorization/data classification and managing CMEK/API validation rules are customer responsibilities.
These controls govern data protection and application access logic, which are customer-managed duties.

Key Concept

Cloud Shared Responsibility Model in FaaS / Serverless Deployments
Question 103Question

A healthcare technology enterprise deploys an event-driven application using cloud-managed API gateways, serverless execution functions (FaaS), and a managed NoSQL database service to ingest patient telemetry data. The chief information security officer (CISO) requires a security matrix mapping operational duties under the cloud service provider's shared responsibility model for serverless workloads. Which of the following tasks is exclusively the responsibility of the customer organization?

Show answer & explanation

Answer: Writing secure application logic, defining granular function access permissions, and managing data payload encryption key policies

Answer

Writing secure application logic, defining granular function access permissions, and managing data payload encryption key policies
Under the cloud shared responsibility model for serverless (Function as a Service) deployments, the cloud provider abstracts away infrastructure, host operating systems, and runtime engines. The customer remains fully accountable for secure application coding practices, configuring Identity and Access Management (IAM) role privileges assigned to functions, validating input data, and encrypting sensitive data at rest and in transit.

Step-by-Step Solution

1
Analyze the cloud service abstraction level in the scenario
Identified the architecture as a serverless (FaaS) and managed platform deployment where hardware, virtualization, and host operating systems are abstracted away by the CSP.
Serverless architectures shift low-level infrastructure management (OS patching, runtime maintenance) to the cloud service provider.
2
Evaluate operational responsibilities under the Shared Responsibility Model for FaaS
Determined that the customer remains responsible for application code, IAM role definitions, API configuration, and data security.
Even in highly abstracted serverless environments, customers always own their data, access management logic, and application code security.

Key Concept

Cloud Shared Responsibility Model in Serverless (FaaS) Architecture
Question 104Question

A network security technician is configuring access controls for a healthcare portal. The technician establishes a system that continuously authenticates user identity, validates device compliance, and evaluates permissions for every resource request, even when traffic originates from within the internal corporate network. Which core principle of Zero Trust Architecture is directly demonstrated by this implementation?

Show answer & explanation

Answer: Explicit verification of every access request regardless of network location

Answer

Explicit verification of every access request regardless of network location
The correct answer highlights explicit verification, which is a foundational tenet of Zero Trust Architecture requiring that all access requests be authenticated, authorized, and continuously validated regardless of where the request originates.

Step-by-Step Solution

1
Analyze the access control scenario requirements
Identified continuous authentication, device status checking, and per-request authorization both inside and outside the corporate network.
Understanding the operational behavior helps align it with foundational architectural principles.
2
Evaluate against Zero Trust Architecture core tenets
The requirement to verify every user, device, and request continuously aligns directly with 'explicit verification' ('never trust, always verify').
Zero Trust mandates removing implicit trust tied to internal IP addresses or network perimeters.

Key Concept

Zero Trust Explicit Verification
Estimated Time:45s
Question 105Question

A logistics company migrates its core inventory database to a public cloud Infrastructure as a Service (IaaS) environment using custom virtual machine instances. Under the cloud shared responsibility model, which of the following tasks is the sole operational security responsibility of the customer enterprise?

Show answer & explanation

Answer: Applying operating system security updates and configuring host-based firewalls on virtual machines

Answer

Applying operating system security updates and configuring host-based firewalls on virtual machines is the sole operational security responsibility of the customer enterprise.
In Infrastructure as a Service (IaaS), the cloud provider is responsible for securing the underlying physical infrastructure, virtualization hypervisors, and data center facilities. The customer enterprise retains total administrative responsibility for everything running above the hypervisor layer, including installing, patching, and hardening guest operating systems, as well as managing host-based network controls.

Step-by-Step Solution

1
Identify the cloud service model referenced in the enterprise scenario
The scenario specifies an Infrastructure as a Service (IaaS) deployment model.
Security responsibilities vary depending on whether IaaS, PaaS, or SaaS is implemented.
2
Differentiate shared responsibility boundaries between the Cloud Service Provider (CSP) and the customer for IaaS
The CSP manages physical data centers, physical hardware, power, facility security, and hypervisors. The customer manages guest operating systems, application code, data classification, and virtual network configuration.
IaaS provides raw compute and storage infrastructure, leaving operating system control with the tenant.
3
Select the task aligned with customer-managed IaaS responsibilities
Guest operating system security patching and host firewall configuration fall directly on the customer enterprise.
The CSP cannot access or modify the internal guest OS software stack managed by the customer without explicit tenant access.

Key Concept

Cloud Shared Responsibility Model (IaaS)
Question 106Question

A security architect is designing the network architecture for a manufacturing facility. The site contains a legacy Industrial Control System (ICS) operating sensitive Programmable Logic Controllers (PLCs), alongside an automated telemetry module that needs to push real-time performance metrics to a cloud analytics provider. Enterprise security policy mandates that external cloud systems and corporate IT networks must be strictly prevented from sending incoming traffic back into the ICS network segment. Which of the following network architecture designs best fulfills these security requirements?

Show answer & explanation

Answer: Deploy a unidirectional security gateway (data diode) to enforce hardware-based physical layer flow control, permitting outbound telemetry data while physically preventing any inbound network traffic into the ICS environment.

Answer

Deploying a unidirectional security gateway (data diode) to enforce hardware-based physical layer flow control, permitting outbound telemetry data while physically preventing inbound traffic into the ICS environment.
Deploying a unidirectional security gateway (data diode) physically enforces one-way communication at Layer 1. This allows outbound telemetry flow to cloud systems while physically blocking any inbound connection attempts, perfectly satisfying the requirement to isolate critical ICS assets from external network threats.

Step-by-Step Solution

1
Analyze security and architectural requirements
The requirement specifies outbound telemetry data export to the cloud while enforcing a zero-risk policy against inbound network connections into the legacy ICS network segment.
Legacy Industrial Control Systems (ICS/SCADA) and PLCs often lack modern host security controls, making them highly vulnerable to network-based exploits and lateral movement.
2
Evaluate network isolation technologies
A data diode (unidirectional gateway) provides a physical, hardware-based guarantee that data can only travel in one direction.
Unlike software firewalls or VLAN access control lists (ACLs) that could be misconfigured or bypassed via software flaws, a data diode physically lacks the hardware receiver components in the return direction.
3
Eliminate non-compliant isolation mechanisms
Perimeter firewalls with implicit internal trust, dual-homed jump host bridging, and passive NIDS sensors fail to provide non-bypassable unidirectional isolation.
Firewalls and VLANs remain vulnerable to misconfiguration or logical exploits, while NIDS sensors only detect activity rather than preventing inbound connection establishment.

Key Concept

Unidirectional Data Diodes and OT/ICS Network Segmentation
Estimated Time:1m 30s
Question 107Question

A network security architect is implementing defense-in-depth segmentation to secure access from external users to an isolated internal backend database. Arrange the network transit points and security control boundaries in the correct sequence through which inbound traffic must flow from the untrusted Internet to the database server.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct ingress sequence flows from the Perimeter WAF in the DMZ, to the Reverse Proxy/API Gateway in the Public Services Subnet, through the Internal Microsegmentation Firewall, and finally to the Database Subnet ACL and Host Firewall.
Secure network architecture mandates a defense-in-depth approach where inbound traffic traverses from public edge boundaries to increasingly restrictive internal zones. Traffic first enters the DMZ via the Perimeter WAF, moves to the API Gateway in the public services tier for authentication, passes through an internal microsegmentation firewall inspecting East-West flows, and lastly encounters the Database Subnet ACL and Host Firewall enforcing strict destination isolation.

Step-by-Step Solution

1
Filter North-South traffic at the network edge
Untrusted external traffic is inspected by the Perimeter WAF in the DMZ.
Perimeter security controls must evaluate incoming public requests first to block common web attacks before traffic reaches internal endpoints.
2
Terminate external connections and validate application requests
The Reverse Proxy/API Gateway handles session termination and request verification.
De-encapsulating and authenticating requests in a public-facing service subnet prevents unverified external clients from directly connecting to internal application instances.
3
Enforce East-West microsegmentation boundaries
The Internal Microsegmentation Firewall evaluates traffic traveling between application tiers.
Microsegmentation prevents lateral movement by explicitly inspecting and controlling data flows transitioning across internal zone boundaries.
4
Apply host and subnet-level isolation controls
Database Subnet ACLs and Host Firewalls enforce zero trust rules at the target resource.
Final line-of-defense controls restrict access strictly to authorized source IP addresses and database-specific communication protocols.

Key Concept

Multi-tier network segmentation and zoning boundaries control the flow of ingress and lateral traffic across security zones based on least privilege and defense-in-depth.
Question 108Question

A healthcare organization deploys a microservice backend utilizing a serverless Function-as-a-Service (FaaS) architecture on a public cloud platform to ingest patient telemetry. Under the cloud shared responsibility model, which TWO of the following security tasks remain the responsibility of the organization rather than the cloud service provider?

Select all that apply

Show answer & explanation

Answer: Defining granular execution roles and access permissions within the cloud identity and access management framework; Performing static code analysis and enforcing input validation logic within the serverless function source code

Answer

The organization is responsible for defining granular identity and access management policies for function execution roles and performing code-level security mitigations within the serverless application source code.
In serverless (FaaS) architectures, the cloud service provider abstracts and manages the underlying server hardware, operating systems, and runtime execution engines. The customer retains full responsibility for security 'in' the cloud—specifically writing secure application code, sanitizing input data, and defining granular access permissions and identity policies for execution roles.

Step-by-Step Solution

1
Analyze the cloud service model (FaaS/Serverless).
Identify that the provider abstracts server hardware, OS patching, and runtime engine management.
Serverless architectures offload infrastructure provisioning and runtime operational duties to the cloud service provider.
2
Differentiate customer security duties from provider responsibility.
Determine that application logic, source code security, data validation, and IAM role access rights remain customer obligations.
Under the shared responsibility model, security 'in' the cloud (code, data, and access configurations) belongs to the customer, while security 'of' the cloud belongs to the provider.

Key Concept

Shared Responsibility Model in Serverless (FaaS) Architectures
Question 109Question

A security administrator needs to prevent smart building environmental sensors from communicating directly with internal servers holding confidential employee files on the company network. Which of the following secure network design techniques provides the most effective logical isolation for these sensors?

Show answer & explanation

Answer: Placing the sensors on a dedicated Virtual Local Area Network (VLAN) with restricted inter-VLAN routing

Answer

Placing the sensors on a dedicated Virtual Local Area Network (VLAN) with restricted inter-VLAN routing is the most effective approach for logically isolating IoT devices from sensitive internal resources.
Placing smart building sensors on a dedicated Virtual Local Area Network (VLAN) isolates their traffic into a distinct logical broadcast domain. With inter-VLAN routing rules or firewalls configured between subnets, lateral movement from compromised IoT devices to confidential internal servers is blocked.

Step-by-Step Solution

1
Identify the risk and segmentation requirement.
The smart sensors represent untrusted or low-security devices that share network access with high-value internal servers.
Unsecured IoT devices can be leveraged as entry points to laterally move across flat internal networks.
2
Evaluate network isolation techniques.
Creating a dedicated VLAN partitions the network at Layer 2/Layer 3, isolating broadcast domains.
Logical segmentation via VLANs coupled with firewall access control lists (ACLs) enforces boundary controls on internal traffic.

Key Concept

Logical Network Segmentation using VLANs
Question 110Question

A network administrator is designing a wireless architecture for a company branch office. The goal is to provide visitors with internet access while preventing them from accessing sensitive internal servers and local network resources. Which of the following controls should the administrator implement to achieve secure network segmentation? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Place visitor traffic on a dedicated guest VLAN isolated with Access Control Lists (ACLs) that restrict access to internal IP ranges.; Deploy the guest wireless gateway in a perimeter DMZ segment configured to route guest traffic directly to the internet gateway.

Answer

The correct controls are assigning visitor traffic to a dedicated guest VLAN with outbound ACLs and deploying the guest wireless gateway within a perimeter DMZ segment.
Isolating untrusted devices via a dedicated guest VLAN with strict ACLs and routing guest traffic through a perimeter DMZ segment ensures that guest packets cannot reach internal corporate resources while maintaining internet access.

Step-by-Step Solution

1
Identify the primary security requirement.
Visitors require internet connectivity but must be prohibited from communicating with internal corporate networks.
Preventing lateral movement from untrusted guest devices into internal subnets is a core objective of network segmentation.
2
Evaluate network segmentation controls.
Dedicated guest VLANs with ACLs and DMZ perimeter placement logically isolate untrusted traffic.
Both techniques enforce layer 2/3 boundary separation so guest packets cannot traverse into internal administrative zones.

Key Concept

Secure Network Design and Segmentation
Estimated Time:1m 0s
Question 111Question

A multinational technology company is migrating its customer analytics workloads to a managed Platform as a Service (PaaS) cloud architecture. Under this service model, the Cloud Service Provider (CSP) manages the physical hardware, hypervisors, database engine software, and underlying operating system runtime environments. The company's security engineering team must establish appropriate security architecture controls for the hosted applications and sensitive data. Under the cloud shared responsibility model, which of the following tasks remains the sole responsibility of the customer organization?

Show answer & explanation

Answer: Configuring application-level access permissions, client data classification policies, and database user authorization schemas.

Answer

Configuring application-level access permissions, client data classification policies, and database user authorization schemas.
Under the cloud shared responsibility model for Platform as a Service (PaaS), the cloud service provider manages the physical data center, hardware infrastructure, hypervisor, and operating system runtime environment. The tenant organization retains full ownership and responsibility for securing its application code, user authorization configurations, data classification, and stored datasets.

Step-by-Step Solution

1
Analyze the cloud deployment model specified in the scenario.
The scenario describes a Platform as a Service (PaaS) deployment model.
Identifying the cloud model (PaaS) establishes the boundary line for shared responsibility between the CSP and the tenant.
2
Determine the cloud service provider's operational duties under PaaS.
The CSP manages physical infrastructure, network infrastructure, virtualization, host OS kernel patching, and database engine maintenance.
PaaS abstracts hardware and OS layers away from the customer so developers can focus on application code and data.
3
Determine the customer organization's remaining security responsibilities.
The customer is always responsible for data classification, application logic security, customer user account authorization, and API client configuration.
Regardless of whether IaaS, PaaS, or SaaS is used, ownership of data classification and access authorization remains strictly with the customer organization.

Key Concept

Cloud Shared Responsibility Model in Platform as a Service (PaaS)
Question 112Question

An enterprise financial institution is establishing a multi-tenant Community Cloud deployment model shared exclusively among partner credit unions to host a real-time collaborative fraud detection platform. The platform is constructed using managed Platform as a Service (PaaS) microservices that process customer transactions. The enterprise security architect must define control boundaries according to the cloud shared responsibility model and Zero Trust principles. Which of the following security responsibilities rests exclusively with the participating organization's security team?

Show answer & explanation

Answer: Defining granular application API authorization policies and managing customer data classification logic

Answer

Defining granular application API authorization policies and managing customer data classification logic is the sole responsibility of the tenant organization.
Under the cloud shared responsibility model for Platform as a Service (PaaS) and Community Cloud environments, the cloud service provider manages physical facilities, hypervisors, and runtime infrastructure. The participating customer organizations remain exclusively responsible for securing their data, defining data classification schemes, and configuring application-level access control and API authorization policies.

Step-by-Step Solution

1
Analyze the cloud deployment model (Community Cloud) and service model (Platform as a Service - PaaS).
PaaS abstracts the underlying operating systems, runtime engines, and hardware infrastructure, assigning their maintenance to the cloud service provider.
Understanding the abstraction layer isolates tenant responsibilities from provider responsibilities.
2
Evaluate the cloud shared responsibility boundary for PaaS environments.
The customer is always responsible for data governance, application-layer identity/access management (IAM), data classification, and API security policies.
Regardless of deployment model, customer data and application access controls never shift to the cloud service provider.
3
Align responsibility allocation with architectural constraints (Zero Trust and regulatory requirements).
Defining explicit application authorization logic enforces data isolation across multi-tenant community boundaries.
Proper control placement ensures data protection without misassigning infrastructure duties.

Key Concept

Cloud Shared Responsibility Model in PaaS and Community Cloud Deployments
Question 113Question

An enterprise security architecture team is auditing security responsibility boundaries across diverse cloud deployment models and specialized security integrations. Which operational security responsibility correctly aligns with each cloud architecture or deployment model?

Click a left item, then click its matching right item

Items

API-based Cloud Access Security Broker (CASB)
On-Premises Private Cloud
Managed Platform as a Service (PaaS) Container Service
Community Cloud Deployment

Matches

Show answer & explanation

Answer

API-based CASB matches with enforcing policies out-of-band via direct provider APIs. On-Premises Private Cloud matches with retaining full control over physical hardware, hypervisors, and workloads. Managed PaaS Container Service matches with customer responsibility for application code and container images while provider manages the control plane. Community Cloud Deployment matches with sharing governance and costs among organizations with joint compliance goals.
Each deployment model and cloud architectural control has specific boundaries: API CASBs operate out-of-band via cloud APIs; On-Premises Private Clouds demand full physical and virtualization stack management by the enterprise; PaaS container platforms split responsibility between provider control planes and tenant container content; and Community Clouds distribute shared governance across multiple affiliated entities.

Step-by-Step Solution

1
Analyze API-based CASB operational architecture.
Identify out-of-band API integration as the defining characteristic compared to inline proxies.
API CASBs inspect data at rest and event logs directly via provider interfaces rather than intercepting active inline network traffic.
2
Evaluate On-Premises Private Cloud responsibility boundaries.
Confirm 100% customer responsibility for physical hardware, virtualization layer, and guest OS security.
Private clouds hosted locally do not offload any layer of physical or hypervisor security to a third-party cloud service provider.
3
Delineate PaaS managed container service responsibilities under the shared responsibility model.
Separate container application runtime security from infrastructure control plane security.
The provider secures the host OS, orchestrator nodes, and physical hardware, while the tenant secures container images and application code.
4
Classify Community Cloud deployment governance features.
Link to multi-organizational resource and governance sharing based on joint mission or regulatory needs.
Community clouds exist to service specific groups with common requirements (e.g., healthcare or government agencies).

Key Concept

Cloud Shared Responsibility Model and Cloud Architecture Integrations
Question 114Question

Match each Zero Trust Architecture (ZTA) functional component on the left with its corresponding operational role on the right.

Click a left item, then click its matching right item

Items

Policy Engine (PE)
Policy Administrator (PA)
Policy Enforcement Point (PEP)
Data Plane

Matches

Show answer & explanation

Answer

Policy Engine matches with evaluating security policies and context; Policy Administrator matches with issuing control commands to manage connections; Policy Enforcement Point matches with intercepting traffic and enforcing access controls; Data Plane matches with carrying actual application payload traffic.
Each Zero Trust architecture component serves a distinct role split across the control plane and data plane. The Policy Engine (PE) evaluates policies and context to determine authorization. The Policy Administrator (PA) generates signals and credentials to open or close sessions. The Policy Enforcement Point (PEP) acts as the inline mechanism enforcing access. The Data Plane carries the actual payload once allowed.

Step-by-Step Solution

1
Identify the decision-making brain of Zero Trust Architecture.
The Policy Engine (PE) processes rules and context to make authorization decisions.
ZTA relies on dynamic evaluation of trust before access is decided.
2
Identify the control signaling component.
The Policy Administrator (PA) executes decision commands to control connection establishment.
PA coordinates between the decision engine and enforcement mechanisms.
3
Identify the inline gatekeeper component.
The Policy Enforcement Point (PEP) directly inspects and controls subject access requests.
Enforcement must happen directly at the gateway or endpoint interface.
4
Identify the network layer responsible for user payload.
The Data Plane transports application user data separate from control signals.
NIST SP 800-207 mandates separation between the control plane and data plane.

Key Concept

Zero Trust Functional Components (NIST SP 800-207)
Question 115Question

A network security team is establishing a zero-trust transit pipeline for remote systems administrators managing a backend database server located in a restricted internal network zone. Place the traffic flow controls and access verification steps in the correct sequential order, from the initial remote connection request to establishing access on the target server.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence for administrative transit into a highly segmented database zone begins at the external perimeter VPN gateway with MFA, proceeds to an isolated bastion host in a management DMZ, transitions through internal microsegmentation firewalls evaluating East-West traffic, and culminates with scoped authentication on the target database server.
Secure network architecture mandates defense-in-depth and strict boundary isolation. The correct order ensures that untrusted external traffic is authenticated at the perimeter VPN, proxied through a bastion host in a management DMZ, filtered through internal microsegmentation firewalls for East-West traffic control, and finally authorized at the destination asset using least-privilege credentials.

Step-by-Step Solution

1
Enforce North-South perimeter security and identity verification
Remote administrator connects via TLS VPN with MFA to gain ingress authorization.
Untrusted incoming connections must be encrypted and authenticated at the edge before any internal subnet exposure occurs.
2
Route administrative traffic to a jump server in the management DMZ
The user initiates an administrative proxy session on a hardened bastion host.
Direct management access from client endpoints to high-value internal assets violates secure segmentation principles. Bastions act as controlled proxies.
3
Enforce internal zone boundaries and microsegmentation filtering
Traffic from the jump server is inspected by internal firewalls filtering East-West network paths.
Internal segmentation controls ensure that even within internal zones, traffic crossing boundaries between management and database segments is explicitly validated.
4
Complete target host authentication in the restricted database segment
The session establishes to the target database server using scoped just-in-time credentials.
Final authentication and granular authorization occur directly at the target resource within the most restrictive network zone.

Key Concept

Bastion Transit Rules and Zone-based Microsegmentation Flow Controls
Estimated Time:2m 0s
Question 116Question

A financial enterprise security team mandates that every access request to sensitive payment processing services must be explicitly authenticated, authorized, and encrypted, regardless of whether the request originates from an internal office workstation or a remote home connection. Which core principle of Zero Trust Architecture does this policy directly demonstrate?

Show answer & explanation

Answer: Explicit verification of every access request regardless of user location or network origin

Answer

Explicit verification of every access request regardless of user location or network origin
Zero Trust Architecture operates on the fundamental principle of explicit verification ('never trust, always verify'). Every access request must be continuously authenticated, authorized, and encrypted using all available context (such as user identity, location, device health, and data sensitivity) regardless of whether the request originates inside or outside the traditional corporate network.

Step-by-Step Solution

1
Analyze the enterprise security requirement described in the stem.
The policy requires strict authentication, authorization, and encryption for every single connection attempt, treating internal and external network locations identically.
Identifying the operational boundary and access conditions enforced by the policy.
2
Map the requirement to established Zero Trust Architecture tenets.
The requirement directly aligns with the foundational Zero Trust principle of explicit verification ('never trust, always verify').
Zero Trust eliminates implicit trust based on network topology or user location.

Key Concept

Zero Trust Explicit Verification Tenet
Question 117Question

A financial organization is incorporating a legacy mainframe transaction processing engine into its modern hybrid data center architecture. The legacy system cannot support modern endpoint detection software or host-based firewalls, but it must securely accept transactions from front-end web servers while strictly preventing unauthorized lateral movement to adjacent enterprise database subnets. Which network architecture decision best isolates the legacy system while managing East-West traffic risks?

Show answer & explanation

Answer: Implement microsegmentation using software-defined networking rules and application proxy gateways between network zones.

Answer

Enforcing microsegmentation using software-defined networking and application proxy gateways provides granular, preventive East-West traffic control around legacy systems without requiring host-level agents.
Microsegmentation partitions the data center into isolated logical zones down to individual workload levels. Combined with proxy gateways, it enforces strict Zero Trust policy controls over lateral (East-West) traffic without needing agent software installed on the legacy endpoint.

Step-by-Step Solution

1
Analyze the operational constraints and threat model for the legacy mainframe system.
Determine that host-based firewalls cannot be installed and that the main risk vector is lateral (East-West) movement from compromised internal web or database servers.
Legacy devices without modern host controls must be shielded at the network layer.
2
Evaluate segmentation strategies capable of restricting East-West traffic while permitting legitimate API requests.
Identify microsegmentation with proxy gateways as the optimal mechanism to create isolated security boundaries around specific workloads.
Microsegmentation enforces explicit allow rules between defined network workloads regardless of physical network topology.
3
Reject ineffective or overly restrictive isolation options.
Eliminate perimeter-only defense (lacks internal lateral prevention), passive NIDS (detective, not preventive), and physical air-gapping (disrupts necessary real-time connectivity).
Secure network design must balance required operational functionality with preventive security controls.

Key Concept

Microsegmentation and East-West Traffic Isolation
Question 118Question

A Chief Information Security Officer (CISO) is auditing enterprise cloud services to enforce compliance with the cloud shared responsibility model across diverse architectures. Match each cloud service model implementation on the left to the corresponding primary security responsibility retained by the cloud customer on the right.

Click a left item, then click its matching right item

Items

Infrastructure as a Service (IaaS) virtual server cluster
Platform as a Service (PaaS) managed relational database
Function as a Service (FaaS) event-driven microservice
Software as a Service (SaaS) cloud collaboration suite

Matches

Show answer & explanation

Answer

Each cloud service model maps to a specific tier in the shared responsibility matrix based on the level of abstraction provided by the vendor. IaaS requires customer management of OS and networking firewall controls; PaaS requires customer management of data objects and access rights while delegating OS/engine patching to the vendor; FaaS leaves application code and identity execution context to the customer; SaaS limits customer control strictly to data governance, access controls, and policy configurations.
The mapping accurately reflects how responsibility shifts from customer-heavy in IaaS (OS, middleware, network controls) to provider-heavy in SaaS (entire application stack), with PaaS and FaaS delegating runtime and platform maintenance to the cloud provider while keeping data, code, and access governance under customer control.

Step-by-Step Solution

1
Analyze the IaaS virtual server cluster requirements.
IaaS provides bare compute infrastructure and virtualized host space, leaving OS patching, guest firewalls, and application management to the customer.
The provider only controls physical infrastructure and the hypervisor layer in IaaS.
2
Analyze the PaaS managed relational database requirements.
PaaS abstracts the underlying operating system and software engine, leaving database object access control and schema management to the customer.
The provider patches the host OS and DB engine, but cannot manage customer data access or application-level queries.
3
Analyze the FaaS event-driven microservice requirements.
FaaS abstracts both OS and runtime environments, requiring the customer to focus on secure function code and IAM execution roles.
Serverless architectures push infrastructure provisioning to the provider while keeping code and execution policy on the customer side.
4
Analyze the SaaS cloud collaboration suite requirements.
SaaS abstracts the entire hardware and software stack, leaving identity access, tenant settings, and data classification to the customer.
The vendor maintains all software and underlying platforms in SaaS deployments.

Key Concept

Cloud Shared Responsibility Matrix across IaaS, PaaS, FaaS, and SaaS
Question 119Question

An enterprise security administrator needs to isolate public-facing web servers from the internal corporate network to ensure that external internet traffic cannot directly reach internal database servers. Which network design boundary should the administrator implement to host these public services?

Show answer & explanation

Answer: Demilitarized zone (DMZ)

Answer

Demilitarized zone (DMZ)
A demilitarized zone (DMZ) is a specialized physical or logical subnetwork that exposes an organization's external-facing services to an untrusted network, such as the internet, while keeping the rest of the enterprise network isolated. If a server in the DMZ is compromised, the internal firewall controls limit the attacker's ability to pivot into the internal network.

Step-by-Step Solution

1
Identify the architectural requirement
Public-facing services (web servers) need to be accessible from the internet while preventing direct access to sensitive internal resources.
Security best practices dictate separating publicly reachable assets from internal private assets.
2
Evaluate network segmentation options
A demilitarized zone (DMZ) creates a perimeter subnet placed between the untrusted external network (internet) and the trusted internal network.
Firewall rules control North-South traffic into the DMZ and strictly restrict East-West traffic from the DMZ into the internal network.

Key Concept

Demilitarized Zone (DMZ) Perimeter Design
Estimated Time:45s
Question 120Question

An enterprise security architect is designing a defense-in-depth framework across a multi-cloud environment. Match each cloud security technology on the left with its primary operational function on the right.

Click a left item, then click its matching right item

Items

Cloud Access Security Broker (CASB)
Cloud Security Posture Management (CSPM)
Cloud Workload Protection Platform (CWPP)
Secure Access Service Edge (SASE)

Matches

Show answer & explanation

Answer

Cloud Access Security Broker (CASB) matches with policy and DLP enforcement between users and cloud applications; Cloud Security Posture Management (CSPM) matches with continuous audit of cloud resource configurations and compliance drift; Cloud Workload Protection Platform (CWPP) matches with runtime threat detection and vulnerability management for workloads (VMs, containers); Secure Access Service Edge (SASE) matches with the convergence of SD-WAN networking and cloud-delivered security controls.
Each cloud security solution targets a distinct architectural operational boundary: CASB protects application-level usage and data flows; CSPM monitors infrastructure control plane compliance and configuration hygiene; CWPP secures individual compute workload runtimes; and SASE converges network transport infrastructure with edge-delivered security controls.

Step-by-Step Solution

1
Identify the primary scope of Cloud Access Security Broker (CASB).
CASB secures user interaction with cloud applications (SaaS/PaaS) by enforcing governance, authentication, and Data Loss Prevention (DLP).
CASB acts as an intermediary policy enforcement point between endpoints and cloud service providers.
2
Identify the primary scope of Cloud Security Posture Management (CSPM).
CSPM audits cloud management planes for misconfigurations and regulatory compliance drift.
CSPM continuously inspects environment settings against baseline security standards.
3
Identify the primary scope of Cloud Workload Protection Platform (CWPP).
CWPP secures compute resources (VMs, containers, serverless instances) at runtime.
CWPP provides workload-centric security features such as process monitoring and container image scanning.
4
Identify the primary scope of Secure Access Service Edge (SASE).
SASE combines wide-area network routing (SD-WAN) with cloud-delivered security services like ZTNA and SWG.
SASE integrates network routing with cloud-native security enforcement at the edge.

Key Concept

Cloud Security Architecture and Monitoring Solutions
PreviousPage 6 / 21Next
Security Architecture Practice Questions — CompTIA Security+ — Page 6 | Examkin