Security Architecture

405 questions

Question 1Question

An enterprise security architect is redesigning identity infrastructure to align with Zero Trust principles for a hybrid workforce. The organization must support real-time token revocation and risk evaluation for SaaS resources when user posture changes, as well as eliminate persistent administrator credentials on legacy infrastructure by enforcing ephemeral privilege allocation. Which TWO of the following identity and access management architecture components or protocols must be implemented to fulfill these requirements?

Select all that apply

Show answer & explanation

Answer: Identity Provider (IdP) integration supporting the Continuous Access Evaluation Protocol (CAEP) and Shared Signals Framework; Privileged Access Management (PAM) vault utilizing Just-In-Time (JIT) provisioning and short-lived ephemeral credentials

Answer

The correct architecture requires integrating an Identity Provider supporting the Continuous Access Evaluation Protocol (CAEP) alongside a Privileged Access Management (PAM) framework utilizing Just-In-Time (JIT) provisioning with ephemeral credentials.
Zero Trust IAM architecture requires continuous risk evaluation and minimization of standing privileges. Implementing CAEP (Continuous Access Evaluation Protocol) allows IdPs and SaaS platforms to exchange real-time security events to revoke access tokens immediately upon risk detection. Implementing a PAM vault with JIT temporary credentials removes standing administrator accounts by dynamically assigning short-lived privileges only when required.

Step-by-Step Solution

1
Analyze requirement 1: Dynamic session revocation and real-time posture risk evaluation across SaaS apps.
Identify that standard OAuth2/OIDC refresh token lifecycles are periodic; Continuous Access Evaluation Protocol (CAEP) / Shared Signals Framework enables real-time event-driven session revocation across identity providers and relying parties.
Enforces continuous verification rather than trusting static long-lived tokens.
2
Analyze requirement 2: Elimination of persistent privileged accounts on internal server infrastructure.
Identify Privileged Access Management (PAM) with Just-In-Time (JIT) credentialing as the standard architectural control for dynamic temporary elevation without standing administrative permissions.
Minimizes the blast radius of credential harvesting by ensuring privileged credentials expire immediately after administrative tasks.

Key Concept

Zero Trust IAM Architecture, CAEP, and Privileged Access Management (PAM)
Question 2Question

An enterprise deploys several virtual machines in a cloud environment. The organization's internal IT team is responsible for installing operating system security patches, configuring guest firewalls, and managing application software, while the cloud provider manages the underlying physical hardware and hypervisor infrastructure. Which cloud service model is being used?

Show answer & explanation

Answer: Infrastructure as a Service (IaaS)

Answer

Infrastructure as a Service (IaaS)
Infrastructure as a Service (IaaS) provides customers with virtualized computing resources over the cloud. Under the shared responsibility model for IaaS, the cloud provider manages the physical data centers, hardware servers, storage, and hypervisors, whereas the client remains fully responsible for managing and securing the guest operating systems, network configurations, database instances, and installed applications.

Step-by-Step Solution

1
Analyze the customer's operational responsibilities described in the scenario
The customer manages operating system patching, guest firewall rules, and application installations.
Identifying the highest level of system access controlled by the client defines the boundary of the shared responsibility model.
2
Analyze the cloud service provider's responsibilities described in the scenario
The vendor maintains the physical servers, data center facilities, and hypervisors.
Determining what infrastructure components are outsourced helps classify the service model.
3
Map the responsibility allocation to standard cloud service models
Providing raw compute, storage, and networking hardware while leaving OS control to the consumer defines Infrastructure as a Service (IaaS).
IaaS provides bare virtualization resources where the client retains control from the guest OS upward.

Key Concept

Cloud Service Models and Shared Responsibility Boundaries
Question 3Question

Match each enterprise security management scenario to the cloud service model that reflects its allocation of customer responsibilities under the Shared Responsibility Model.

Click a left item, then click its matching right item

Items

Managing virtual machine operating system patches, guest firewall rules, and persistent storage volume encryption
Configuring application logic, database access controls, and custom API endpoints while the provider manages runtime binaries
Managing user identity governance, role-based permissions, and data loss prevention policies for a vendor-hosted turn-key application
Securing event-driven execution code and trigger definitions while the provider handles automatic container scaling and host OS management

