Which four actions should you take before proceeding with applying updates to your Exadata Database Machine?

Question

Options

• AConsult My Oracle Support note 888828.1 to determine the current recommended Exadata
• BCheck the Exadata Critical Issues My Oracle Support note 1270094.1 for any issues not added to
• CRun exachk and resolve only WARNINGS that you have not seen before.
• DRun the appropriate patchmgr preqequisite check step for each component being updated.
• ERun patchmgr --all_comp --autofix --autobackup --upgrade --rolling.
• FFor database servers, perform a server backup using patchmgr --dbnodes db_list_file --backup --

• A
  83% (19)
• E
  13% (3)
• F
  4% (1)

Explanation

Before patching an Exadata Database Machine, Oracle requires a structured preparation phase: consulting MOS note 888828.1 (A) ensures you're targeting the current recommended software versions; reviewing the Critical Issues note 1270094.1 (B) surfaces known blockers that may not yet appear in patches; running exachk and resolving warnings (C) validates your environment's health pre-patch; and running the patchmgr prerequisite check (D) confirms all components meet patch requirements before any change is made.

Why the distractors are wrong:

• E skips all preparation and immediately runs an upgrade - this is the action you take after completing A–D, not before.
• F is a backup step that belongs in the execution phase, not the pre-check phase (and it's incomplete without the prerequisite checks first).

Memory tip: Think "Check, Check, Run, Run" - two check actions (MOS notes 888828.1 and 1270094.1), then two run actions (exachk health check, patchmgr prereq check). Everything else (autofix, backup, upgrade) belongs to the execution phase that follows.

No community discussion yet for this question.