The Payment Card Industry Data Security Standard (PCI-DSS) is a set of security standards designed to ensure that all companies that accept, process, store, or transmit credit card information maintain a secure environment. A fundamental principle of PCI-DSS is the protection of cardholder data. Specifically, Requirement 3 mandates the protection of stored cardholder data, requiring the Primary Account Number (PAN) to be rendered unreadable wherever it is stored. Requirement 4 mandates the encryption of cardholder data during transmission over open, public networks. These requirements directly address the prohibition of exchanging or storing credit card data in cleartext.

A. CSA: The Cloud Security Alliance (CSA) provides research and best practices for cloud security (e.g., the Cloud Controls Matrix), but it is not a regulatory standard specifically for credit card data.

B. GDPR: The General Data Protection Regulation (GDPR) is a European Union regulation focused on the protection of personal data and privacy of EU citizens, not exclusively on payment card information.

C. SOC 2: A Service Organization Control 2 (SOC 2) report is an audit of a service organization's controls related to security, availability, processing integrity, confidentiality, and privacy, but it is not the specific standard governing credit card data.

1. PCI Security Standards Council. (2022). Payment Card Industry (PCI) Data Security Standard: Requirements and Security Assessment Procedures

Version 4.0. Page 48

Requirement 3.5.1 states

"Primary account number (PAN) is rendered unreadable wherever it is stored." Page 58

Requirement 4.2.1 states

"Strong cryptography and security protocols are used to safeguard PAN during transmission over open

public networks."

2. Amazon Web Services (AWS). (2024). PCI DSS Compliance. AWS Compliance Documentation. Retrieved from https://aws.amazon.com/compliance/pci-dss-level-1-faqs/. The documentation states

"The PCI DSS is a proprietary information security standard for organizations that handle branded credit cards from the major card schemes."

3. Microsoft Azure. (2024). Azure compliance documentation: PCI DSS. Microsoft Learn. Retrieved from https://learn.microsoft.com/en-us/azure/compliance/offerings/offering-pci-dss. The document clarifies

"The Payment Card Industry (PCI) Data Security Standards (DSS) is a global information security standard designed to prevent fraud through increased control of credit card data."

A Common Vulnerability and Exposure (CVE) identifies a specific, known software flaw. The standard and most direct method to remediate such a vulnerability is to apply the security patch released by the vendor. Given the critical CVSS score of 9.0 and a network attack vector, the vulnerability is remotely exploitable and poses a significant risk. Patching the operating systems directly addresses and eliminates the underlying security flaw, which is the most effective and appropriate mitigation strategy. This action is a fundamental component of vulnerability management and security hygiene.

Upgrading to beta software is not a recommended security practice for production systems as it is untested and likely contains its own bugs and vulnerabilities.

Encrypting operating system disks protects data at rest but offers no protection against a network-based attack that exploits a vulnerability in the running OS.

Disabling ports is a hardening measure but does not fix the vulnerability itself and may not be feasible if the flaw exists on a necessary, business-critical service.

1. National Institute of Standards and Technology (NIST) Special Publication 800-40r4 (Draft)

Guide to Enterprise Patch Management Planning: Preventive Maintenance for Technology. Section 2.1

"The Importance of Patch Management

" states

"Patch management is the process of identifying

acquiring

installing

and verifying patches for products and systems. Patches correct security and functionality problems in software and firmware." This establishes patching as the direct corrective action for vulnerabilities.

2. AWS Well-Architected Framework

Security Pillar (July 2023). Page 49

under "Vulnerability Management

" recommends

"Perform vulnerability scans and patching in a timely manner to reduce the attack surface... Automate patching to operating systems and applications to reduce the window of opportunity for an attacker." This highlights patching as a primary security control in a public cloud environment.

3. FIRST.org

Common Vulnerability Scoring System v3.1: Specification Document. Section 2.1

"Attack Vector (AV)

" defines the "Network" value

confirming the remote exploitability. Section 4

"Qualitative Severity Rating Scale

" categorizes a CVSS Base Score of 9.0-10.0 as "Critical

" underscoring the urgency for remediation.

4. Microsoft Azure Documentation

Remediate findings from Microsoft Defender for Endpoint. The documentation outlines the process for handling discovered vulnerabilities

stating

"After you've identified the devices at risk

you can remediate them with a security recommendation." These recommendations consistently prioritize applying vendor-supplied security updates (patches).

