Security Architecture

405 questions

Question 81Question

An organization is deploying a custom web application to a cloud environment where the cloud service provider manages the underlying hardware, operating system, and web server runtime environment. The organization's development team is responsible only for deploying their application code and managing the application data. Which cloud service model is being utilized in this scenario?

Show answer & explanation

Answer: Platform as a Service (PaaS)

Answer

Platform as a Service (PaaS)
Platform as a Service (PaaS) abstracts the underlying infrastructure and operating system layer. The cloud provider maintains hardware, operating systems, and runtime environments, while the customer retains control over application code and data management.

Step-by-Step Solution

1
Analyze the management boundary described in the scenario.
The cloud provider handles physical hardware, OS, and runtime middleware, while the organization handles application code and data.
Determining where customer responsibility starts is key to identifying the service model under the Shared Responsibility Model.
2
Map the boundary to standard cloud service models.
Managing code and data on top of a provider-managed runtime environment defines Platform as a Service (PaaS).
PaaS abstracts the underlying operating system and hardware so developers can focus solely on application code.

Key Concept

Cloud Service Models and Shared Responsibility
Question 82Question

An enterprise organization is migrating its core billing application to a public cloud using an Infrastructure as a Service (IaaS) deployment model. Which of the following security tasks remain the direct responsibility of the enterprise customer within this framework? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Hardening guest operating systems and configuring host-level firewalls; Configuring identity access controls and defining resource authorization policies

Answer

The customer is responsible for hardening guest operating systems and host-level firewalls, as well as configuring identity access controls and resource authorization policies.
Under the cloud shared responsibility model for Infrastructure as a Service (IaaS), the cloud provider manages the physical datacenters, server hardware, and virtualization hypervisors. The customer retains full ownership and operational responsibility for guest operating systems, software patching, host-based security controls, and user access authorization.

Step-by-Step Solution

1
Analyze the specified cloud deployment model
Identified Infrastructure as a Service (IaaS) as the service model in scope.
Under IaaS, the Cloud Service Provider (CSP) manages physical facilities, hardware host infrastructure, and hypervisor software, while the customer manages virtual machines, operating systems, applications, and data.
2
Evaluate operating system and network responsibilities
Selected guest operating system hardening and host firewall management as customer duties.
Because the customer provisions and maintains the virtual machine environment in IaaS, OS patching and local firewall configuration rest entirely on the customer.
3
Evaluate identity and data control responsibilities
Selected identity access management and resource authorization policy configuration as customer duties.
User access management, data classification, and authorization rules remain customer responsibilities across all cloud models (IaaS, PaaS, SaaS).

Key Concept

Cloud Shared Responsibility Model (IaaS)
Question 83Question

A technology firm has deployed several virtual machines on an Infrastructure as a Service (IaaS) public cloud platform. According to the cloud shared responsibility model, which of the following security tasks is the sole responsibility of the customer?

Show answer & explanation

Answer: Configuring and applying patches to the guest operating system

Answer

Configuring and applying patches to the guest operating system
Under the cloud shared responsibility model for Infrastructure as a Service (IaaS), the cloud service provider maintains the physical facilities, hardware, and hypervisor layer. The customer assumes full responsibility for configuring, managing, and patching the guest operating systems running within their virtual instances, along with securing installed applications and customer data.

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.
Different service models (IaaS, PaaS, SaaS) dictate distinct boundaries for shared responsibility between the customer and provider.
2
Apply the shared responsibility model rules for IaaS
The Cloud Service Provider (CSP) manages the physical security, underlying host hardware, facilities, and hypervisor. The customer manages the guest operating system, network configuration, applications, and data.
IaaS provides raw compute resources, placing operating system administration squarely on the customer.
3
Evaluate the options against the customer responsibility domain
Guest operating system configuration and patching is managed by the customer, whereas physical access, hypervisors, and storage hardware are managed by the CSP.
Selecting the task that resides on the customer side of the responsibility boundary satisfies the question.

Key Concept

Shared Responsibility Model in IaaS
Question 84Question

An enterprise security architect is mapping security governance duties across various cloud service models during a multi-cloud initiative. Match each cloud service model on the left with the customer's primary security responsibility on the right.

Click a left item, then click its matching right item

Items

