A z/OS customer is concerned about complying with privacy rules. How is the concept of Pervasive Encryption a potential solution to address the concern?

Question

Options

• AIt is implemented without application or database changes.
• BIt is implemented by only requiring database changes.
• CIt is implemented by requiring application changes.
• DIt is implemented by encrypting only the data at rest.

• A
  89% (24)
• B
  7% (2)
• D
  4% (1)

Explanation

Pervasive Encryption on z/OS is designed to encrypt data transparently across the entire environment - at rest, in flight, and in storage - without requiring any changes to existing applications or databases (A), making it viable for organizations that need broad compliance without costly re-architecture.

• B is wrong because Pervasive Encryption requires no database changes either; it operates below the application and database layer via hardware-accelerated cryptography (IBM's CP Assist for Cryptographic Functions).
• C is wrong for the same reason - the entire value proposition is that application code is untouched; encryption is handled by z/OS system services and storage subsystems transparently.
• D is wrong because Pervasive Encryption covers data in transit as well (e.g., TLS for network communications), not just data at rest - "pervasive" literally means everywhere, not just storage.

Memory tip: Think of "Pervasive" as "invisible" - it encrypts everything behind the scenes, so the answer will always involve no changes to apps or databases. If an answer mentions requiring changes, it contradicts the core definition.

No community discussion yet for this question.