A direct connection, such as AWS Direct Connect, Azure ExpressRoute, or Google Cloud Interconnect, establishes a dedicated, private physical or logical network link between an on-premises data center and the cloud provider's network. By bypassing the public internet, this method avoids the variable performance, unpredictable routing, and congestion inherent to shared networks. This results in a highly consistent network experience with minimal latency and lower overhead compared to internet-based solutions like VPNs, which must contend with public network conditions and the processing overhead of encryption/decryption.

A. Site-to-site VPN: This method tunnels traffic over the public internet, which leads to unpredictable latency and performance. The encryption process also introduces computational overhead.

B. Peer-to-peer VPN: This is not the standard terminology for connecting an entire on-premises network to a cloud environment and still relies on the public internet, sharing the same drawbacks as a site-to-site VPN.

D. Peering: In a cloud context, this typically refers to connecting two virtual networks within the cloud (e.g., VPC Peering). It does not describe a dedicated connection from an on-premises location.

1. Microsoft Azure Documentation. (2023). What is Azure ExpressRoute? Microsoft Learn. In the "Benefits" section

it states

"ExpressRoute connections don't go over the public Internet. They offer more reliability

faster speeds

consistent latencies

and higher security than typical connections over the Internet."

2. Amazon Web Services Documentation. (2023). AWS Direct Connect FAQs. Under the question "How is AWS Direct Connect different from an IPsec VPN Connection?"

the documentation explains

"An IPsec VPN connection utilizes the internet... AWS Direct Connect bypasses the internet... [providing] a more consistent network experience than internet-based connections."

3. Google Cloud Documentation. (2023). Choosing a Network Connectivity product. The comparison table shows that for the requirement of "Lowest latency

" the recommended solution is "Dedicated Interconnect

" which is a direct connection. It explicitly contrasts this with Cloud VPN

which operates over the internet.