Infrastructure as a Service (IaaS)
Platform as a Service (PaaS)
Software as a Service (SaaS)
Function as a Service (FaaS)

Matches

Show answer & explanation

Answer

Infrastructure as a Service (IaaS) matches with configuring guest operating system security patches, virtual machine firewalls, and installed middleware applications. Platform as a Service (PaaS) matches with managing application code and database schemas while relying on the provider to maintain the operating system and runtime framework. Software as a Service (SaaS) matches with configuring user identity access permissions and monitoring data access policies while the provider maintains all application code, runtime, and infrastructure. Function as a Service (FaaS) matches with managing event trigger permissions and stateless code execution logic while the provider completely abstracts infrastructure host provisioning and scaling.
Each cloud service model defines a distinct boundary of ownership under the shared responsibility framework. In Infrastructure as a Service (IaaS), customer responsibility extends from the guest OS upward (including OS patching and virtual network security). Platform as a Service (PaaS) shifts OS and runtime maintenance to the provider, leaving code and database management to the customer. Software as a Service (SaaS) shifts application code management to the provider, leaving identity governance and data access to the customer. Function as a Service (FaaS) abstracts server infrastructure entirely, limiting customer responsibility to discrete event-driven function code.

Step-by-Step Solution

1
Analyze the scope of customer control in Infrastructure as a Service (IaaS).
Identify that IaaS grants full control down to the operating system level, making OS patch management and virtual firewalls customer duties.
Under the cloud shared responsibility model for IaaS, virtualization hardware is provider-managed, but guest OS and compute configurations belong to the customer.
2
Analyze Platform as a Service (PaaS) boundaries.
Determine that PaaS abstracts OS and runtime management, limiting customer duties to code development and database management.
PaaS providers manage the framework and environment to streamline application development for enterprise developers.
3
Evaluate Software as a Service (SaaS) responsibility scope.
Recognize that SaaS offloads all application maintenance to the vendor, restricting customer duties to identity, access, and data security.
SaaS solutions deliver fully formed applications where customers only govern data and access permissions.
4
Determine Function as a Service (FaaS) responsibility.
Confirm that serverless execution removes host management completely, focusing customer effort strictly on short-lived function logic and execution triggers.
FaaS dynamic execution models isolate customer responsibility to individual units of deployed logic and authorization policies.

Key Concept

Cloud Shared Responsibility Model across Service Delivery Architecture Types
Question 85Question

An e-commerce organization is transitioning its customer portal microservices from self-managed virtual machines running in an Infrastructure as a Service (IaaS) environment to a managed Platform as a Service (PaaS) application hosting engine. Which of the following security management tasks is transferred from the organization to the cloud service provider as a direct result of adopting this PaaS model?

Show answer & explanation

Answer: Applying security updates and security patches to the underlying operating system of the application hosting environment.

Answer

Applying security updates and security patches to the underlying operating system of the application hosting environment.
In the Cloud Shared Responsibility Model for Platform as a Service (PaaS), the Cloud Service Provider (CSP) assumes full management of the hardware, hypervisor, operating system (OS), and middleware runtime. Moving from IaaS to PaaS transfers the burden of OS security patching and kernel updates from the customer to the provider.

Step-by-Step Solution

1
Analyze the scope of responsibility in Infrastructure as a Service (IaaS).
In IaaS, the customer manages the guest operating system, runtime software, network configurations, application code, and data.
IaaS provides raw virtualized compute infrastructure where the OS layer is customer-maintained.
2
Analyze the shift in scope when migrating to Platform as a Service (PaaS).
In PaaS, the Cloud Service Provider (CSP) manages the hardware, hypervisor, operating system, and execution runtime environment.
PaaS abstracts the underlying operating system and hardware platform so developers can focus solely on application code and data.
3
Identify the task transferred from the customer to the CSP.
Operating system patching and runtime engine maintenance are transferred to the CSP in PaaS.
Because the customer no longer manages or accesses the underlying OS in PaaS, OS update enforcement becomes a provider duty.

Key Concept

Cloud Shared Responsibility Model (IaaS vs. PaaS)
Question 86Question

A healthcare provider maintains an on-premises data center for storing confidential patient health records to maintain direct physical oversight. To handle peak computing demands during annual health audits, the provider integrates resources from a public cloud vendor. Which cloud deployment model is the organization utilizing?

