Which two tasks should you perform initially to Implement native network encryption without disrupting client applications?

Question

Options

• AUpgrade all OCI-basod clients to match the database version.
• BSet the server side sqinet.oia parameter sqlnet.encryption_server = requested.
• CConfigure the listener with an endpoint for protocol TCPS.
• DVerify which clients have encrypted connections using the view vSsession_CONNECT_INFO.
• ESet the client side sqinec.ora parameter SQLNET.ENCRYPTION _client = required.
• FSet the server side sqinot.ora parameter SQLNET.CRYPTO_CHECKSOM_SERVER - accepted.
• GModify all JDBC Thin based clients to include network encryption parameters in Java.

• A
  2% (1)
• B
  12% (7)
• C
  73% (43)
• E
  2% (1)
• F
  8% (5)
• G
  3% (2)

Explanation

Note: The question asks for two correct answers, but only "C" is listed - this appears to be an incomplete answer key. Based on Oracle NNE (Native Network Encryption) documentation, the two correct initial steps are likely B and D.

Why B and D are correct: Setting SQLNET.ENCRYPTION_SERVER = REQUESTED (option B) enables the server to negotiate encryption without requiring it - clients without encryption configured can still connect uninterrupted, making it safe for a non-disruptive rollout. Option D (checking V$SESSION_CONNECT_INFO) is the correct first diagnostic step to inventory which clients are already using encrypted connections before enforcing a policy.

Why C is wrong: TCPS configures the listener to use SSL/TLS certificates - a different encryption mechanism from Oracle NNE. TCPS requires clients to update their connection strings from TCP to TCPS, which would disrupt existing applications.

Why the others are wrong:

• A & G both require modifying clients - directly contradicting the "without disrupting" requirement.
• E sets the client side to REQUIRED, which would break connections to servers not yet configured for encryption.
• F (CRYPTO_CHECKSUM_SERVER = ACCEPTED) addresses data integrity checksums, not encryption - a related but separate feature.

Memory tip: The key word is "requested" vs. "required" - REQUESTED means "I'd like encryption but won't insist," letting you phase in NNE safely. Think: Request before Require.

No community discussion yet for this question.