For Exadata systems, hardware monitoring for components like the motherboard, memory, power, fans, and network cards on the database nodes is managed through the Integrated Lights Out Manager (ILOM). The ILOM provides built-in thresholds and sensor readings that are automatically recognized by Oracle Enterprise Manager.
These thresholds and alerts are already configured within ILOM for Exadata components, ensuring seamless integration with Enterprise Manager for alerting and monitoring purposes.
Enterprise Manager uses these pre-set ILOM thresholds and does not require additional configuration for monitoring hardware components. Therefore, administrators benefit from preset alerting mechanisms that are sufficient for comprehensive hardware status visibility.

Your customer needs to ensure that their data is available on the Exadata machine during updates. The customer wants to be able to update one server at a time but still be protected against single-node server failure. This means that they need a redundancy level that can tolerate at least one disk failure without losing data availability or performance. Therefore, the best option for them is normal redundancy . Normal redundancy provides two-way mirroring by default, which means that each data extent has a primary copy and a mirror copy on different disks in different failure groups1. A failure group is a subset of disks within a disk group that are likely to fail at the same time due to common dependencies2. On Exadata Database Machine , each Storage Server is considered as a failure group by default2. This means that if one Storage Server fails or needs to be updated , the data on its disks can still be accessed from another Storage Server that has the mirror copies of the same data extents2. Therefore, normal redundancy ensures data availability and performance during updates or single-node server failures.
https://docs.oracle.com/en/engineered-systems/exadata-database-machine/sagug/exadata-administering-asm.html

On Oracle Exadata Database Machine X9M, the default configuration of the IPTables firewall varies between storage servers and database servers:
Storage Servers: After initial deployment, IPTables is installed but remains in an unconfigured and inactive state. The Exadata storage servers focus on providing high availability and performance for database workloads and thus rely on internal security measures. The external firewall or network security policies typically handle firewall responsibilities, so IPTables is not actively configured on these servers by default.
Database Servers: Similar to storage servers, IPTables is also installed but neither configured nor running on the database servers. The Oracle Exadata Database Machine X9M emphasizes security through other means, such as its network isolation and dedicated interconnects. As part of Oracle's engineered systems design philosophy, the database servers are primarily focused on database performance, offloading much of the security management to other parts of the infrastructure and relying on data center-level firewalls for perimeter security.
To summarize, both database and storage servers have IPTables installed and available, but they are not configured or running by default on either server type. This setup allows Exadata environments to focus on optimized database performance while integrating with external network security solutions.

According to the Oracle Exadata Database Machine documentation12, two recommended configuration best practices for backup and recovery on Exadata are:
A) Placing the backup network on dedicated switches installed in the top of the rack (ToR) has the benefits of isolating the backup network from other workloads and providing a greater level of control.
D) When off-site long-term backup retention is needed, use Oracle Database Backup Cloud Service as a low-cost, offsite scalable storage for a disaster recovery solution.

Your customer needs to ensure that their data is available on the Exadata machine during updates. The customer wants to be able to update one server at a time but still be protected against single-node server failure. This means that they need a redundancy level that can tolerate at least one disk failure without losing data availability or performance. Therefore, the best option for them is normal redundancy . Normal redundancy provides two-way mirroring by default, which means that each data extent has a primary copy and a mirror copy on different disks in different failure groups1. A failure group is a subset of disks within a disk group that are likely to fail at the same time due to common dependencies2. On Exadata Database Machine , each Storage Server is considered as a failure group by default2. This means that if one Storage Server fails or needs to be updated , the data on its disks can still be accessed from another Storage Server that has the mirror copies of the same data extents2. Therefore, normal redundancy ensures data availability and performance during updates or single-node server failures.
https://docs.oracle.com/en/engineered-systems/exadata-database-machine/sagug/exadata-administering-asm.html