問題文
A client team plans to reach an Exadata Database in OD@GCP over TCPS and has therefore configured its Oracle Net client to reject native encryption. The architect is asked what the server side does with such a client, and what TCPS asks of the client. What is the documented behavior?
選択肢
- The server side treats native encryption as optional and leaves the integrity check aside, so such a client reaches the database over an unencrypted channel, while TCPS asks the client for a certificate that the client's own certificate authority issues.
- The server side turns such a client away and offers it the TCPS port instead, so the attempt ends in an error until the client holds the entry for that service in its own local names file, and TCPS reads the file rather than the downloadable wallet.
- The server side requests native encryption and accepts the integrity check by default, so a connection attempt from such a client ends in an error, while TCPS asks the client for the downloadable connection wallet that carries the handshake.
- The server side asks for the integrity check and leaves the encryption to the client's own choice, so such a client reaches the database with the checksum in place, while TCPS asks the client for the same wallet that the database backups use.