Matches

Show answer & explanation

Answer

Operating system patching and guest firewall configuration match Infrastructure as a Service (IaaS). Application logic and database access control configuration match Platform as a Service (PaaS). User identity governance and data loss prevention for pre-built applications match Software as a Service (SaaS). Event-driven code execution and trigger definitions match Function as a Service (FaaS).
Each cloud service model defines a distinct boundary of ownership under the Shared Responsibility Model: IaaS grants customer control over guest OS and virtual networking; PaaS isolates customer control to application logic and data schemas; SaaS restricts customer management to user access, data protection, and client devices; and FaaS delegates container scaling and OS maintenance to the provider while the customer provides serverless code functions.

Step-by-Step Solution

1
Analyze the customer control boundary for each administrative task scenario.
Tasks range from low-level OS management to high-level application access governance and serverless trigger setup.
The cloud shared responsibility model dictates customer responsibilities based on the abstraction layer of the chosen service model.
2
Associate lower-level infrastructure administration with compute-focused delivery models.
Guest operating system patching and virtual storage encryption belong to IaaS.
IaaS provides virtualized hardware resources where OS maintenance falls on the tenant.
3
Differentiate application runtime management from ephemeral execution.
Persistent application configuration maps to PaaS, while short-lived event-driven function management maps to FaaS.
PaaS abstracts OS management for hosted application frameworks, whereas FaaS abstracts long-running servers completely.
4
Identify complete vendor-hosted software management.
Turn-key applications where the customer manages only access permissions and data map to SaaS.
SaaS abstracts all infrastructure and software maintenance away from the cloud consumer.

Key Concept

Cloud Shared Responsibility Model across Service Models
Question 4Question

Match each cloud service model to the primary component managed by the enterprise customer under the cloud shared responsibility model.

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)

Matches

Show answer & explanation

Answer

Infrastructure as a Service (IaaS) matches guest operating system maintenance, installed application stacks, and virtual network security settings; Platform as a Service (PaaS) matches application source code and stored data; Software as a Service (SaaS) matches user credential management and data access permissions.
Each cloud service model defines clear boundaries for the shared responsibility model: IaaS requires customer configuration of guest operating systems and virtual networks; PaaS limits customer responsibility to application code and data management; SaaS restricts customer management strictly to user authentication and data access controls.

Step-by-Step Solution

1
Determine customer responsibilities for Infrastructure as a Service (IaaS).
IaaS leaves operating system management, virtual networking, and application security to the customer.
The provider only maintains physical servers, facilities, and the hypervisor layer.
2
Determine customer responsibilities for Platform as a Service (PaaS).
PaaS limits customer control to deployed application code and data.
The provider handles operating system administration, runtime environments, and database engines.
3
Determine customer responsibilities for Software as a Service (SaaS).
SaaS leaves user credentials and data access policies as the primary customer responsibilities.
The provider operates and secures the full application software stack.

Key Concept

Cloud Shared Responsibility Model across IaaS, PaaS, and SaaS service models.
Question 5Question

A financial institution maintains its core transactional database within an on-premises data center to strictly observe regulatory data sovereignty mandates. During peak quarterly reporting periods, local compute capacity is insufficient. The security team implements an automated architecture that securely extends non-sensitive processing workloads into a third-party public cloud environment while maintaining dedicated encrypted connectivity back to the private data center. Which cloud deployment model is being utilized in this scenario?

Show answer & explanation

Answer: Hybrid cloud

Answer

The scenario describes a hybrid cloud deployment model utilizing cloud bursting.
A hybrid cloud deployment integrates two or more distinct cloud infrastructures (such as private/on-premises and public cloud) bound together by standardized technology that enables data and application portability. Dynamically expanding local private capacity into public cloud compute during peak demand is known as cloud bursting.

Step-by-Step Solution

1
Analyze the environment components described in the scenario.
Identified an existing on-premises data center operating alongside a third-party public cloud service.
Determining the infrastructure boundaries helps classify the deployment model.
2
Evaluate the workload operational interaction between the environments.
The organization dynamically scales capacity from on-premises into the public cloud for overflow processing (cloud bursting).
Bridging private and public environments to share workloads defines hybrid cloud functionality.

