Security Architecture

405 questions

Question 41Question

An enterprise security architect is designing an Identity and Access Management (IAM) architecture to support modern cloud applications, API access, network administration, and automated user lifecycle management. Match each IAM protocol or specification on the left to its corresponding architectural use case on the right.

Click a left item, then click its matching right item

Items

SAML 2.0
OAuth 2.0
OpenID Connect (OIDC)
TACACS+
SCIM

Matches

Show answer & explanation

Answer

SAML 2.0 matches XML-based federation assertion exchange between IdP and SP; OAuth 2.0 matches API authorization and access token delegation; OpenID Connect (OIDC) matches user identity authentication layer over OAuth using JWT ID tokens; TACACS+ matches full-payload encrypted network AAA separating authN and authZ; SCIM matches automated identity provisioning/deprovisioning REST standard.
Each IAM technology fulfills a distinct architectural role within enterprise security. SAML 2.0 facilitates XML assertion-based web browser federation SSO across organizations. OAuth 2.0 governs delegated access authorization to protected resources via tokens. OpenID Connect operates on top of OAuth 2.0 to add authentication capability using JWT ID tokens. TACACS+ provides secure administrative AAA for network appliances with full payload encryption and command-level authorization decoupling. SCIM provides standard REST endpoints to automate identity provisioning and account lifecycle operations across enterprise and cloud services.

Step-by-Step Solution

1
Analyze SAML 2.0 functionality.
Identified SAML 2.0 as an XML-based federated SSO standard that passes security assertions between Identity Providers and Service Providers.
SAML relies on XML payload assertions across cross-domain boundaries.
2
Analyze OAuth 2.0 functionality.
Identified OAuth 2.0 as an authorization framework that delegates scoped API access tokens to applications.
OAuth 2.0 provides delegated authorization rather than direct authentication.
3
Analyze OpenID Connect (OIDC) functionality.
Identified OIDC as an authentication extension on top of OAuth 2.0 utilizing JSON Web Tokens (JWTs).
OIDC fills the authentication gap in OAuth 2.0 by introducing standardized ID tokens.
4
Analyze TACACS+ network administrative AAA properties.
Identified TACACS+ as encrypting the entire packet body and decoupling authentication from command authorization.
Unlike RADIUS, TACACS+ separates AAA functions and provides full payload encryption.
5
Analyze SCIM protocol functionality.
Identified SCIM as an open standard protocol for automating cloud identity provisioning and deprovisioning.
SCIM uses RESTful Web APIs and standardized JSON/XML schemas to manage identity lifecycle changes across disparate SaaS systems.

Key Concept

Identity and Access Management Architecture Protocols and Frameworks
Question 42Question

An enterprise security analyst is designing an isolation architecture for a multi-tenant physical host. The system will process sensitive financial transactions alongside untrusted third-party code. The security policy mandates that a vulnerability exploited in one workload must not allow memory access or host execution privileges over co-located workload instances on the same server. Which of the following isolation strategies best fulfills this requirement?

Show answer & explanation

Answer: Deploying the workloads in separate Virtual Machines managed by a Type 1 hypervisor to leverage hardware-assisted memory protection and virtualization boundaries.

Answer

Deploying the workloads in separate Virtual Machines managed by a Type 1 hypervisor to leverage hardware-assisted memory protection and virtualization boundaries.
Virtual machines (VMs) managed by a Type 1 (bare-metal) hypervisor instantiate dedicated guest virtual hardware environments. By leveraging hardware virtualization features embedded in CPU architecture, the hypervisor enforces strict hardware-level memory paging and execution abstraction, ensuring untrusted code in one guest OS cannot inspect or compromise co-located workloads.

Step-by-Step Solution

1
Evaluate the architectural isolation requirement.
The requirement demands strong hardware-enforced memory separation between co-located workloads handling untrusted code.
Software-level process separation on a shared host OS kernel does not prevent cross-workload memory access if kernel-level vulnerabilities exist.
2
Compare container-based OS isolation against hypervisor-based hardware virtualization.
Virtual Machines (VMs) present virtualized hardware abstractions to guest operating systems, whereas containers share a single host OS kernel.
Hardware-assisted CPU virtualization enforced by a Type 1 hypervisor ensures memory paging and execution states remain isolated per guest VM.
3
Identify the option offering hypervisor-level hardware isolation.
Type 1 hypervisor deployment satisfies the requirement by preventing guest-to-guest and guest-to-host memory leaks.
This strategy aligns with enterprise security principles for high-assurance multi-tenant workload isolation.

Key Concept

Hypervisor vs. Container Isolation Boundaries
Estimated Time:1m 30s
Question 43Question

