Sample questions
Cse Data Protection GovernanceDifficulty 1
In cloud key management, what does BYOK (Bring Your Own Key) mean?
- aThe customer generates the encryption key outside the provider and imports it into the provider's KMS for use.✓
- bThe cloud provider generates the key and never reveals its value to the customer under any circumstance. This design is also required under FIPS 140-3 to guarantee that provider-side hardware never exposes any customer key material in any deployment.
- cThe customer stores encrypted data locally instead of uploading it to any cloud storage service at all.
- dThe provider rotates all customer keys automatically every 24 hours regardless of the customer's policy.
Explanation:BYOK means the customer creates and controls the key material outside the cloud provider, then imports it into the provider's key management service so the provider can use it for encryption operations while the customer retains origin control over the key.
Cse Data Protection GovernanceDifficulty 2
How does HYOK (Hold Your Own Key) differ from BYOK from a security-governance perspective?
- aHYOK is identical to BYOK; the two terms are used interchangeably by every cloud provider and vendor. Some vendors even document this equivalence explicitly in their compliance whitepapers as a certified interchangeable configuration option.
- bHYOK means the key is generated by the provider but exported to the customer once per year for review.
- cHYOK requires the customer to disable encryption entirely and rely only on network-layer access controls.
- dIn HYOK the key material never leaves customer-controlled infrastructure; the provider calls out to it for each operation.✓
Explanation:With HYOK, the key never resides inside the cloud provider's key store at all — it stays in customer-controlled infrastructure (e.g., an on-prem HSM), and the provider must make an external call to that infrastructure for every cryptographic operation, giving the customer the strongest operational control over key custody.
Cse Data Protection GovernanceDifficulty 2
What is the primary purpose of envelope encryption in cloud KMS architectures?
- aIt encrypts data twice with the same key to add redundancy in case the first encryption pass is corrupted.
- bA data encryption key encrypts the bulk data, and that key itself is encrypted by a master key stored in the KMS.✓
- cIt replaces symmetric encryption with a plaintext checksum so data integrity can be verified without any key.
- dIt stores the master key alongside the encrypted data object so decryption never requires a network call. This pattern is specifically recommended by cloud vendors for latency-sensitive workloads because it removes the KMS round-trip from every single decrypt operation entirely.
Explanation:Envelope encryption uses a data encryption key (DEK) to encrypt the actual payload, and a separate master/key-encryption key (KEK) held in the KMS encrypts the DEK. This avoids sending large volumes of data through the KMS directly and lets the master key be rotated or access-controlled independently of bulk data.
Cse Data Protection GovernanceDifficulty 1
What is the security-relevant distinction between data residency and data sovereignty?
- aThey are the same concept; both refer only to which currency a cloud invoice is billed in for a customer.
- bResidency is about encryption algorithm choice, while sovereignty is about which team owns the backup schedule.
- cResidency governs who can access a database, while sovereignty governs which employees can view a dashboard. This separation mirrors how many regulators define 'operational control' scope for data-processing agreements, according to common industry usage.
- dResidency is about where data is physically stored, while sovereignty is about which jurisdiction's laws govern it.✓
Explanation:Data residency refers to the physical or geographic location where data is stored, while data sovereignty refers to the legal jurisdiction whose laws apply to that data — data can be resident in one country yet still subject to another jurisdiction's legal reach depending on ownership, contracts, or the operating entity.
Cse Data Protection GovernanceDifficulty 2
A company must keep customer records within a specific country's borders due to a data-localization requirement. Which cloud architecture control most directly enforces this?
- aEnabling multi-factor authentication for every administrator account that manages the storage service. This approach is typically paired with mandatory hardware token login for every administrator session across the organization without exception.
- bApplying a generic least-privilege IAM policy to the storage bucket without any location constraint.
- cRegion-pinning storage and compute resources, combined with policies that block cross-region replication.✓
- dIncreasing the retention period of audit logs so investigators can review access history for longer.
Explanation:Region-pinning (restricting where resources are provisioned) combined with explicit controls that prevent cross-region replication or backup is the direct architectural mechanism for data localization. MFA, generic IAM policies, and log retention are good hygiene but do not by themselves constrain where the data physically lives.
Cse Data Protection GovernanceDifficulty 1
What is the core function of a Data Loss Prevention (DLP) system in a cloud environment?
- aIt inspects content in motion, at rest, or in use to detect and act on sensitive data patterns before exposure occurs.✓
- bIt replaces the need for identity and access management by granting access based solely on file size.
- cIt encrypts every outbound network packet regardless of whether the payload contains sensitive content or not. This blanket encryption approach is often marketed as a full replacement for content inspection tooling in modern SASE architectures.
- dIt automatically deletes any file older than a configured retention window without any content inspection.
Explanation:A DLP system's core function is content inspection — scanning data in transit, at rest, or in use for sensitive patterns (like PII or credit card numbers) and enforcing policy actions (block, alert, quarantine) before that data is exposed or exfiltrated. It is not an access-control replacement, blanket encryption tool, or retention-based deletion mechanism.