Key Concept

Hybrid Cloud Deployment and Cloud Bursting
Estimated Time:1m 0s
Question 6Question

A financial technology firm processes sensitive payment transactions using a serverless architecture (Function-as-a-Service) and utilizes a third-party Software-as-a-Service (SaaS) platform for customer records management. Which of the following security tasks remain the sole responsibility of the enterprise customer across these cloud deployment models? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Developing secure application source code and defining IAM role permissions for the serverless functions.; Classifying organizational data and administering user access rights within the SaaS platform.

Answer

The enterprise customer is strictly responsible for developing secure serverless application code, managing IAM role policies, classifying organizational data, and controlling user access within the SaaS application.
Under the cloud shared responsibility model, higher abstraction models (such as FaaS and SaaS) transfer physical infrastructure, operating system maintenance, and host application management to the cloud provider. However, regardless of the deployment model, the customer always retains ultimate responsibility for data classification, identity and access management (IAM), and custom code development.

Step-by-Step Solution

1
Evaluate customer responsibilities in Function-as-a-Service (FaaS)
In FaaS, the cloud provider abstracts away servers, operating systems, and runtime provisioning. The customer is solely responsible for code security, data handling, and access permissions (IAM).
Understanding the boundary of abstraction in serverless compute models.
2
Evaluate customer responsibilities in Software-as-a-Service (SaaS)
In SaaS, the provider manages the application code, infrastructure, and hardware availability. The customer remains responsible for data governance, classification, user management, and authorization.
Identifying shared responsibility limits in application-level cloud services.
3
Select tasks common to customer ownership
Writing secure code and configuring IAM for serverless functions, alongside classifying data and managing user access in SaaS, fall entirely on the customer.
Matching shared responsibility allocation across abstract cloud service models.

Key Concept

Cloud Shared Responsibility Model across FaaS and SaaS
Estimated Time:1m 30s
Question 7Question

A financial institution is refactoring a monolithic legacy application into a serverless Function-as-a-Service (FaaS) architecture managed via a public cloud provider's API gateway. The cloud provider maintains the underlying physical infrastructure, host hypervisors, and serverless execution runtimes. During an architecture security review, the lead security engineer must establish control placement and operational duties aligned with the cloud shared responsibility model and Zero Trust principles. Which of the following architectural strategies correctly defines the division of security responsibilities between the organization and the cloud provider?

Show answer & explanation

Answer: The organization is responsible for securing function code, configuring API gateway authorization policies, and defining IAM least-privilege execution roles, while the provider manages runtime container isolation, host OS patching, and physical infrastructure.

Answer

The organization is responsible for securing function code, configuring API gateway authorization policies, and defining IAM least-privilege execution roles, while the provider manages runtime container isolation, host OS patching, and physical infrastructure.
Under the cloud shared responsibility model for serverless (FaaS) deployments, the cloud service provider manages the physical facilities, server hardware, hypervisors, operating system patching, and function execution runtimes. The customer retains ownership and responsibility for their application code security, API gateway policy definition, data protection, and least-privilege Identity and Access Management (IAM) role scoping.

Step-by-Step Solution

1
Analyze the cloud service model
Identified the architecture as Function-as-a-Service (FaaS) integrated with an API gateway.
The service model dictates where the provider's management ends and the customer's governance begins.
2
Delineate shared responsibility boundaries for FaaS
The provider abstracts the hardware, host OS, container runtime, and hypervisors. The customer owns data, application code, API configuration, and identity/access management (IAM).
In serverless deployments, customers do not manage underlying servers or operating systems, but remain fully accountable for code security and access policies.
3
Apply Zero Trust and AAA principles
Verified that authentication at the gateway does not replace downstream fine-grained authorization, and perimeter trust must be rejected in favor of explicit verification.
Zero Trust mandates explicit verification across all microservice transactions.

Key Concept

Cloud Shared Responsibility Model in Serverless (FaaS) Architectures
Question 8Question

