Default Service PDB RAC Creation

Why the Answer Is Correct

The default service created for a PDB behaves differently than the database-level services in terms of automation and registry management. Statement B is correct because the default service does not have the necessary attributes set to allow Clusterware to automatically open the PDB; manual intervention or explicit configuration is required. Statement E is correct because the default service is not automatically registered in the Oracle Cluster Registry (OCR). While it registers with the local listeners on the instance where it is running, it does not appear as a managed resource in the OCR by default.

Why the Other Options Are Wrong

Option A is incorrect because the availability of the service depends on the configuration (administered vs policy-managed) and whether the PDB is open on that specific instance. Option C is incorrect because, as noted, automatic registration in OCR does not happen for the default PDB service without specific commands like srvctl modify service or enable. Option D is misleading; while policy-managed databases distribute resources, the key distinction tested here is the lack of OCR registration and automation capability, making E and B the definitive technical truths.

Community Comment Notes

Community consensus strongly supports options B and E. Users note that for OCR registration, you typically need to run srvctl commands explicitly, confirming that it is not automatic. One commenter verified the documentation stating that the default service lacks the automation capabilities for opening the PDB, reinforcing option B.