Cloud-native monitoring services (like AWS CloudWatch, Azure Monitor, or Google Cloud's operations suite) provide high-level metrics from the hypervisor by default, such as overall CPU utilization for a VM. However, to collect detailed in-guest operating system data, such as process-level memory usage, it is necessary to install a dedicated monitoring agent. This agent software runs inside the VM, collects the specified metrics directly from the OS, and sends them to the cloud monitoring service. For an autoscaling group, the agent is installed on the base machine image, ensuring all new instances automatically report these detailed metrics, making it the most effective and scalable solution.

A. Configuring page file/swap metrics: This only tracks the usage of virtual memory on disk, which is an indicator of memory pressure, not a direct measurement of memory usage by individual processes.

C. Scheduling a script to collect the data: This is a custom, non-native solution. While possible, it requires manual development and maintenance and is less integrated and reliable than using the purpose-built agent provided by the cloud platform.

D. Enabling memory monitoring in the VM configuration: This option typically enables hypervisor-level memory metrics, which report the total memory consumed by the VM as a whole, but lack the visibility to report on individual processes running inside the guest OS.

1. Amazon Web Services (AWS) Documentation. The CloudWatch agent is required to collect guest OS-level metrics. "By default

EC2 instances send hypervisor-visible metrics to CloudWatch... To collect metrics from the operating system or from applications

you must install the CloudWatch agent."

Source: AWS Documentation

"The metrics that the CloudWatch agent collects

" Section: "Predefined metric sets for the CloudWatch agent."

2. Microsoft Azure Documentation. The Azure Monitor agent is used to collect in-depth data from the guest operating system of virtual machines. "Use the Azure Monitor agent to collect guest operating system data from Azure... virtual machines... It collects data from the guest operating system and delivers it to Azure Monitor."

Source: Microsoft Learn

"Azure Monitor agent overview

" Introduction section.

3. Google Cloud Documentation. The Ops Agent is Google's solution for collecting detailed telemetry from within Compute Engine instances. "The Ops Agent is the primary agent for collecting telemetry from your Compute Engine instances. It collects both logs and metrics." The agent can be configured to collect process metrics.

Source: Google Cloud Documentation

"Ops Agent overview

" What the Ops Agent collects section.

4. Armbrust

M.

et al. (2010). A View of Cloud Computing. This foundational academic paper from UC Berkeley discusses the challenges of cloud monitoring

implying the need for mechanisms beyond the hypervisor to understand application-level performance. The distinction between what the infrastructure provider can see (hypervisor-level) and what the user needs to see (in-guest) necessitates agent-based approaches for detailed monitoring.

Source: Communications of the ACM

53(4)

50-58. Section 5.3

"Monitoring and Auditing." DOI: https://doi.org/10.1145/1721654.1721672

Infrastructure as a Service (IaaS) is the most appropriate model as it provides fundamental computing resources, including virtual servers, networking, and storage. This gives the engineering department the maximum level of control needed to provision a large cluster of servers (100+), install custom operating systems and dependencies, and deploy their in-house software for a comprehensive scalability test. The on-demand, pay-as-you-go nature of IaaS is ideal for a temporary, month-long project, allowing the company to access massive computing power without the capital expense of purchasing physical hardware.

A. PaaS abstracts the underlying server infrastructure, which would limit the team's ability to control the environment and install the specific software stack required for their test.

B. SaaS provides ready-to-use software applications, not the underlying infrastructure needed to test a company's own custom-developed software.

C. DBaaS is a specialized service for managing databases. It does not provide the general-purpose server cluster needed to run the application itself.

1. Mell

P.

& Grance

T. (2011). The NIST Definition of Cloud Computing (NIST Special Publication 800-145). National Institute of Standards and Technology.

Page 2

Section "Infrastructure as a Service (IaaS)": "The capability provided to the consumer is to provision processing

storage

networks

and other fundamental computing resources where the consumer is able to deploy and run arbitrary software

which can include operating systems and applications." This directly supports the need to deploy in-house software on a large number of servers.

2. Armbrust

M.

Fox

A.

Griffith

R.

Joseph

A. D.

Katz

R.

Konwinski

A.

Lee

G.

Patterson

D.

Rabkin

A.

Stoica

I.

& Zaharia

M. (2009). Above the Clouds: A Berkeley View of Cloud Computing (Technical Report No. UCB/EECS-2009-28). University of California

Berkeley.

Page 5

Section 3.1: Discusses how IaaS enables "pay-as-you-go" access to infrastructure

which is ideal for short-term

large-scale needs like the month-long test described

a use case often termed "batch processing" or "elastic computing."

3. Microsoft Azure Documentation. (n.d.). What is Infrastructure as a Service (IaaS)?

Section "Common IaaS business scenarios": "Test and development. Teams can quickly set up and dismantle test and development environments

bringing new applications to market faster. IaaS makes it quick and economical to scale up dev-test environments up and down." This explicitly validates using IaaS for temporary

large-scale testing.

Ephemeral storage, also known as container-scoped storage, is intrinsically tied to the lifecycle of a container. It exists as the container's writable layer. When a container is stopped, restarted, or deleted, this writable layer is destroyed, and any data written to it is permanently lost. This type of storage is suitable for temporary files or cache data that an application needs during its runtime but does not need to persist. The data does not survive a restart, which directly answers the question.

A. Object: Object storage is a persistent storage service external to the container. Data is managed as objects and is not lost when a container restarts.

B. Persistent volume: A persistent volume is an abstraction for a piece of storage that exists independently of a container's or pod's lifecycle, explicitly designed to preserve data.

D. Block: Block storage provides persistent volumes that can be attached to containers. The data on these volumes is independent of the container's lifecycle and survives restarts.

---

1. Kubernetes Documentation

"Volumes". The official Kubernetes documentation describes ephemeral volume types like emptyDir. It states

"When a Pod is removed from a node for any reason

the data in the emptyDir is deleted forever." This confirms that data in this type of volume is lost when the container's pod is terminated. (Source: Kubernetes.io

Concepts > Storage > Volumes

Section: emptyDir).

2. Docker Documentation

"Manage data in Docker". The official Docker documentation explains that data not stored in a volume is written to the container's writable layer. It clarifies

"The data doesn't persist when that container is no longer running

and it can be difficult to get the data out of the container if another process needs it." (Source: Docker Docs

Storage > Volumes > "Manage data in Docker").

3. Red Hat Official Documentation

"Understanding container storage". This vendor documentation distinguishes between ephemeral and persistent storage. For ephemeral storage

it notes

"The storage is tightly coupled with the container’s life cycle. If the container crashes or is stopped

the storage is lost." (Source: Red Hat Customer Portal

OpenShift Container Platform 4.10 > Storage > "Understanding container storage"

Section: "Ephemeral storage").

4. University of California

Berkeley

"CS 162: Operating Systems and System Programming"

Lecture 19: "Virtual Machines

Containers

and Cloud Computing". Course materials often describe the container file system as a series of read-only layers with a final writable layer for the specific container. This top writable layer is ephemeral and is discarded when the container is destroyed. (Reference concept covered in typical advanced OS/Cloud Computing university curricula).