An organization hosts its web application using a Platform as a Service (PaaS) model from a public cloud service provider. Under the cloud shared responsibility model, which TWO of the following tasks remain the responsibility of the customer?

Select all that apply

Show answer & explanation

Answer: Configuring application-level identity access controls and authorization settings; Securing custom application source code and managing database data classification

Answer

The customer is responsible for configuring application-level access controls and securing custom application code along with data classification.
Under Platform as a Service (PaaS), the cloud service provider abstracts and manages the underlying hardware, hypervisor, and operating system. The customer remains strictly responsible for securing their custom application source code, data classification, user identities, and application-level access controls.

Step-by-Step Solution

1
Identify the cloud service model referenced in the scenario
The model is Platform as a Service (PaaS).
Different cloud models (IaaS, PaaS, SaaS) divide responsibilities differently between the provider and customer.
2
Determine the division of responsibilities for PaaS
The Cloud Service Provider (CSP) manages physical infrastructure, hardware, network virtualization, and the operating system/runtime environment. The customer manages application logic, code, user access permissions, and data security.
PaaS abstracts the underlying operating system and hardware layer away from the customer.
3
Evaluate the choices based on customer responsibilities
Application authorization configuration and application code/data classification are customer duties. OS patching and hypervisor perimeter defense are CSP duties.
Customer responsibility stops above the runtime/OS layer in PaaS deployments.

Key Concept

Cloud Shared Responsibility Model (PaaS)
Question 9Question

A logistics enterprise is migrating its legacy inventory management platform to a cloud-hosted Infrastructure as a Service (IaaS) environment. As part of establishing the operational security baseline, the security team is defining the boundary of duties between the customer organization and the cloud service provider (CSP). Based on the cloud shared responsibility model, which of the following security tasks is the exclusive responsibility of the customer organization?

Show answer & explanation

Answer: Patching the guest operating system and configuring host-based firewall rules on virtual machines

Answer

Patching the guest operating system and configuring host-based firewall rules on virtual machines is the exclusive responsibility of the customer organization.
Under Infrastructure as a Service (IaaS), the cloud service provider is responsible for the 'security OF the cloud' (hardware, hypervisors, physical network, facility controls), whereas the customer is responsible for 'security IN the cloud' (guest operating system maintenance, middleware, application installation, data classification, and host firewall configuration). Therefore, patching guest operating systems and setting up host firewalls is entirely the customer's duty.

Step-by-Step Solution

1
Identify the cloud service model referenced in the scenario.
The scenario specifies an Infrastructure as a Service (IaaS) deployment.
Different service models (IaaS, PaaS, SaaS) partition duties differently between the customer and provider.
2
Analyze the scope of responsibility assigned to the customer in IaaS.
In IaaS, the cloud provider manages hardware, facilities, network abstraction, and hypervisor software, while the customer manages OS, applications, runtime environments, and data controls.
The boundary of control starts at the guest operating system layer for the customer.
3
Evaluate each task against the IaaS responsibility boundary.
Guest OS patching and host firewall configuration fall above the hypervisor line, making them customer responsibilities.
The provider does not have access to manage or patch internal guest OS settings on tenant virtual machines.

Key Concept

Cloud Shared Responsibility Model in IaaS
Question 10Question

A security architect is updating the network architecture for a pharmaceutical company's laboratory. The network contains legacy instrument controllers operating on legacy software alongside modern cloud-connected analytics platforms. The legacy controllers must transmit processed test metrics to an internal staging database, but must be prohibited from initiating connections to the internet or directly communicating with general corporate workstations. Which of the following controls should the security architect implement to enforce isolation while accommodating operational needs? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Place legacy controllers on a dedicated VLAN with firewall stateful packet inspection rules restricting East-West traffic exclusively to required ports on the staging database.; Implement an administrative jump box host configured with multi-factor authentication and role-based access for remote maintenance of the legacy controllers.

Answer

The correct controls are placing the legacy controllers on a dedicated VLAN with strict East-West firewall rules and deploying an administrative jump box with multi-factor authentication for maintenance access.
Placing legacy lab equipment on a segregated VLAN with restrictive firewall rules enforces microsegmentation and limits East-West network flow exclusively to necessary staging destinations. Pairing this with a jump box ensures administrative management occurs through an audited, multi-factor authenticated transit host rather than direct workstation-to-controller sessions.