Show answer & explanation

Answer: Hybrid cloud

Answer

Hybrid cloud
A hybrid cloud deployment model bridges private on-premises infrastructure with public cloud resources, allowing organizations to store sensitive data locally while bursting workloads to the cloud during high-demand periods.

Step-by-Step Solution

1
Identify the environments present in the scenario.
The healthcare provider relies on an internal on-premises data center alongside external public cloud resources.
Determining all hosting environments in use is essential for identifying the overall deployment model.
2
Map the combined environment structure to standard cloud deployment definitions.
An architecture connecting private local infrastructure with public cloud services to support workload bursting is defined as a hybrid cloud.
Hybrid cloud architectures allow organizations to maintain strict control over sensitive data locally while dynamically leveraging public cloud elasticity.

Key Concept

Cloud Deployment Models
Estimated Time:45s
Question 87Question

A financial institution is deploying a microservice platform using a Function-as-a-Service (FaaS) cloud model to process high-frequency transaction requests. During a security architecture review, the compliance team requires a clear matrix of operational duties between the organization and the cloud service provider (CSP). Which of the following responsibilities is retained solely by the enterprise customer under this deployment model?

Show answer & explanation

Answer: Configuring application-level access control logic and authorization rules within the function code

Answer

Configuring application-level access control logic and authorization rules within the function code is retained solely by the enterprise customer.
Under the cloud shared responsibility model for Function-as-a-Service (FaaS), the cloud service provider abstracts and manages the underlying hardware, hypervisor, host operating system, and language runtime environment. The enterprise customer retains complete responsibility for writing secure code, managing user data, defining data access policies, and embedding application-level authorization controls within the deployed function code.

Step-by-Step Solution

1
Analyze the cloud service model specified in the scenario
Identified the platform model as Function-as-a-Service (FaaS) / Serverless compute
Service responsibility boundaries vary significantly depending on whether IaaS, PaaS, SaaS, or FaaS is used
2
Evaluate CSP versus customer responsibility for FaaS deployments
The CSP manages physical hardware, hypervisors, server OS, container runtimes, and auto-scaling logic
FaaS abstracts server and runtime management away from the customer
3
Identify the remaining customer management domain
The customer remains responsible for code development, API authorization logic, data classification, and IAM permissions
The customer owns all custom application logic and security configuration within their functions

Key Concept

Cloud Shared Responsibility Model in Serverless / FaaS Architectures
Question 88Question

An enterprise security architect is establishing a security baseline across diverse cloud deployment and service models. Match each security operational task or control responsibility to the corresponding cloud service or deployment model that correctly allocates primary tenant responsibility.

Click a left item, then click its matching right item

Items

Configuring guest operating system firewall rules, virtual network routing policies, and OS-level security patches
Managing application runtime environments, database engine security updates, and middleware framework dependencies
Defining user access role permissions, data classification rules, and identity governance within fully hosted turnkey applications
Enforcing a shared infrastructure security baseline and compliance governance model across independent organizations with common regulatory mandates

Matches

Show answer & explanation

Answer

Configuring guest OS firewall rules and virtual routing maps to Infrastructure as a Service (IaaS). Managing application runtime environments and database engine updates maps to Platform as a Service (PaaS). Defining user access permissions and data classification rules in turnkey applications maps to Software as a Service (SaaS). Enforcing a shared infrastructure baseline across entities with common compliance requirements maps to Community Cloud.
The allocation of security management responsibilities follows the cloud shared responsibility framework across service models (IaaS, PaaS, SaaS) and deployment structures (Community Cloud). In IaaS, the customer manages everything from the guest OS upwards. In PaaS, the provider manages the host infrastructure and runtime environment, while the customer manages code and data. In SaaS, the provider manages the full application stack, leaving data protection and access administration to the customer. A Community Cloud specifically serves multiple organizations sharing regulatory and operational requirements.

Step-by-Step Solution