An enterprise organization is designing a high-availability infrastructure for its edge network services across two geographically separate data centers. The design requires automatic traffic redirection to the healthy data center if a primary site suffers an outage, while minimizing client browser resolution caching during a failover event. Which of the following mechanisms should the security architect deploy to meet these resilience objectives? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Global Server Load Balancing (GSLB) configured with short Time-to-Live (TTL) DNS record values; Automated DNS health-check monitoring paired with dynamic failover routing policies

Answer

The correct mechanisms are Global Server Load Balancing (GSLB) configured with short Time-to-Live (TTL) DNS record values, and automated DNS health-check monitoring paired with dynamic failover routing policies.
High-availability edge architecture across multiple data centers relies on Global Server Load Balancing (GSLB) to route traffic to active facilities. Configuring short Time-to-Live (TTL) values prevents client systems and resolvers from caching obsolete IP addresses. Automated health checks work alongside GSLB to detect site outages in real time and automatically re-route incoming connections to healthy infrastructure.

Step-by-Step Solution

1
Identify the primary requirement for geographic site failover and client caching prevention.
Determined that multi-site traffic routing and DNS cache control are required.
Geographically separate data centers require site-level load distribution and rapid record expiry so clients query healthy nodes promptly.
2
Evaluate high-availability network routing controls.
GSLB with short TTLs and continuous health checks dynamically redirect traffic away from failed sites without client resolution delays.
GSLB evaluates node health dynamically and short TTLs prevent clients from retaining stale IP addresses.
3
Differentiate storage fault tolerance and detective monitoring controls from network resilience controls.
Eliminated RAID 10 drive arrays and passive IDS network taps.
RAID handles local storage drive failures, not site failover; passive IDS monitors network packets without altering or redirecting traffic paths.

Key Concept

Geographic High Availability and Global Server Load Balancing
Question 44Question

An industrial manufacturing facility needs to secure its operational technology (OT) network housing Programmable Logic Controllers (PLCs) from the corporate IT network. Unauthorized network scanning originating from corporate workstations recently reached the shop floor. The security architect must permit authorized engineering personnel to conduct remote maintenance on PLCs while preventing direct network routing between IT endpoints and OT devices. Which of the following network architecture designs best meets these security requirements?

Show answer & explanation

Answer: Deploy a jump box in a segmented DMZ requiring multifactor authentication and session recording for management traffic between IT and OT networks.

Answer

Deploying a jump box in a segmented DMZ requiring multifactor authentication and session recording for management traffic between IT and OT networks.
Deploying a jump box within a demilitarized zone (DMZ) between corporate IT and industrial control OT networks prevents direct network connectivity between endpoints. Requiring strong authentication and session logging ensures remote maintenance traffic is securely managed, authorized, and audited without exposing PLCs directly to enterprise network risks.

Step-by-Step Solution

1
Analyze the operational and security requirements
Direct IP routing between corporate IT workstations and OT PLCs must be blocked while still enabling monitored administrative access.
Protecting critical industrial control devices against unauthorized lateral movement and network scanning requires strict security zone separation.
2
Evaluate secure network boundary and transit control options
A jump box situated in a DMZ isolates the two zones by terminating incoming sessions and proxying management commands rather than allowing direct end-to-end packet transit.
Intermediary jump servers combined with MFA and session auditing enforce least-privilege access and strong zone isolation.
3
Verify the correct architectural implementation
The DMZ jump box architecture fulfills segmentation principles for OT and IT network isolation.
It prevents direct network traversal between environments while maintaining full auditability for remote administration.

Key Concept

Secure Network Design and Segmentation using DMZ and Jump Servers
Estimated Time:1m 30s
Question 45Question

A security architect is designing a cloud backup and object storage architecture to safeguard critical corporate records against unauthorized data exfiltration and ransomware tampering. The design must guarantee data confidentiality at rest while preventing stored backup snapshots from being modified or deleted even if administrative credentials are compromised. Which TWO of the following technical controls should the architect incorporate into the storage design to satisfy these requirements? (Select TWO).

Select all that apply

Show answer & explanation

Answer: Enforce AES-256 symmetric encryption managed through a dedicated key management service for bulk storage encryption.; Configure Write Once, Read Many (WORM) storage policies with object retention locks on backup buckets.

Answer

The architect should enforce AES-256 symmetric encryption managed via a key management service to ensure data confidentiality at rest, and configure Write Once, Read Many (WORM) storage policies with retention locks to ensure data immutability against deletion.
To satisfy both requirements, the organization needs a robust encryption mechanism for confidentiality at rest and an immutable storage policy for anti-deletion resilience. AES-256 symmetric encryption provides high-speed bulk storage encryption suitable for large backup volumes. Write Once, Read Many (WORM) storage policies enforce object immutability, prohibiting data overwrite or deletion even if administrative credentials are compromised.