The core of the question is protecting data from a natural disaster by using a geographically separate facility. This practice is known as off-site disaster recovery. By renting a colocation space in another part of the country, the organization establishes a secondary location that is unlikely to be affected by the same disaster that impacts the primary site. This geographic separation is the fundamental principle of an off-site strategy, ensuring business continuity and data availability in the event of a regional catastrophe.

A. On-site: This practice involves keeping data backups or redundant systems at the same physical location as the primary data, offering no protection against a site-wide disaster like a fire or flood.

B. Replication: This is the process of copying data. While replication is a mechanism used to send data to an off-site location, "off-site" is the specific disaster recovery practice described in the scenario.

C. Retention: This refers to policies that dictate how long data is stored. Data retention is unrelated to the physical location of data for disaster recovery purposes.

1. National Institute of Standards and Technology (NIST) Special Publication 800-34 Rev. 1

Contingency Planning Guide for Federal Information Systems. Section 4.3.2

"Alternate Storage Site

" states: "An alternate storage site is used for storage of backup media... The site should be geographically separated from the primary site so as not to be susceptible to the same hazards." This directly supports the concept of using a geographically distant location (off-site) for disaster protection.

2. Amazon Web Services (AWS)

Disaster Recovery of Workloads on AWS: Recovery in the Cloud (July 2021). Page 6

in the section "Backup and Restore

" discusses storing backups in a separate AWS Region. It states

"By replicating your data to another Region

you can protect your data in the unlikely event of a regional disruption." This exemplifies the off-site practice in a cloud context.

3. Microsoft Azure Documentation

Disaster recovery and high availability for Azure applications. In the section "Azure services that provide disaster recovery

" it describes Azure Site Recovery

which "replicates workloads to a secondary location." The use of a secondary

geographically distinct location is the definition of an off-site strategy.

The optimal backup solution must meet three criteria: cost-effectiveness, granular recovery, and multilocation storage.

1. Multilocation: An off-site or cloud-based storage solution is essential for disaster recovery, satisfying the multilocation requirement by storing data in a geographically separate location from the primary site.

2. Cost-Effective & Granular Recovery: A strategy combining full, incremental, and differential backups provides the most flexibility. Incremental backups are highly cost-effective as they only copy data that has changed since the last backup of any type, minimizing storage space and network bandwidth usage—key cost drivers in the cloud. All three backup types (full, incremental, differential) support the granular recovery of specific files or data points. This combination offers the best balance of recovery speed, storage cost, and data granularity.

B. Cloud site, full, and differential

This option is less cost-effective than a strategy that includes incremental backups, which consume less storage and bandwidth for frequent backups.

C. On-site. full, and incremental

On-site storage fails the multilocation requirement, as it does not protect against a site-wide disaster (e.g., fire, flood) affecting the primary data and its backup.

D. On-site. full, and differential

On-site storage fails the multilocation requirement, offering no protection from localized disasters that could destroy both the original data and the backup.

---

1. National Institute of Standards and Technology (NIST) Special Publication 800-34 Rev. 1

Contingency Planning Guide for Federal Information Systems.

Section 3.4.2.1

"Backup Types": This section details full

differential

and incremental backups. It explains that incremental backups copy data modified since the last backup

making them efficient. "Incremental backups are the most efficient because they copy the least amount of data." (Page 29).

Section 3.4.2.2

"Off-site Storage": This section explicitly states

"To protect against a disaster that could damage the primary facility...backup media should be stored at an off-site location." (Page 30). This supports the "multilocation" requirement.

2. Amazon Web Services (AWS) Documentation

How AWS Backup works.

"Backups" section: The documentation explains that AWS Backup leverages the native snapshot capabilities of services like Amazon EBS

which are incremental. "The first snapshot of a volume is always a full snapshot. Subsequent snapshots of the same volume are incremental... This saves on storage costs because data is not duplicated." This directly links the incremental method to the "cost-effective" requirement in a cloud context.

3. Microsoft Azure Documentation

About Azure VM backup.

"Backup process" section: The documentation states

"For Azure VMs

the initial backup is a full backup... Subsequent backups are incremental." This highlights that major cloud providers use incremental backups as a standard

cost-effective practice for virtual machine protection.

