Which are two correct statements for managing virtual deployment using Oracle Exadata Deployment Assistant (OEDA)?

Question

Options

• AOEDA allows customers to have both bare metal (BM) and virtual machine (VM) in an Exadata
• BThere is no limit on the number of VMs in an Exadata rack as long as the Exadata rack has
• COEDA deployment steps include calibrate cells, create cell disks, and resecure machine.
• DOEDA sets up key-based authentication for the root user by using the setuprootssh.sh utility

• A
  3% (1)
• B
  3% (1)
• C
  94% (29)

Explanation

Options C and D are correct because OEDA's documented deployment workflow explicitly includes steps such as calibrating storage cells, creating cell disks, and resecuring the machine - these are core phases in the OEDA-driven build process. Additionally, OEDA automates SSH key-based authentication setup for the root user across all Exadata nodes via the setuprootssh.sh utility, which is a well-known OEDA security configuration step.

Why A is wrong: OEDA does not support mixing bare metal and VM deployments within the same Exadata rack simultaneously - a rack is configured for one deployment model, not both coexisting.

Why B is wrong: The statement is truncated in the question, but the premise is false; the number of VMs is bounded by physical resources (CPU cores, memory, storage) allocated within the rack, so a hard limit always exists in practice.

Memory tip: Think of OEDA as a Configured Deployment tool - C (Calibrate/Create disks/reseCure = deployment steps) and D (setuprootssh.sh = key-based auth for root). The distractors both make "no limits" or "mix everything" claims, which should be a red flag on any infrastructure exam - Exadata is a controlled, prescriptive platform where limits and separation are by design.

No community discussion yet for this question.