Step-by-Step Solution

1
Analyze the operational requirements and security risks associated with legacy equipment on unsupported systems.
Identified that legacy devices must reach the internal staging database but present high exposure risks if exposed to broader internal or external networks.
Legacy systems lack modern host hardening and patch support, requiring strict network-level isolation.
2
Select network containment and access control mechanisms appropriate for secure architecture design.
Determined that VLAN isolation with firewalled East-West access controls restricts communication pathways, and a jump box secures administrative ingress.
VLAN isolation prevents unauthorized lateral movement while the jump server acts as an audited ingress point for administration.
3
Evaluate and eliminate incorrect architectural control choices.
Rejected edge-only perimeter firewall reliance and inline honeypot deployments.
Edge firewalls do not stop internal lateral movement, and honeypots are deception mechanisms rather than inline traffic filters.

Key Concept

Secure Network Architecture and East-West Traffic Isolation
Question 11Question

A pharmaceutical research firm integrates an on-premises high-performance compute cluster with a cloud-managed Platform as a Service (PaaS) database pipeline to process sensitive genomic records across a hybrid cloud model. To protect data in transit and control unauthorized access, the security team implements an inline Cloud Access Security Broker (CASB) alongside microsegmentation. When evaluating security responsibility boundaries under this PaaS architecture, which security management task remains exclusively the responsibility of the cloud customer?

Show answer & explanation

Answer: Managing customer-managed encryption keys (CMEK) and defining database user privilege policies

Answer

Managing customer-managed encryption keys (CMEK) and defining database user privilege policies is exclusively the customer's responsibility in a PaaS model.
Under the cloud shared responsibility model for Platform as a Service (PaaS), the cloud service provider abstract and manages the underlying hardware, hypervisors, and database engine software. However, data ownership, access control configurations, user entitlement definitions, and data-at-rest encryption key lifecycle management (such as CMEK) always remain under the explicit administrative control of the cloud customer.

Step-by-Step Solution

1
Identify the cloud service model referenced in the scenario.
The scenario explicitly specifies a Platform as a Service (PaaS) database pipeline deployment.
Shared responsibility boundaries vary significantly between IaaS, PaaS, and SaaS models.
2
Analyze the scope of Cloud Service Provider (CSP) responsibilities in PaaS.
The CSP manages physical facility security, hypervisor infrastructure, host OS patching, database runtime software, and physical hardware maintenance.
PaaS abstracts the underlying infrastructure and operating system from the customer.
3
Analyze the customer's responsibilities in PaaS.
The customer retains full ownership and responsibility for data classification, application data access policies, database user account privileges, and customer-managed encryption keys (CMEK).
Regardless of cloud model, data ownership and access governance remain entirely under customer control.

Key Concept

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

A security administrator is drafting baseline policies to align the enterprise network with Zero Trust Architecture (ZTA) principles. Which of the following fundamental tenets should be included in these guidelines? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Explicitly verify the identity, context, and security posture of every access request regardless of user location.; Enforce least privilege access by restricting user permissions to only the specific resources required for their role.

Answer

The correct answers are the principles of explicit verification of all requests and enforcing least privilege access.
Zero Trust Architecture operates on the core philosophy of 'Never Trust, Always Verify'. This entails explicitly authenticating and authorizing every request regardless of origin, and applying least privilege access controls to limit potential damage from compromised accounts or assets.

Step-by-Step Solution

1
Identify core Zero Trust Architecture (ZTA) principles.
ZTA relies on foundational tenets including 'Never Trust, Always Verify', explicit verification, least privilege, and assumed breach.
Establishing accurate baseline policies requires distinguishing Zero Trust tenets from legacy perimeter defenses.
2
Evaluate the option regarding explicit verification.
Verifying identity, device posture, and context for all access requests regardless of location directly reflects the 'Explicitly Verify' tenet.
Zero Trust eliminates implicit trust based on network location.
3
Evaluate the option regarding least privilege access.
Restricting permissions to only necessary resources directly aligns with the 'Least Privilege' tenet.
Limiting access reduces the blast radius of potential security compromises.