The requirements for immediate failover and a maximum replication latency of one second necessitate a continuous, near-real-time data protection strategy. Live replication, often implemented as synchronous or near-synchronous replication, continuously transmits data changes from the primary VM to a replica in a secondary data center as they occur. This method ensures the replica is always in a consistent and up-to-date state, enabling an immediate and automated failover with a Recovery Point Objective (RPO) of near-zero. This directly meets the stringent availability and low-latency demands described in the scenario for mission-critical applications.

A. Snapshot: Snapshot replication is periodic, creating copies at discrete intervals. This method cannot meet the immediate failover or sub-second latency requirements due to inherent data loss (RPO) between snapshots.

B. Transactional: Transactional replication is a database-specific technology that replicates database transactions. It does not apply to the entire virtual machine state, including the operating system and application files.

D. Point-in-time: This is a general term for creating a copy of data as it existed at a specific moment, which includes snapshots. It is not a continuous process and cannot support immediate failover.

1. VMware

Inc. (2023). vSphere Storage Documentation

Administering vSphere Virtual Machine Storage

Chapter 8: Virtual Machine Storage Policies. VMware. In the section "Site disaster tolerance

" the documentation explains that synchronous replication provides the highest level of availability with a Recovery Point Objective (RPO) of zero

which is essential for immediate failover scenarios. This aligns with the concept of "live" replication.

2. Kyriazis

D.

et al. (2013). Disaster Recovery for Infrastructure-as-a-Service Cloud Systems: A Survey. ACM Computing Surveys

46(1)

Article 10. In Section 3.2

"Replication Techniques

" the paper contrasts synchronous and asynchronous replication. It states

"Synchronous replication... offers a zero RPO... suitable for mission-critical applications with low tolerance for data loss." This supports the choice of a live/synchronous method for immediate failover. https://doi.org/10.1145/2522968.2522978

3. Microsoft Corporation. (2023). Azure Site Recovery documentation

About Site Recovery. Microsoft Docs. The documentation describes "continuous replication" for disaster recovery of VMs

which provides minimal RPOs. While specific RPO values vary

the principle of continuous or "live" data transfer is fundamental to achieving the low latency and immediate failover required.

The scenario describes an e-commerce website with performance degradation during "random periods," indicating unpredictable traffic spikes. Automatic elasticity is a fundamental cloud computing characteristic designed specifically for this use case. It allows the system to automatically scale resources (e.g., compute instances) up or down based on real-time demand, monitored through metrics like CPU utilization or network traffic. This ensures that the website has sufficient resources to maintain performance during unexpected surges and scales down to reduce costs when the demand subsides. This dynamic and automated approach is the most effective and efficient way to manage variable workloads.

A. Migrating to a dedicated host: This provides a fixed amount of resources. It does not dynamically scale to meet random demand and can lead to either under-provisioning or costly over-provisioning.

B. Purchasing additional servers: This is a static, capital-intensive solution. It lacks the agility to respond to real-time, random fluctuations in traffic and is not a typical cloud approach.

C. Scheduling resource allocation: This method is only effective for predictable, cyclical traffic patterns (e.g., daily or weekly peaks), not for the "random periods" mentioned in the question.

1. Mell

P.

& Grance

T. (2011). The NIST Definition of Cloud Computing (Special Publication 800-145). National Institute of Standards and Technology. On page 2

under "Essential Characteristics

" it defines Rapid elasticity: "Capabilities can be elastically provisioned and released

in some cases automatically

to scale rapidly outward and inward commensurate with demand."

2. Armbrust

M.

Fox

A.

Griffith

R.

Joseph

A. D.

Katz

R.

Konwinski

A.

... & Zaharia

M. (2010). A view of cloud computing. Communications of the ACM

53(4)

50-58. In Section 3.1

"Elasticity and the Illusion of Infinite Resources

" the UC Berkeley authors state

"Cloud Computing gives the illusion of infinite computing resources available on demand... This elasticity of resources

without paying a premium for large scale

is unprecedented in the history of IT." This directly addresses the need to handle variable demand effectively. DOI: https://doi.org/10.1145/1721654.1721672

3. Vaquero

L. M.

Rodero-Merino

L.

Caceres

J.

& Lindner

M. (2008). A break in the clouds: towards a cloud definition. ACM SIGCOMM Computer Communication Review

39(1)

50-55. In Section 3

"A Proposed Definition

" the paper highlights elasticity as a key property

stating that it "allows for the dynamic reconfiguration of the infrastructure according to the service's needs." This supports the use of elasticity for managing fluctuating performance requirements. DOI: https://doi.org/10.1145/1496091.1496100