Step-by-Step Solution

1
Identify confidentiality control requirement for bulk data at rest
AES-256 symmetric encryption delivers secure, fast bulk encryption appropriate for storage volumes and objects.
Symmetric algorithms are optimized for high-volume storage encryption performance compared to asymmetric ciphers.
2
Identify anti-tampering and anti-deletion control requirement for backup objects
Write Once, Read Many (WORM) policies combined with retention locks enforce data immutability.
WORM storage prevents any modification or destruction of written data objects even by privileged accounts during the retention period.

Key Concept

Data Protection and Storage Security Architecture
Question 46Question

A maritime shipping enterprise is formalizing its cloud security architecture strategy across diverse operational environments. Match each security operational requirement on the left with the corresponding cloud model or security architecture component on the right.

Click a left item, then click its matching right item

Items

Enforcing data loss prevention (DLP) and access controls across web applications used by corporate employees without modifying the cloud application code.
Provisioning isolated compute and storage infrastructure exclusively dedicated to single-tenant regulatory compliance data within an enterprise-controlled datacenter.
Deploying virtual instances where the enterprise retains full administrative control over operating system hardening, middleware configuration, and local firewall rules.
Participating in a joint logistics tracking platform hosted in the cloud and shared exclusively among authorized trade partners and customs authorities.

Matches

Show answer & explanation

Answer

Enforcing DLP across web applications matches Cloud Access Security Broker (CASB); Dedicated single-tenant infrastructure matches Private Cloud Deployment Model; Managing guest OS hardening and firewall rules on virtual instances matches Infrastructure as a Service (IaaS); Shared tracking platform among authorized partners matches Community Cloud Deployment Model.
Each operational requirement correctly aligns with its architectural counterpart based on the shared responsibility model and deployment boundaries: CASB handles proxy/API security enforcement for cloud applications, Private Cloud guarantees single-tenant isolation, IaaS gives the customer full OS-level management control, and Community Cloud supports shared infrastructure restricted to specified industry partners.

Step-by-Step Solution

1
Analyze the operational security requirement for intermediate policy enforcement over third-party web apps.
Identify that a Cloud Access Security Broker (CASB) provides inline or API-based enforcement of DLP and access control across cloud services.
CASB acts as an intermediary enforcing security, compliance, and governance policies.
2
Evaluate the tenancy and location requirements for single-tenant compliance data.
Map single-tenant, dedicated enterprise infrastructure to a Private Cloud model.
Private clouds guarantee isolated resources managed solely for one enterprise.
3
Examine the management responsibility boundary of guest OS hardening and middleware.
Map guest OS administration and virtual firewall control to Infrastructure as a Service (IaaS).
In IaaS, the customer retains control over the operating system and above, while the provider manages physical infrastructure.
4
Determine the cloud deployment model for infrastructure shared among bounded organizations with common goals.
Map joint industry partner platforms to a Community Cloud model.
Community clouds host joint infrastructure shared exclusively among participating entities with shared missions or compliance mandates.

Key Concept

Cloud Service and Deployment Models
Estimated Time:1m 30s
Question 47Question

A security engineer is establishing hardware hardening controls for smart grid embedded devices deployed in physically accessible remote locations. Which of the following hardware-level controls will protect device integrity and prevent unauthorized boot-level tampering? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Implementation of Secure Boot backed by a hardware Root of Trust to verify bootloader cryptographic signatures; Deployment of eFuse technology to permanently lock bootloader settings and disable sensitive hardware debug interfaces

Answer

The correct controls are implementing Secure Boot backed by a hardware Root of Trust and deploying eFuse technology to permanently lock bootloader settings and debug interfaces.
Establishing a hardware Root of Trust for Secure Boot ensures that the system checks cryptographic signatures before running any firmware or boot code. Complementing this with eFuse technology provides a permanent, hardware-enforced lockdown of configuration parameters and debugging interfaces that cannot be reverted through software.

Step-by-Step Solution

1
Analyze the hardware security requirement for embedded systems deployed in unmonitored environments.
Identified the primary requirement: preventing unauthorized firmware modification and enforcing low-level integrity.
Physical accessibility makes remote embedded devices vulnerable to unauthorized bootloader flashing and hardware-level tampering.
2
Select appropriate hardware-rooted integrity mechanisms.
Secure Boot with a Root of Trust verifies firmware signatures at initialization, while eFuses permanently enforce immutable configuration state.
Both mechanisms provide low-level, hardware-backed integrity guarantees against unauthorized code execution.

Key Concept

Hardware-rooted security mechanisms, such as Secure Boot with a Root of Trust and eFuse lockdown, protect device integrity by ensuring only authenticated firmware executes.
Question 48Question

