To avoid hard coding passwords in scripts, you have elected to create an external password store- Examine this list of steps: 1. Set the external password store wallet location. ALTER SYSTEM SET…

Question

Options

• A2,1,3,4
• B1,2,5,4
• C1,2,3,6,4
• D1,2,6,3,5
• E2,3,6,4
• F1,2,3,4

• A
  3% (1)
• C
  10% (3)
• D
  83% (24)
• F
  3% (1)

Explanation

Option D (1→2→6→3→5) follows the only logically valid sequence: you must first define where the external store will live (step 1, EXTERNAL_KEYSTORE_CREDENTIAL_LOCATION) before any keystore operations are possible, then connect with SYSKM privileges (step 2), then set the encryption key (step 6) as a prerequisite before secrets can be stored, then add the TDE wallet password as a secret using the ADD SECRET clause (step 3), and finally create the auto-login keystore (step 5) to complete the passwordless setup - no instance restart is required for this workflow.

Why distractors fail:

• A (2,1,3,4): The location parameter (step 1) must be set before connecting as SYSKM (step 2), not after; also skips the encryption key (step 6).
• B (1,2,5,4): Skips both the encryption key (step 6) and the ADD SECRET step (step 3); you cannot create a meaningful auto-login store without first adding a secret.
• C (1,2,3,6,4): Puts ADD SECRET (step 3) before setting the encryption key (step 6), which reverses a hard dependency - the keystore must have an active key before secrets can be added to it.
• E (2,3,6,4): Skips the location setup (step 1) entirely and places ADD SECRET before the encryption key.
• F (1,2,3,4): Skips the encryption key (step 6) and the auto-login creation (step 5), and includes an unnecessary restart.

Memory tip: Use the acronym L-P-K-S-A - Location, Privilege, Key, Secret, Auto-login - to recall steps 1→2→6→3→5 in order.

No community discussion yet for this question.