1
Analyze task 1 regarding guest OS firewalls and patching.
Identified as IaaS responsibility because the customer controls the OS layer and virtual network configuration while the CSP manages the hypervisor and physical hosts.
IaaS provides raw infrastructure primitives, leaving OS administration to the tenant.
2
Analyze task 2 regarding application runtime engines and middleware patching.
Identified as PaaS responsibility because the provider abstracts away OS and infrastructure maintenance, providing a ready-to-use execution engine for user applications.
PaaS offloads OS and engine maintenance to the CSP while keeping application code under tenant control.
3
Analyze task 3 regarding identity governance in turnkey software applications.
Identified as SaaS responsibility because the entire software product is abstracted, leaving only data security and user access management to the tenant.
SaaS providers deliver complete applications, shifting all infrastructure and application maintenance away from the tenant.
4
Analyze task 4 regarding joint infrastructure baseline enforcement across distinct organizations with shared compliance needs.
Identified as Community Cloud because this deployment model specifically pools infrastructure resources for member organizations operating under a shared security or regulatory umbrella.
Community clouds cater to multi-tenant peer cohorts with unified governance criteria.

Key Concept

Shared Responsibility Model across Cloud Service and Deployment Models
Question 89Question

A network administrator needs to isolate legacy industrial control devices that cannot accept software patches from the primary corporate network to prevent unauthorized lateral movement. Which of the following network design techniques best fulfills this security requirement?

Show answer & explanation

Answer: Placing the legacy devices into a dedicated isolated VLAN with strict firewall access control lists restricting inter-zone communication

Answer

Placing the legacy devices into a dedicated isolated VLAN with strict firewall access control lists restricting inter-zone communication
Placing legacy devices into a dedicated, isolated VLAN enforced by firewall rules restricts network traffic to only authorized communication paths, preventing lateral threat movement across the internal network.

Step-by-Step Solution

1
Identify the primary risk described in the scenario
Unpatchable legacy devices on a network create a risk of lateral movement if compromised.
Legacy devices often lack modern security controls and vendor patch support.
2
Determine the appropriate network architecture control
Network segmentation via VLANs and firewall ACLs isolates high-risk assets into specific zones.
Segmentation restricts network traffic flow, preventing unauthorized internal access to and from sensitive or vulnerable systems.

Key Concept

Network Segmentation and Isolation
Estimated Time:45s
Question 90Question

A global manufacturing corporation is deploying a multi-cloud security architecture to support collaborative supply chain partner integration, internal software engineering teams, and cloud governance monitoring. Match each cloud architecture model or security control placement on the left with its corresponding responsibility boundary or functional description on the right.

Click a left item, then click its matching right item

Items

Community Cloud Deployment Model
Cloud Access Security Broker (CASB) API Integration
Infrastructure as a Service (IaaS) Compute Layer
Platform as a Service (PaaS) Application Layer

Matches

Show answer & explanation

Answer

The Community Cloud Deployment Model matches shared infrastructure operated for member organizations with common compliance goals. The Cloud Access Security Broker API Integration matches out-of-band inspection using native provider interfaces without proxy latency. The Infrastructure as a Service Compute Layer matches the boundary where the customer handles guest OS patching and virtual firewalls while the provider manages physical hardware and hypervisor. The Platform as a Service Application Layer matches the boundary where the provider manages the OS and runtime frameworks while the customer manages application code and access control.
Each cloud architectural concept correctly aligns with its defined operational scope under enterprise cloud governance standards. Community clouds address multi-tenant shared mission domains; API-based CASBs provide non-disruptive out-of-band auditing; IaaS demands guest OS management by the customer; and PaaS abstracts OS/runtime management to the CSP while retaining application and data security on the customer side.

Step-by-Step Solution

1
Identify the deployment model characteristics for joint organization platforms.
Community cloud models serve pooled organizations with shared compliance or operational goals, dividing responsibilities among participants.
Differentiates community cloud from public or private deployment models.
2
Analyze CASB integration modes (inline proxy vs. out-of-band API).
API mode connects via provider administrative endpoints asynchronously, avoiding network latency.
Distinguishes API integration from forward/reverse inline proxy configurations.
3
Differentiate shared responsibility boundaries between IaaS and PaaS models.
IaaS obligates the customer to manage guest OS patching and middleware; PaaS shifts OS and runtime maintenance to the cloud service provider.
Establishes accurate security responsibility assignment across cloud service layers.

Key Concept

Cloud Shared Responsibility Model and Security Architecture Integration Modes
Question 91Question