Key Concept

Core Tenets of Zero Trust Architecture
Question 13Question

A security engineer is evaluating an enterprise microservices platform where multiple application containers share the underlying Linux host kernel. The engineer needs to enforce a control that restricts containerized application processes from issuing unauthorized or risky system calls (syscalls) directly to the host kernel. Which of the following mechanisms best satisfies this security requirement?

Show answer & explanation

Answer: Applying secure computing mode (seccomp) profiles to restrict allowable kernel system calls

Answer

Applying secure computing mode (seccomp) profiles to restrict allowable kernel system calls
Secure computing mode (seccomp) allows administrators to restrict which system calls a containerized process can execute on the host kernel, significantly reducing the surface area for kernel vulnerabilities and container escape attacks.

Step-by-Step Solution

1
Identify the threat and architecture model
Containers run as isolated process sets sharing a single underlying host kernel.
Because containers share the host kernel, malicious or compromised process execution can leverage unnecessary system calls to achieve host kernel compromise or container escape.
2
Evaluate technical controls for system call filtering
Seccomp (Secure Computing Mode) defines syscall white-lists/black-lists enforced directly by the Linux kernel.
Restricting process syscall access via seccomp profiles effectively minimizes the attack surface against the shared kernel.

Key Concept

Container System Call Filtering via Seccomp
Question 14Question

A network administrator needs to ensure that a critical database server remains operational without data loss or downtime if a single internal storage drive fails. Which of the following technical controls directly provides this internal drive-level fault tolerance?

Show answer & explanation

Answer: Redundant Array of Independent Disks (RAID) storage configuration

Answer

Redundant Array of Independent Disks (RAID) storage configuration
A Redundant Array of Independent Disks (RAID) configuration provides immediate hardware fault tolerance by duplicating data or distributing parity across multiple physical drives. If a single drive fails, the server continues to function normally without interruption or data loss.

Step-by-Step Solution

1
Identify the primary requirement
The requirement calls for drive-level fault tolerance within a single server to prevent downtime during a hardware disk failure.
Understanding the scope of the risk (single disk failure inside one server chassis) narrows the optimal solution to storage fault tolerance.
2
Evaluate storage fault tolerance technologies
RAID combines multiple physical hard drives into a single logical unit to provide disk redundancy and parity.
If one drive fails in a fault-tolerant RAID setup, the server remains operational while the array rebuilds data.

Key Concept

Disk Redundancy and Fault Tolerance
Question 15Question

A security team is evaluating a microservices environment where untrusted code executes inside application containers on a shared host operating system. The development team asserts that Linux control groups (cgroups) and namespaces provide the same level of boundary separation as a hardware-assisted Type-1 hypervisor. Which of the following security risks should the security team highlight as the primary concern with this architecture?

Show answer & explanation

Answer: A kernel-level privilege escalation vulnerability inside a container can lead to a host compromise because containers share the host kernel.

Answer

A kernel-level privilege escalation vulnerability inside a container can lead to a host compromise because containers share the host kernel.
The correct option correctly points out that application containers share the host operating system kernel. While Linux namespaces and control groups isolate system resource views and restrict resource usage, they do not create a separate guest kernel or hardware virtualization layer. Consequently, a privilege escalation flaw or zero-day vulnerability in the host kernel can allow a container escape, granting full host access.

Step-by-Step Solution

1
Analyze the isolation architecture proposed by the development team.
The proposed architecture uses application containers dependent on host OS Linux kernel facilities (namespaces and cgroups) rather than virtual machines with hypervisor isolation.
Understanding the operational boundary of containers vs. hypervisors is essential to evaluating risk.
2
Evaluate the risk associated with shared kernel architectures.
Because all containers running on the host interact directly with the same underlying OS kernel syscall interface, any successful kernel exploit allows an attacker to break out of the container boundary.
Identifying shared components reveals single points of failure in multi-tenant systems.
3
Select the option that accurately describes this structural risk.
The risk of kernel vulnerability exploitation leading to host compromise correctly highlights the security trade-off between containerization and full virtualization.
Virtual machines enforce hardware-level separation via a hypervisor, whereas standard containers share the host kernel.