An enterprise cloud security architect is evaluating isolation boundaries for a multi-tenant microservices platform. The platform currently runs multiple containerized services sharing a single host Linux kernel. During a risk assessment, the team identifies a risk where a kernel-level privilege escalation or vulnerability exploitation within one container could allow an attacker to escape to the host host OS and compromise adjacent tenant workloads. Which of the following deployment strategies provides the strongest architectural isolation boundary to mitigate host kernel sharing risks?

Show answer & explanation

Answer: Encapsulating container execution environments inside dedicated lightweight virtual machines (microVMs) with independent kernels

Answer

Encapsulating container execution environments inside dedicated lightweight virtual machines (microVMs) with independent kernels provides the strongest architectural isolation boundary against host kernel exploits.
Encapsulating container workloads inside dedicated lightweight virtual machines (microVMs) provides each instance with a distinct guest kernel managed by hardware-assisted virtualization. This ensures that any exploit targeting kernel vulnerabilities remains isolated within the microVM guest rather than compromising the host OS kernel shared by other tenants.

Step-by-Step Solution

1
Analyze the container threat model in shared-kernel environments
Containers traditionally share the underlying host operating system kernel via system call interfaces.
If a kernel flaw exists, any container making system calls can potentially escape to the host.
2
Evaluate hypervisor vs container isolation boundaries
Hypervisors utilize hardware virtualization extensions (e.g., VT-x/AMD-V) to isolate memory and execution spaces into virtual machines running separate guest kernels.
Lightweight virtual machines (microVMs) combine the quick startup time of containers with hypervisor-enforced kernel isolation.
3
Select the control that eliminates shared kernel vulnerability exposure
Running containers inside individual microVMs ensures that a container escape only compromises the isolated guest kernel of that microVM, not the host hypervisor or host OS.
This architectural pattern provides true defense-in-depth for multi-tenant microservices.

Key Concept

Hypervisor-assisted container isolation (microVMs) vs. kernel-sharing container isolation
Estimated Time:2m 0s
Question 49Question

A enterprise storage architect is designing a secure storage architecture for an off-site media storage facility and cloud synchronization gateway that processes large volumes of sensitive customer transactional data. The solution must ensure bulk encryption of data at rest with minimal CPU overhead, enforce hardware-isolated key protection to prevent key extraction, and prevent unauthorized exfiltration of unencrypted sensitive data across network egress interfaces. Which of the following technological controls should the architect incorporate into the architecture design to meet these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Self-Encrypting Drives (SEDs) leveraging hardware-based AES-256 transparent encryption; Hardware Security Module (HSM) deployed to manage and safeguard root keys and Key Encryption Keys (KEKs)

Answer

The enterprise storage architecture should implement Self-Encrypting Drives (SEDs) utilizing AES-256 hardware encryption alongside a dedicated Hardware Security Module (HSM) for root key protection.
Implementing Self-Encrypting Drives provides high-speed, hardware-based symmetric encryption at rest (AES-256) without host CPU penalties. Pairing SEDs with a Hardware Security Module ensures key generation and protection occur inside a hardware-isolated, tamper-evident boundary.

Step-by-Step Solution

1
Evaluate bulk data encryption requirements for storage at rest.
Self-Encrypting Drives (SEDs) handle hardware-level symmetric bulk encryption directly on the drive controller, ensuring high performance without burdening system CPUs.
Bulk storage requires fast symmetric algorithms (like AES) offloaded to specialized hardware controllers.
2
Identify key management controls for hardware isolation.
A Hardware Security Module (HSM) provides physical and logical tamper-resistant boundaries to generate, store, and manage master keys and KEKs.
HSMs ensure cryptographic keys cannot be extracted in plaintext by unauthorized users or compromised OS layers.

Key Concept

Data Protection at Rest and Storage Hardware Security Architecture
Question 50Question

A game development studio migrates its multiplayer matchmaking microservices to a managed Platform as a Service (PaaS) environment hosted by a public cloud provider. As part of defining the organization's cloud security baseline, the architecture team evaluates operational governance duties. Which of the following security responsibilities remains strictly with the game development studio under this cloud service model?

Show answer & explanation

Answer: Configuring application-level identity access management policies and user authentication controls

Answer

Configuring application-level identity access management policies and user authentication controls remains the customer's sole responsibility under Platform as a Service (PaaS).
Under the Platform as a Service (PaaS) shared responsibility model, the cloud provider assumes responsibility for host hardware, physical facility security, hypervisor management, operating system updates, and middleware engine maintenance. The cloud customer remains responsible for application code development, customer data management, and configuring application-level authentication and access control policies.

Step-by-Step Solution

