Managing-Cloud-Security Exam Questions & Answers

With SaaS, applications are delivered entirely by the provider, and customers have little to no control over the underlying platform or data portability. This creates a higher risk of vendor lock-in, as migrating away from one SaaS provider to another may require reworking applications or losing features.

In contrast, PaaS gives customers more flexibility by allowing them to build, deploy, and manage their own applications while relying on standardized frameworks and platforms. Because applications are customer-managed, switching providers or migrating workloads can be easier compared to SaaS.

Cloud providers typically manage multi-tenant infrastructure, where physical hardware is shared among customers. Therefore, drives are not destroyed for each customer unless explicitly required in the contract. If the customer's agreement specifies dedicated hardware disposal, then the provider must comply by physically destroying the drives.

Cryptographic erasure and degaussing are valid sanitization methods, but they may not meet the specific contractual requirement of physical destruction. Insurance clauses are unrelated to disposal.

This question underscores the importance of negotiating contractual terms in cloud agreements. Customers handling highly sensitive or regulated data may require physical destruction, while others may accept logical erasure. Clear agreements ensure both compliance and alignment of security responsibilities.

Bollards are physical barriers designed to prevent vehicles from ramming into or breaching secure facilities. They are often placed at entrances, around perimeters, or in front of critical infrastructure like data centers.

Locks, cameras, and fences provide important physical security, but they cannot stop a high-speed vehicle from causing damage. Cameras record activity, fences create boundaries, and locks secure access points, but only bollards physically block or mitigate vehicle attacks.

Governmental and critical infrastructure sites commonly deploy bollards to protect against both accidental collisions and deliberate vehicle-borne attacks. Combined with layered security measures---such as surveillance and fencing---they enhance resilience against physical threats to sensitive data centers.

The most critical concern in long-term cloud storage is key management. If encryption keys are lost, corrupted, or improperly rotated, the organization will lose the ability to decrypt its own data, rendering backups unusable. This issue is particularly serious because cloud storage almost always relies on encryption to secure sensitive or regulated information.

While regulatory compliance, quantum threats, and change tracking are important, none directly prevent permanent data loss. The reliability of key management ensures that access to long-term archival data is preserved across changes in personnel, technology, and vendors.

Best practices include using centralized key management systems (such as Hardware Security Modules or cloud Key Management Services), applying role-based controls, and performing periodic key rotation and escrow. Addressing key management in the backup plan ensures that data will remain accessible for years or decades, regardless of technological shifts.

Resource pooling is one of the core characteristics of cloud computing defined by NIST. It refers to the provider's ability to serve multiple customers by dynamically allocating and reallocating computing resources such as storage, processing, memory, and network bandwidth. These resources are abstracted using virtualization, ensuring that customers remain isolated from one another even though they share the same physical assets.

Rapid scalability describes elasticity, on-demand self-service allows users to provision resources without provider intervention, and measured service refers to metering usage. None of these concepts directly describe the multi-tenant model of shared resources.

Resource pooling improves efficiency, reduces costs, and provides flexibility, but it also introduces new security considerations such as data isolation and hypervisor security. Customers must ensure that providers implement strong controls to prevent data leakage or cross-tenant compromise.