Match each cloud deployment model to its defining security architecture characteristic.

Click a left item, then click its matching right item

Items

Public Cloud
Private Cloud
Hybrid Cloud
Community Cloud

Matches

Show answer & explanation

Answer

Public Cloud matches multi-tenant third-party infrastructure. Private Cloud matches single-tenant dedicated infrastructure. Hybrid Cloud matches integrated private and public cloud infrastructure. Community Cloud matches shared infrastructure for organizations with common compliance goals.
Each deployment model is defined by its tenant isolation structure and user community: Public Cloud utilizes multi-tenant vendor infrastructure, Private Cloud provides dedicated single-tenant resources, Hybrid Cloud bridges private and public environments, and Community Cloud is shared among specific organizations with common compliance objectives.

Step-by-Step Solution

1
Identify the multi-tenant deployment model hosted by third parties.
Public Cloud is hosted by third parties for external subscribers in a shared multi-tenant environment.
Public cloud resources are pooled by vendors and delivered over public networks to diverse customers.
2
Identify the dedicated single-tenant deployment model.
Private Cloud provides single-tenant isolation dedicated solely to one organization.
Organizations with strict regulatory needs use private clouds to maintain complete control over data storage and governance.
3
Identify the combined environment connecting distinct infrastructure types.
Hybrid Cloud connects on-premises or private infrastructure with public cloud resources.
Hybrid deployment allows organizations to maintain sensitive internal workloads while leveraging cloud elasticity.
4
Identify the model shared among specific organizations with shared industry or compliance requirements.
Community Cloud serves organizations with common regulatory mandates or goals.
Community cloud distributes pool costs and management across a restricted group of aligned entities.

Key Concept

Cloud Deployment Models
Estimated Time:1m 0s
Question 92Question

An organization plans to deploy a database solution in the cloud. The company requires the Cloud Service Provider (CSP) to manage hardware provisioning, operating system installation, and database engine maintenance, while the internal IT team retains control over database tables and user permissions. Which cloud service model should the organization select to meet these requirements?

Show answer & explanation

Answer: Platform as a Service (PaaS)

Answer

Platform as a Service (PaaS)
Platform as a Service (PaaS) abstracts away physical infrastructure, OS deployment, and software runtime patching, enabling the cloud provider to manage the platform environment while allowing the customer to maintain full ownership over data structures, schemas, and identity permissions.

Step-by-Step Solution

1
Analyze the management boundary described in the scenario
The Cloud Service Provider maintains the hardware, operating system, and database software binaries.
Determining which tier of the stack is vendor-managed establishes the service model tier.
2
Identify customer responsibilities
The customer manages data schemas, database contents, and access permissions.
Customer responsibility limited to application data and configuration aligns directly with PaaS.

Key Concept

Cloud Service Models and Shared Responsibility Boundaries
Question 93Question

A security architect is developing a cloud security matrix to clarify operational responsibilities across multi-cloud environments. Match each security operational task to the corresponding cloud service model where the customer is primarily responsible for performing that specific task.

Click a left item, then click its matching right item

Items

Applying security patches to the guest operating system and configuring host network firewalls
Configuring user role permissions and single sign-on (SSO) integration within a fully vendor-managed application
Hardening source code and managing database schemas while the vendor maintains the execution runtime and middleware
Securing custom function trigger logic and API endpoints while the provider manages event orchestration and container execution

Matches

Show answer & explanation

Answer

Guest OS patching and firewalling matches Infrastructure as a Service (IaaS); configuring user role permissions matches Software as a Service (SaaS); source code and schema security matches Platform as a Service (PaaS); securing function logic and API endpoints matches Function as a Service (FaaS / Serverless).
Each service model transfers specific operational responsibilities to the cloud provider. In IaaS, the customer retains control down to the guest OS level. In PaaS, the provider handles the OS and runtime, leaving application code to the customer. In SaaS, the provider manages the entire application stack, leaving access control to the customer. In FaaS, short-lived function code and trigger handling are the customer's focus.

Step-by-Step Solution