Key Concept

Container Isolation vs Virtual Machine Hypervisor Boundaries
Question 16Question

A organization needs to integrate its internal directory service with external cloud services so that employees can authenticate to third-party web portals using their existing corporate credentials. Which XML-based open standard should the identity architect select to enable cross-domain single sign-on (SSO)?

Show answer & explanation

Answer: Security Assertion Markup Language (SAML)

Answer

Security Assertion Markup Language (SAML)
Security Assertion Markup Language (SAML) is an XML-based framework used for exchanging security assertions containing authentication details between an identity provider and external service providers, enabling web-based federated single sign-on.

Step-by-Step Solution

1
Identify the core requirement
The requirement calls for an XML-based open standard that supports cross-domain single sign-on (SSO) to external web applications using corporate credentials.
Establishing identity federation across disparate organizational boundaries requires a standard token format for asserting user identities securely across web browsers.
2
Evaluate candidate protocols
Security Assertion Markup Language (SAML) uses XML assertions passed via HTTP to authenticate users between an Identity Provider (IdP) and a Service Provider (SP).
Protocols such as LDAP, RADIUS, and Kerberos are designed for local network directory queries or network access AAA, rather than federated web SSO.

Key Concept

Federated Identity and SAML Architecture
Estimated Time:45s
Question 17Question

A security analyst is establishing baseline service level objectives for system availability and recovery. Match each resiliency metric on the left with its corresponding definition on the right.

Click a left item, then click its matching right item

Items

Recovery Time Objective (RTO)
Recovery Point Objective (RPO)
Mean Time Between Failures (MTBF)
Mean Time to Repair (MTTR)

Matches

Show answer & explanation

Answer

Recovery Time Objective (RTO) pairs with maximum acceptable service disruption duration; Recovery Point Objective (RPO) pairs with maximum acceptable data loss time; Mean Time Between Failures (MTBF) pairs with average operational uptime before failure; Mean Time to Repair (MTTR) pairs with average time required to repair a failed component.
Each metric uniquely defines a specific resilience or availability constraint: RTO defines outage duration tolerance, RPO defines data loss age limits, MTBF calculates component reliability, and MTTR measures repair efficiency.

Step-by-Step Solution

1
Differentiate between time-to-recover metrics (RTO) and data-loss metrics (RPO).
RTO measures duration of downtime, while RPO measures volume/age of data loss.
RTO focuses on service restoration speed, whereas RPO focuses on data restoration limits.
2
Distinguish system reliability metrics (MTBF) from maintenance efficiency metrics (MTTR).
MTBF quantifies how long a system operates reliably without failing, while MTTR quantifies how quickly repairs are completed after a failure occurs.
MTBF reflects system durability, whereas MTTR reflects incident resolution speed.

Key Concept

High Availability and Resilience Metrics (RTO, RPO, MTBF, MTTR)
Question 18Question

A security architect is updating the network architecture for an organization that hosts public-facing web services, internal corporate workstations, and backend databases containing confidential payment data. Which of the following network segmentation controls and design practices should the architect implement to secure East-West traffic and isolate these environments? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Place public-facing web servers in a screened subnet (DMZ) to prevent external untrusted traffic from directly accessing backend database servers.; Implement microsegmentation using internal next-generation firewalls to continuously filter and restrict traffic moving laterally between server zones.

Answer

The architect should deploy public web servers in a screened subnet (DMZ) to prevent direct inbound database connectivity, and implement microsegmentation via internal next-generation firewalls to inspect lateral East-West traffic.
Establishing a screened subnet (DMZ) ensures external web traffic is isolated from internal databases, while microsegmentation restricts lateral movement between internal workload zones by applying policy checks on East-West communications.

Step-by-Step Solution

1
Analyze North-South traffic control requirements
Identify that public-facing web servers require isolation from sensitive internal backend systems.
Placing web application servers in a screened subnet (DMZ) ensures that exposed endpoints cannot initiate unrestricted connections into database zones.
2
Analyze East-West traffic control requirements
Identify that lateral movement between internal tiers must be restricted using policy-based enforcement.
Microsegmentation partitions internal networks into granular zones and enforces firewall policies on inter-segment communication.
3
Evaluate distractor controls against security best practices
Reject single-perimeter trust assumptions and shared VLAN topologies.
Implicit trust models and combined untrusted/sensitive VLANs violate isolation standards.