1
Identify the cloud service model specified in the scenario.
The deployment uses Platform as a Service (PaaS).
Service models (IaaS, PaaS, SaaS) dictate how operational and security duties are partitioned between customer and vendor.
2
Analyze responsibility boundaries for PaaS environments.
The CSP manages physical data center security, hardware maintenance, hypervisor virtualization, operating system patching, and runtime stacks. The customer manages application logic, dataset configuration, and identity permissions.
PaaS abstracts underlying infrastructure management to allow developers to focus on software deployment and access management.
3
Determine which option represents a customer-retained security control.
Managing application-level user authentication and access control policies belongs to the customer.
Identity governance, application logic, and user access definitions remain the customer's duty regardless of the cloud service tier.

Key Concept

Cloud Shared Responsibility Model (PaaS)
Question 51Question

Match each specialized enterprise network architectural scenario with the network segmentation control or isolation mechanism that best satisfies its security and operational constraints.

Click a left item, then click its matching right item

Items

A legacy industrial control system (ICS) sensor network running end-of-life firmware must transmit batch operational logs out to an external cloud database while strictly blocking any physical or logical inbound transmission paths.
A multi-tenant containerized microservices application requires workload-to-workload identity verification and dynamically enforced intra-host software policy without relying on static IP subnets or perimeter firewall rules.
A corporate remote access environment requires external third-party auditors to access internal administrative web consoles without granting their client devices direct IP network routing into the internal corporate subnets.
A public access Wi-Fi network deployed across corporate branch offices must allow connected client endpoints to reach the default gateway while prohibiting direct Layer 2 peer-to-peer traffic between clients on the same subnet.

Matches

Show answer & explanation

Answer

The scenarios correctly match as follows: Legacy ICS telemetry requiring strictly one-way egress matches Unidirectional Data Diode with physical layer isolation; Multi-tenant container microservice isolation requiring identity verification matches Service Mesh Microsegmentation using eBPF and mTLS attestation; Third-party remote access without direct subnet routing matches Jump Box / Bastion Host in a DMZ with proxy brokering; Public branch Wi-Fi client-to-client blocking on a shared subnet matches Private VLANs (PVLANs) configured with isolated ports.
Each segmentation technology directly aligns with the operational constraints of the scenario: physical data diodes guarantee hardware-level one-way transmission for sensitive OT logs; eBPF microsegmentation with mTLS enforces identity-based zero trust for ephemeral container workloads; proxy-based jump boxes isolate internal networks from third-party client routing; and PVLAN isolated ports restrict Layer 2 lateral communications on shared wireless subnets.

Step-by-Step Solution

1
Analyze the legacy ICS requirement for guaranteed one-way outbound data movement with zero inbound connectivity.
Identified physical unidirectional data diode enforcement as the only control preventing backchannel traffic hardware-wide.
Firewalls or software ACLs can be misconfigured or bypassed, whereas data diodes enforce hardware-level physical one-way transmission.
2
Evaluate intra-host container microservices dynamic zero-trust requirements.
Identified service mesh microsegmentation using eBPF and mTLS workload attestation.
Dynamic container environments require identity-based policy enforcement rather than static network IP subnet boundaries.
3
Evaluate third-party remote management without network-level access.
Identified jump box / bastion host with application proxy brokering in a DMZ.
Proxying session protocol payloads avoids routing network packets directly from untrusted client endpoints into corporate subnets.
4
Analyze public Wi-Fi peer-to-peer Layer 2 isolation on the same broadcast domain.
Identified Private VLANs (PVLANs) with isolated ports.
PVLAN isolated ports allow frames to flow only to promiscuous ports (gateway) and drop inter-port client communication.

Key Concept

Selecting network architecture controls based on isolation boundaries (physical, microsegmentation, proxy/bastion, and Layer 2 PVLANs).
Question 52Question

A biomedical equipment manufacturer is designing an embedded patient monitoring device intended for hospital environments where physical access to the device cannot be fully restricted. To meet strict regulatory standards, the architecture must guarantee that the initial bootloader execution sequence is validated using one-time programmable, non-volatile hardware fuses burned into the system-on-chip during manufacturing, preventing any subsequent firmware update or physical attacker from altering the initial trust anchor. Which hardware security component best establishes this immutable, non-modifiable foundation for the secure boot process?

Show answer & explanation

Answer: eFuse-backed hardware Root of Trust (RoT)

Answer

The eFuse-backed hardware Root of Trust (RoT) provides an immutable, non-modifiable foundation programmed during manufacturing to validate the initial bootloader prior to execution.
An eFuse-backed hardware Root of Trust establishes an immutable anchor by burning key hashes or configuration flags into the physical chip silicon during manufacturing. Because eFuses cannot be reset or reprogrammed, the processor reliably executes only authentic boot code before handing control to subsequent boot stages.

Step-by-Step Solution

