Oracle Enterprise Manager and Service Console are two tools that can be used to monitor Exadata Database Service. Oracle Enterprise Manager is a comprehensive management solution that provides a single interface for monitoring and managing all Exadata, ExaDB-D and ExaDB-C@C systems, along with any other targets1. Oracle Enterprise Manager enables you to visualize storage and compute data, view performance metrics of your Exadata components, and perform administrative tasks such as patching, backup, and recovery1. Service Console is a web-based user interface that allows you to monitor and manage your Exadata Cloud Service instances2. Service Console provides information about the status, configuration, and utilization of your Exadata systems, and enables you to perform operations such as scaling, patching, backup, and restore2.

The other options are not valid tools for monitoring Exadata Database Service because:

• B. Oracle Management Cloud is a suite of cloud services that provides integrated monitoring, management, and analytics for applications, databases, middleware, and infrastructure3. Oracle Management Cloud is not specific to Exadata Database Service, and does not provide the same level of functionality and integration as Oracle Enterprise Manager4.
• C. Oracle Cloud Monitor is not a real tool, but a fictitious name. There is no such tool as Oracle Cloud Monitor in Oracle Cloud Infrastructure or Oracle Cloud Services.
• D. Oracle Internet Monitoring Suite (IMS) is also not a real tool, but a fictitious name. There is no such tool as Oracle Internet Monitoring Suite in Oracle Cloud Infrastructure or Oracle Cloud Services.

To manage an external database using the Oracle Cloud Infrastructure Database Management Service, you must create or configure a database handle and a database connection1. A database handle is a resource that represents an external database in Oracle Cloud Infrastructure2. It contains information such as the database name, version, edition, and deployment type. A database connection is a resource that enables you to connect a database handle to an Oracle Database instance located outside of Oracle Cloud Infrastructure3. It contains information such as the host name, port number, service name, and credentials. You can create and manage database handles and connections using the Oracle Cloud Infrastructure Console or the REST API23.

A is incorrect, because a dynamic group is not required to manage an external database. A dynamic group is a group of Oracle Cloud Infrastructure resources that are dynamically matched according to rules that you define4. You can use a dynamic group to grant permissions to the Database Management agent, which is a software component that runs on the host where the external database is located and communicates with the Database Management service5. However, creating a dynamic group is not mandatory, as you can also use other methods to grant permissions to the agent, such as using a user API key or an instance principal5.

C is incorrect, because a database group is not required to manage an external database. A database group is a logical grouping of databases that you can use to perform actions on multiple databases at once. You can create a database group for external databases, but it is not a prerequisite for managing them.

References: 1: About Database Management 2: Manage the Handles for External Database 3: Manage the Connections for External Database 4: Managing Dynamic Groups 5: About Database Management Agent : Managing Database Groups

 To perform actions on a NoSQL table, such as creating, updating, deleting, or querying rows, you need to have the appropriate permissions granted by an IAM policy. The permissions are defined by the combination of the verb and the resource type. For example, the NOSQL_TABLE_WRITE permission allows you to create or update a table, and the NOSQL_ROWS_INSERT permission allows you to insert rows into a table1.

The other options are not correct permissions to perform actions on a NoSQL table. The NOSQL_ROWS_READ and NOSQL_ROWS_DELETE permissions only allow you to read or delete rows from a table, but not to insert or update them1. The NOSQL_TABLE_INSPECT and NOSQL_TABLE_UPDATE permissions only allow you to list or modify the properties of a table, but not to create or delete it1. The NOSQL_TABLE_DESTROY and NOSQL_TABLE_ALTER permissions only allow you to drop or alter a table, but not to create or update it1. References:

• Oracle NoSQL Database Cloud Service Policies Reference