1
Analyze the IaaS responsibility boundary
Identify tasks that involve managing operating system kernels, host security policies, and virtual networking.
IaaS provides raw compute resources, making OS maintenance and host firewalling a customer responsibility.
2
Analyze the SaaS responsibility boundary
Identify tasks limited strictly to identity access management and application configuration.
SaaS abstracts all infrastructure and software delivery, leaving customer responsibility focused on data governance and access control.
3
Analyze the PaaS responsibility boundary
Identify tasks managing custom code and application data while relying on provider-managed runtimes.
PaaS relieves the customer of operating system patching while keeping application logic and data within the customer's domain.
4
Analyze the FaaS responsibility boundary
Identify tasks focused purely on event execution logic and API triggers.
FaaS isolates customer responsibility to individual execution functions and endpoint security, abstracting all server host execution.

Key Concept

Cloud Shared Responsibility Model across Service Delivery Models
Estimated Time:1m 30s
Question 94Question

A security architect is updating the enterprise security baseline for several subnets and workload environments. Match each network design requirement to the most appropriate architecture technique or isolation mechanism.

Click a left item, then click its matching right item

Items

Completely detaching sensitive legacy industrial control devices from all physical and wireless network connectivity
Restricting lateral East-West traffic flow between virtual machine workloads operating on the same hypervisor host
Placing publicly accessible web application servers in a network boundary separated from internal database servers
Establishing a single, heavily monitored host through which system administrators must authenticate to access remote secure zones

Matches

Show answer & explanation

Answer

Complete network detachment corresponds to Air-gapping; Restricting lateral virtual machine traffic corresponds to Microsegmentation; Separating public web servers from core databases corresponds to Demilitarized Zone (DMZ); Enforcing a single monitored administrative gateway corresponds to Jump box / Bastion host.
Air-gapping ensures absolute isolation from external networks; microsegmentation applies workload-level traffic filtering to limit lateral movement within subnets; a DMZ segregates public-facing resources from internal networks; and a jump box serves as a secured gateway for privileged administrative sessions.

Step-by-Step Solution

1
Evaluate requirement 1 (legacy device isolation without connectivity)
Identified absolute physical/logical separation requirement
Disconnecting systems entirely from networks defines an air gap topology.
2
Evaluate requirement 2 (lateral East-West traffic control between workloads on the same host)
Identified fine-grained workload-level policy enforcement
Controlling communication between individual container/VM workloads on shared subnets is achieved using microsegmentation.
3
Evaluate requirement 3 (isolating internet-exposed services from private networks)
Identified perimeter network isolation pattern
Exposing services to external traffic while keeping internal networks protected behind firewall interfaces defines a DMZ.
4
Evaluate requirement 4 (centralized administrative management entry point)
Identified single-purpose proxy server requirement
Requiring admins to connect through a single secure proxy before reaching target systems describes a jump box.

Key Concept

Network Segmentation Archetypes and Traffic Isolation Controls
Question 95Question

A security architect is designing a multi-tier web application network layout for a corporate enterprise. The design requires that public Internet users can access the front-end web servers, but direct connectivity from the Internet to the backend database servers holding sensitive payment data must be strictly prohibited. Furthermore, administrative access to the database tier must be tightly restricted and audited, with lateral East-West movement between unauthorized server segments blocked. Which of the following network architecture designs best achieves this security objective?

Show answer & explanation

Answer: Place web servers in a perimeter screened subnet (DMZ) and isolate database servers in a restricted internal network segment, enforcing access control lists and requiring administrative transit through a dedicated jump server.

Answer

Placing public-facing web servers in a screened subnet (DMZ), placing backend databases in isolated internal network segments, and restricting management access via jump boxes best protects sensitive assets from direct external access and lateral threat movement.
Placing public-facing services in a screened subnet (DMZ) isolates external exposure. Combining this with internal subnetting/VLAN isolation for database tiers and restricting administrative access to a jump server enforces effective defense-in-depth and controls lateral movement.

Step-by-Step Solution

1
Identify perimeter isolation requirements for public-facing assets versus sensitive data stores.
Public web servers must reside in a screened subnet (DMZ) to accept external requests while keeping the internal network protected.
Direct Internet access to database tiers creates high vulnerability exposure.
2
Evaluate lateral traffic control (East-West enforcement) and administration pathways.
Database servers require microsegmentation or restricted VLAN placement, with firewall ACLs permitting connection only from authorized web tier ports and audited jump hosts.
Strict segmentation prevents compromised front-end hosts from pivoting freely to internal database assets.

