Which two statements are true about the Secure External Password Store (SEPS)?

Question

Options

• APassword credentials are stored on the database server.
• BBypassing database authentication adds significant performance benefits to middle-tier
• CThe database does not need to authenticate the connection because the password credentials are
• DWallet usage secures deployments that rely on password credentials for connecting to databases
• EPassword rotation policies can be enforced without changing application code.

• A
  92% (48)
• B
  2% (1)
• C
  2% (1)
• E
  4% (2)

Explanation

A is correct because SEPS stores encrypted password credentials in an Oracle wallet file on the local file system of the server - credentials live on the server infrastructure itself rather than being hardcoded in application source code or plain-text config files.

D is correct because the Oracle wallet is the core security mechanism of SEPS - it encrypts and protects database connection credentials for any deployment that relies on password-based authentication, which is the primary purpose of the feature.

B is wrong because SEPS does not bypass or skip database authentication, and it offers no performance benefit - it is purely a credential management and security feature, not an optimization.

C is wrong for the same reason: the database still authenticates the connection normally; SEPS only automates secure credential retrieval on the client side so the application doesn't handle raw passwords.

E is wrong in this context because while updating wallet credentials can reduce code changes, SEPS itself doesn't enforce or govern rotation policies - that responsibility belongs to Oracle's password management or audit controls, not SEPS.

Memory tip: Think of SEPS as a safe deposit box on the server - the box (wallet) lives on the server (A) and locks up your passwords (D). It doesn't unlock the database for free (not C/B), and it doesn't write the rotation schedule (not E).

No community discussion yet for this question.