1
Analyze the scenario requirements
Identified the need for an unalterable, manufacturing-level hardware mechanism to validate initial boot code execution under physical access threats.
Embedded systems security requires validating early boot code before loading higher-level software components.
2
Evaluate hardware-level trust mechanisms
eFuse technology irreversibly alters microscopic fuses on-chip during factory provisioning, rendering the stored public key hash or boot configuration permanently read-only.
Only physical, non-reprogrammable hardware states like eFuses ensure non-modifiability even if an attacker possesses physical access.
3
Distinguish from inadequate runtime or external controls
Ruled out external network appliances, symmetric RAM encryption, and OS software integrity monitoring.
These controls operate either outside the local boot stage, target dynamic runtime data confidentiality, or run after kernel load.

Key Concept

eFuse and Hardware Root of Trust (RoT)
Question 53Question

A software company hosts a critical customer service portal on a Managed Kubernetes platform (PaaS). The cloud service provider (CSP) maintains the master control plane, hypervisor infrastructure, and worker node operating system updates. During a recent vulnerability scan, security auditors identified critical security flaws in the application runtime dependencies packaged inside the deployment container images. Which of the following actions represents the customer's responsibility under the cloud shared responsibility model to remediate these vulnerabilities?

Show answer & explanation

Answer: Implement container image scanning in the CI/CD pipeline to detect and patch vulnerable application dependencies prior to deployment.

Answer

Implement container image scanning in the CI/CD pipeline to detect and patch vulnerable application dependencies prior to deployment.
Under the cloud shared responsibility model for Platform as a Service (PaaS) and managed container environments, the cloud service provider manages physical infrastructure, hypervisors, and the container engine/node operating system. However, the customer is strictly responsible for securing everything inside their container images, including custom application code, third-party libraries, and dependencies. Scanning container images within the CI/CD pipeline ensures vulnerable dependencies are identified and updated by the customer before deployment.

Step-by-Step Solution

1
Analyze the cloud service model and operational context.
The scenario describes a Managed Kubernetes platform operating under Platform as a Service (PaaS).
Identifying the service model establishes the boundaries between customer and CSP responsibilities.
2
Delineate responsibilities between the CSP and the customer.
The CSP manages physical hardware, hypervisors, control plane components, and worker node OS patching. The customer retains ownership of application code, container images, data, and application runtime dependencies.
Under the shared responsibility model, application code and custom container layers are exclusively managed by the tenant.
3
Evaluate remediation options based on customer ownership.
Incorporating dependency scanning and base image updating within the customer's CI/CD pipeline directly resolves the vulnerability at the customer-managed application layer.
Proactive image analysis prevents vulnerable software components from reaching production environments.

Key Concept

Cloud Shared Responsibility Model in Managed Platform Services
Estimated Time:1m 30s
Question 54Question

A medical clinic wants to allow guest patients to access the internet via wireless access points while ensuring their traffic is completely isolated from the internal network housing sensitive Electronic Health Record (EHR) systems. Which of the following network design strategies should the security administrator implement on the existing network infrastructure to achieve this isolation?

Show answer & explanation

Answer: Configure VLAN segmentation paired with access control lists to separate guest traffic from internal systems

Answer

Configure VLAN segmentation paired with access control lists to separate guest traffic from internal systems.
The correct response recommends configuring VLAN segmentation along with access control lists. VLANs separate network traffic logically at Layer 2 across shared physical switches and access points, while ACLs explicitly prevent inter-VLAN routing from the guest network to the internal EHR network zone.

Step-by-Step Solution

1
Identify the primary requirement
The requirement is to isolate guest Wi-Fi users from internal medical records on shared physical infrastructure.
Preventing unauthorized access to sensitive internal assets requires logical boundary separation at the network layer.
2
Evaluate network isolation controls
VLANs create separate broadcast domains, and ACLs enforce traffic boundaries between those domains.
VLAN tagging logically partitions physical switches and access points so guest traffic cannot reach internal IP ranges.

Key Concept

VLAN Segmentation and Traffic Isolation
Estimated Time:1m 0s
Question 55Question

An enterprise financial organization is designing a hybrid cloud connectivity model for an analytics workload that dynamically offloads data processing from on-premises servers to a public cloud Platform as a Service (PaaS) environment. Security policy mandates that data in transit must never traverse the public internet, data endpoints must not expose public IP addresses, and customer responsibility must be limited strictly to application logic, data classification, and access policies without host management overhead. Which of the following architecture designs and responsibility allocations best fulfills these requirements?

Show answer & explanation

Answer: Establish a dedicated private connection with private endpoint interfaces for cloud services; under PaaS, the provider secures the underlying host infrastructure and platform orchestrator, while the organization manages database access control and data security.

Answer