Key Concept

Network Segmentation, Screened Subnets (DMZ), and Bastion/Jump Server Architecture
Question 96Question

A network security team is establishing security zones and access control mechanisms for an enterprise environment. Match each network segmentation strategy on the left to its primary application scenario on the right.

Click a left item, then click its matching right item

Items

Air Gap
DMZ (Demilitarized Zone)
Microsegmentation
Jump Box

Matches

Show answer & explanation

Answer

Air Gap matches complete physical isolation from external networks; DMZ matches hosting internet-accessible services while buffering internal networks; Microsegmentation matches granular isolation of individual virtual workloads; Jump Box matches serving as a hardened administrative entry point.
Air gaps completely physically separate high-security networks from external connections. DMZs host public-facing services to isolate the internal network from internet threats. Microsegmentation applies granular policy controls between individual virtualized workloads. Jump boxes serve as single hardened entry points for administrative traffic accessing sensitive zones.

Step-by-Step Solution

1
Identify the function of an air gap.
Air gaps provide total physical separation.
Air gaps ensure sensitive environments have zero network connections to outside or untrusted systems.
2
Determine the role of a DMZ.
DMZs host public-facing servers separated from internal subnets.
This architecture buffers internal corporate assets from untrusted internet traffic.
3
Define microsegmentation.
Microsegmentation isolates workloads at the virtual machine or container layer.
It applies zero-trust principles to control East-West network traffic between workload instances.
4
Evaluate the function of a jump box.
A jump box acts as a hardened administrative access portal.
Administrators must first connect and authenticate to the jump box before initiating management sessions into isolated zones.

Key Concept

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

An organization is updating its cloud-native architecture for a healthcare portal processing Sensitive Personal Health Information (PHI). The security architecture team must enforce strict isolation between individual microservices to prevent lateral movement, continuously authenticate every service-to-service communication path, and inspect East-West traffic without relying solely on perimeter boundary firewalls. Which of the following network architecture strategies best satisfies these requirements?

Show answer & explanation

Answer: Implement microsegmentation using a Service Mesh architecture enforcing mutual TLS (mTLS) and dynamic identity-based network policies.

Answer

Implementing microsegmentation using a Service Mesh architecture enforcing mutual TLS (mTLS) and dynamic identity-based network policies.
Microsegmentation divides cloud environments into distinct security segments down to the individual workload level. Using a Service Mesh with mTLS ensures cryptographic identity verification and encrypted session enforcement for all East-West microservice traffic, aligning with Zero Trust secure network design principles.

Step-by-Step Solution

1
Analyze the architectural requirements
Identified the need for granular service-to-service isolation (East-West control), continuous identity verification, and prevention of lateral movement within cloud microservices.
Traditional perimeter firewalls cannot inspect microservice-to-microservice traffic efficiently or enforce identity-based access control.
2
Evaluate segmentation strategies for cloud-native microservices
Microsegmentation using a Service Mesh decouples security policies from network topology, enforcing cryptographic identity via mTLS and zero trust access rules at layer 7.
This guarantees granular isolation without relying on implicit perimeter trust.
3
Differentiate from incorrect legacy architecture controls
Eliminated broad VLAN perimeter placement, air-gapping operational microservices, and passive detective sensors.
Perimeter reliance allows unchecked lateral movement, air gaps break cloud microservice functionality, and passive NIPS cannot actively block inline traffic.

Key Concept

Microsegmentation and Zero Trust Architecture in Network Design
Estimated Time:2m 0s
Question 98Question

A enterprise security architecture team is revising its infrastructure segmentation strategy to address specific threat models across varied operational zones. Match each network design architectural technique to the security requirement it fulfills.

Click a left item, then click its matching right item

Items

Out-of-band (OOB) management network with a bastion host
Software-defined microsegmentation
Screened subnet (DMZ) with multi-homed firewalls
Physical air-gapping

Matches

Show answer & explanation

Answer

Out-of-band management with a bastion host pairs with administrative switch isolation; Software-defined microsegmentation pairs with restricting East-West lateral workload traffic; Screened subnets with multi-homed firewalls pair with terminating untrusted Internet traffic away from internal databases; Physical air-gapping pairs with preventing remote intrusion into sensitive SCADA systems.
Each architectural pattern matches its specific security objective: Out-of-band management secures network infrastructure access; Microsegmentation halts intra-subnet lateral movement; DMZs secure public endpoints while safeguarding backend assets; Air gaps eliminate remote connectivity risks for critical isolated systems.