Key Concept

Network Segmentation and Microsegmentation
Question 19Question

An enterprise organization is updating its hybrid storage security architecture to enhance protection for sensitive databases stored on storage area networks (SAN) and prevent unauthorized exfiltration of proprietary data. The security team requires a solution that provides dedicated hardware-backed key protection for disk volume encryption keys, as well as real-time content inspection of egress traffic to block unauthorized data transfers. Which of the following technical controls should the security architect select to meet these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Deployment of a Hardware Security Module (HSM) to generate, store, and manage key encryption keys (KEKs) for disk volume protection.; Implementation of a Network-based Data Loss Prevention (DLP) solution at network perimeter egress points to inspect outbound traffic.

Answer

The security architect should implement a Hardware Security Module (HSM) for dedicated cryptographic key management and a Network Data Loss Prevention (DLP) system for real-time monitoring and blocking of unauthorized data egress.
Implementing a Hardware Security Module (HSM) ensures secure, hardware-rooted management and protection of key encryption keys (KEKs) used to lock storage volume keys. Complementing this with a Network-based Data Loss Prevention (DLP) engine enables real-time deep packet inspection of egress traffic to enforce compliance policies and block sensitive data exfiltration.

Step-by-Step Solution

1
Identify the requirement for hardware-backed encryption key protection.
Selected Hardware Security Module (HSM) deployment for cryptographic key lifecycle management.
HSMs offer tamper-resistant hardware environments for managing Key Encryption Keys (KEKs) that secure storage volume encryption keys.
2
Identify the requirement for real-time egress content inspection.
Selected Network Data Loss Prevention (DLP) solution.
Network DLP inspects protocol traffic at network boundaries to prevent sensitive files and data patterns from unauthorized exfiltration.

Key Concept

Data Protection and Storage Security Architecture
Question 20Question

An enterprise security architect is designing a hybrid Identity and Access Management (IAM) solution to enable Single Sign-On (SSO) for employees accessing both legacy on-premises systems and cloud-hosted web applications. The legacy systems rely on internal Active Directory Domain Services (AD DS) and Kerberos tickets, whereas the cloud applications require SAML 2.0 security assertions. Which of the following architectural controls and components must be deployed to support this hybrid authentication design? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: An Identity Provider (IdP) federation bridge to translate internal Active Directory authentication states into signed SAML assertion tokens for cloud applications.; An on-premises directory connector agent to synchronize user identity attributes and securely validate credentials against internal domain controllers.

Answer

The correct architecture requires deploying an Identity Provider (IdP) federation bridge to convert internal directory authentication states into SAML assertions, alongside an on-premises directory connector agent to synchronize user attributes and validate credentials.
In a hybrid IAM architecture, connecting legacy Active Directory environments with cloud web applications requires two primary components: an Identity Provider (IdP) federation bridge (such as AD FS or a cloud IdP bridge) to generate SAML tokens for web service providers, and a directory connector agent to synchronize identities and delegate password validation back to on-premises domain controllers.

Step-by-Step Solution

1
Analyze the identity requirements across environments.
On-premises legacy systems require Active Directory and Kerberos, while cloud applications rely on SAML 2.0 web assertions.
Cloud software-as-a-service applications cannot directly consume Kerberos tickets generated by internal domain controllers over the internet.
2
Identify the federation requirement for SAML token generation.
Deploying an Identity Provider (IdP) federation bridge allows the organization to authenticate users internally and issue signed SAML assertions to cloud application Service Providers (SPs).
Federation bridges bridge the gap between internal network authentication protocols and external web token standards.
3
Identify the identity lifecycle and validation component.
Deploying an on-premises directory connector syncs account objects and forwards credential validation requests securely.
The cloud IdP requires up-to-date user object attributes and a secure pathway to verify passwords against internal Active Directory domain controllers.

Key Concept

Hybrid Identity and Federation Architecture
Page 1 / 21Next