Establish a dedicated private connection with private endpoint interfaces for cloud services; under PaaS, the provider secures the underlying host infrastructure and platform orchestrator, while the organization manages database access control and data security.
Establishing a dedicated private network connection combined with private endpoints guarantees that network traffic stays off the public internet and does not use public IP addresses. In a PaaS deployment model, the cloud provider manages the underlying infrastructure, operating system, and container runtime environments, while the customer maintains responsibility for data classification, encryption, and access control governance.

Step-by-Step Solution

1
Analyze connectivity requirements.
Requirements specify that traffic must never traverse the public internet and public IPs must not be exposed.
Dedicated private connectivity (such as Direct Connect or ExpressRoute) coupled with private endpoint technologies (such as PrivateLink) ensures private IP routing directly into the cloud infrastructure.
2
Evaluate the cloud service model (PaaS) boundaries.
PaaS shifts infrastructure, hypervisor, OS, and runtime management to the Cloud Service Provider (CSP).
The customer remains responsible only for identity and access management, application logic, and data protection/classification.
3
Synthesize connectivity and responsibility model.
The architecture combining private line endpoints with PaaS shared responsibility fulfills both isolation and minimal operational overhead demands.
This combination isolates traffic at the network layer while restricting customer administrative overhead to application and data security controls.

Key Concept

PaaS Shared Responsibility and Private Cloud Connectivity
Estimated Time:2m 0s
Question 56Question

A security administrator is documenting the secure network transit path for a remote system administrator to access a sensitive internal database server via a bastion host. Arrange the following network zones in order from the initial connection point (least secure/untrusted external) to the final destination (most secure internal target).

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct network path order from external origin to secure target is: External Public Internet, Perimeter Screened Subnet (DMZ), Bastion Host Management Subnet, and Isolated Backend Database Zone.
The proper administrative connection flow follows defense-in-depth segmentation principles: the remote session starts on the untrusted External Public Internet, enters the Perimeter Screened Subnet (DMZ), authenticates at the Bastion Host Management Subnet, and finally proxies through to the Isolated Backend Database Zone.

Step-by-Step Solution

1
Identify the origin of the remote traffic flow.
The connection starts on the External Public Internet.
Remote administrative requests originate outside the enterprise network boundary.
2
Determine the external boundary entry point.
Traffic enters the Perimeter Screened Subnet (DMZ).
External requests must pass through perimeter security controls before reaching internal management components.
3
Identify the intermediary administrative proxy host zone.
Traffic reaches the Bastion Host Management Subnet.
Secure network architecture mandates terminating administrative sessions on an isolated jump box rather than allowing direct access to backend servers.
4
Identify the final protected target network zone.
The session completes at the Isolated Backend Database Zone.
The database subnet is completely isolated from the internet and accepts connections only from authenticated bastion hosts.

Key Concept

Bastion Host Jump Box and Network Zone Transit Sequence
Estimated Time:45s
Question 57Question

An organization needs to prevent customer service representatives from copying sensitive customer database files to unauthorized USB flash drives attached to local workstations. Which data protection control should the security analyst implement to enforce this restriction?

Show answer & explanation

Answer: Endpoint Data Loss Prevention (DLP)

Answer

Endpoint Data Loss Prevention (DLP) should be implemented to monitor and block unauthorized file transfers to removable USB storage.
Endpoint Data Loss Prevention (DLP) software runs directly on user workstations to inspect data in use and enforce policies that block unauthorized operations, such as copying sensitive files containing Personal Identifiable Information (PII) to removable USB media.

Step-by-Step Solution

1
Identify the risk and security objective
The objective is preventing exfiltration of sensitive data to unauthorized local USB drives.
Understanding the threat vector guides selecting the appropriate control boundary.
2
Evaluate the control mechanisms
Endpoint DLP agents inspect content on host devices and block policy violations such as write actions to removable media.
Host-based data protection mechanisms operate directly at the endpoint operating system level where USB peripherals are attached.

Key Concept

Endpoint Data Loss Prevention (DLP)
Question 58Question

A biotechnology company is deploying a cloud-native genomic analysis pipeline utilizing a Function-as-a-Service (FaaS) model coupled with managed cloud object storage. The lead security architect is formalizing operational boundaries to comply with the cloud shared responsibility model. Which of the following tasks remains exclusively the responsibility of the biotechnology company?

Show answer & explanation

Answer: Hardening application source code, managing data classification, and configuring API access authorization rules.

Answer

Hardening application source code, managing data classification, and configuring API access authorization rules.
In Function-as-a-Service (FaaS) serverless architectures, the cloud service provider abstracts away physical hardware, virtualization, and runtime environment management. However, the tenant retains full ownership and responsibility for customer data classification, application source code security, and identity and access governance (including API authorization).

Step-by-Step Solution