Step-by-Step Solution

1
Analyze management plane isolation requirements.
Identified that out-of-band management with jump boxes isolates administrative control interfaces from general user LANs.
Prevents credential sniffing and unauthorized switch access over standard corporate subnets.
2
Evaluate intra-subnet lateral movement controls.
Matched microsegmentation with limiting East-West traffic between individual workloads in shared virtual subnets.
Standard network VLANs allow unrestrained communication within a broadcast domain, whereas microsegmentation enforces workload-to-workload policies.
3
Examine perimeter and backend database protection mechanisms.
Linked screened subnets (DMZs) to untrusted Internet termination and backend database isolation.
Screened subnets proxy or inspect external requests before allowing controlled connections to internal tiers.
4
Determine total physical isolation needs for sensitive operational technology.
Matched physical air-gapping to critical legacy SCADA systems.
Air-gapping ensures complete network disconnection when software patches or logical controls are insufficient.

Key Concept

Secure Network Design and Segmentation Archetypes
Question 99Question

An organization is transitioning from a traditional perimeter-based security model to a Zero Trust Architecture (ZTA). Which of the following fundamental principles must the organization implement as part of this new architectural framework? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Assume all network traffic is untrusted, even if originating within the internal network.; Perform explicit verification for every access request using dynamic identity, context, and policy evaluation.

Answer

The correct principles are assuming all network traffic is untrusted regardless of origin and explicitly verifying every access request using dynamic context and policy evaluation.
Zero Trust Architecture replaces legacy boundary-based trust with two foundational tenets: assuming that network traffic is inherently untrusted regardless of source location ('assume breach'), and enforcing explicit verification on every access request using identity, context, and policy evaluation.

Step-by-Step Solution

1
Identify the foundational trust model of Zero Trust Architecture.
Zero Trust operates under an 'assume breach' philosophy.
Internal network traffic can no longer be assumed secure simply because it originates behind a perimeter firewall.
2
Determine the required access evaluation process.
Every request must undergo explicit verification before access is granted.
Verification must continuously consider user identity, device security posture, and request context.

Key Concept

Zero Trust Core Tenets: Assume Breach and Explicit Verification
Question 100Question

An enterprise security team is implementing a Platform as a Service (PaaS) managed container environment to host web microservices. Under the shared responsibility model, the Cloud Service Provider (CSP) maintains the underlying hardware, hypervisors, and orchestrator control plane. Which of the following operational tasks remains the primary responsibility of the enterprise security team?

Show answer & explanation

Answer: Configuring application-level access controls and remediating vulnerabilities in custom container image code.

Answer

Configuring application-level access controls and remediating vulnerabilities in custom container image code is the primary responsibility of the customer enterprise.
Under the cloud shared responsibility model for Platform as a Service (PaaS), the cloud service provider manages the physical infrastructure, network layer, hypervisor, and container orchestrator engine. The customer remains responsible for application code security, data classification, and access control configuration.

Step-by-Step Solution

1
Analyze the cloud service model specified in the scenario.
The scenario describes a Platform as a Service (PaaS) environment where container orchestration and physical infrastructure are managed by the Cloud Service Provider.
Understanding the service model boundaries determines the baseline division of duties under the shared responsibility model.
2
Differentiate between provider-managed responsibilities and customer-managed responsibilities for PaaS.
The CSP manages physical facility security, hypervisor updates, host OS patching, and control plane orchestration. The customer manages application code, runtime configurations, identity governance, and customer data security.
PaaS offloads hardware and system administration tasks to the CSP while leaving application security with the tenant.
3
Select the option representing customer-side responsibilities.
Application access controls and container image code security belong to the customer domain.
Customers retain ownership and accountability for data, identity governance, and custom application code regardless of cloud service model.

Key Concept

Cloud Shared Responsibility Model in PaaS Environments
Estimated Time:1m 30s
PreviousPage 5 / 21Next
Security Architecture Practice Questions — CompTIA Security+ — Page 5 | Examkin