1
Identify the cloud service model being evaluated.
The scenario specifies Function-as-a-Service (FaaS), a serverless compute model.
Different service models (IaaS, PaaS, SaaS, FaaS) shift different infrastructure management responsibilities between the customer and provider.
2
Determine the cloud service provider's operational scope under FaaS.
The CSP manages physical infrastructure, server hardware, OS patching, runtime environment maintenance, and container orchestration.
Serverless models abstract the underlying server infrastructure away from the enterprise.
3
Determine the customer's operational scope under FaaS.
The customer is responsible for writing secure code, configuring API endpoints, enforcing IAM policies, securing data at rest and in transit, and setting access authorization controls.
Regardless of how high up the stack the cloud model moves, data security and application security remain customer responsibilities.

Key Concept

Shared Responsibility Model in Function-as-a-Service (FaaS)
Question 59Question

An enterprise security architecture team is evaluating modern Identity and Access Management (IAM) components to enhance security across hybrid environments. Based on enterprise security best practices, how should each IAM standard or architecture component be matched to its primary architectural role?

Click a left item, then click its matching right item

Items

SCIM (System for Cross-domain Identity Management)
OAuth 2.0 Token Exchange
Privileged Access Management (PAM) with Ephemeral Credentials
FIDO2 / WebAuthn Framework

Matches

Show answer & explanation

Answer

Each IAM architectural component correctly aligns with its core functionality: SCIM handles automated identity provisioning, OAuth 2.0 Token Exchange propagates identity across microservices, PAM with ephemeral credentials eliminates static admin credentials, and FIDO2/WebAuthn delivers phishing-resistant authentication.
SCIM automates cross-domain provisioning; OAuth 2.0 Token Exchange securely transfers delegative identity context across API endpoints; PAM with ephemeral credentials removes persistent privileged secrets; and FIDO2/WebAuthn provides hardware-backed, domain-bound authentication resistant to phishing.

Step-by-Step Solution

1
Analyze identity lifecycle standards
Identify SCIM as the standard protocol for automated provisioning and deprovisioning across SaaS services.
SCIM uses standardized RESTful schemas to sync user accounts between identity providers and cloud applications.
2
Evaluate token delegation in distributed systems
Identify OAuth 2.0 Token Exchange as the method for context propagation in microservice architecture.
Token exchange enables secure impersonation or delegation across backend services without exposing primary credentials.
3
Examine privileged access hardening techniques
Identify PAM with Ephemeral Credentials for dynamic short-lived administrative access.
Ephemeral credentials mitigate pass-the-hash and lateral movement risks associated with persistent admin accounts.
4
Assess strong authentication frameworks
Identify FIDO2/WebAuthn for hardware-bound, phishing-resistant authentication.
FIDO2 cryptographically binds authenticators to origin domains, preventing credential harvesting via proxy attacks.

Key Concept

Identity and Access Management Architecture Components and Protocols
Estimated Time:2m 0s
Question 60Question

A security architect is designing an Identity and Access Management (IAM) architecture for a microservices-based application deployed across multiple cloud environments. To align with Zero Trust principles, the architecture must issue short-lived, cryptographically verifiable identities to service workloads and decouple fine-grained authorization enforcement from application code. Which of the following protocols or architectural components should the architect integrate to satisfy these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: SPIFFE/SPIRE framework to automatically mint and distribute short-lived cryptographic workload identities to running services.; Decoupled Policy Decision Points (PDP) running as sidecar proxies alongside services to evaluate centralized authorization policies.

Answer

The architecture should implement the SPIFFE/SPIRE framework for workload identity attestation and decoupled Policy Decision Points (PDPs) as sidecar proxies for centralized authorization evaluation.
Implementing SPIFFE/SPIRE provides cryptographically verifiable, short-lived workload identities (SVIDs) for microservices across dynamic environments. Integrating decoupled Policy Decision Points (PDPs) via sidecar proxies allows authorization policies to be updated and evaluated centrally without altering microservice application logic.

Step-by-Step Solution

1
Identify workload identity requirements for dynamic microservice containers.
Recognize that SPIFFE/SPIRE establishes automated, short-lived, cryptographically verifiable identity documents (SVIDs) for workloads without relying on IP addresses or static credentials.
Microservices require dynamic workload attestation and identity propagation across cloud boundaries under Zero Trust.
2
Determine the appropriate pattern for decoupling fine-grained authorization logic.
Select sidecar-based Policy Decision Points (PDPs) that intercept requests and enforce access policies centrally.
Decoupling authorization logic from application code ensures consistent policy enforcement across heterogeneous services.

Key Concept

Workload Identity and Decoupled Authorization in IAM Architecture
PreviousPage 3 / 21Next
Security Architecture Practice Questions — CompTIA Security+ — Page 3 | Examkin