Policy-Managed RAC Singleton Service Failover
You administer a six-instance, policy-managed, multitenant RAC database CDB1 with three PDBs: PDB_1,PDB_2, and PDB_3. Server pool prod_pool has a cardinality of three and all six hosts of the cluster are up. Examine these commands executed on HOST01: Which two statements are true regarding the AR service? (Choose two.) - 
Community Votes
67% of anonymous learners picked answer AC. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
This question tests singleton service behavior in policy-managed RAC and the trap of assuming all CDB1 instances belong to prod_pool.
In a six-instance policy-managed RAC database, the AR service is created in server pool prod_pool with cardinality 3, making it a singleton service. This page establishes that AR can fail over only to another instance within prod_pool and runs on exactly one instance at a time, so the correct statements are C and E.
Many learners choose A, believing AR can fail over to any of the six CDB1 instances, but the server pool contains only three of them, so singleton failover is limited to prod_pool.
Community Discussion (5 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The AR service is a singleton service in the policy-managed server pool prod_pool (cardinality 3). A singleton service runs on exactly one instance in its server pool at any given time, so statement E is true. If that instance fails, Oracle Clusterware can relocate the service to another available instance within prod_pool; since CDB1 has six instances but only three are in prod_pool, the failover target must be one of those three. Thus statement C is also true. A singleton service does not run on multiple instances simultaneously, so B is false.Why the Other Options Are Wrong
Statement A is false because CDB1 is a six-instance database, yet prod_pool has cardinality 3, meaning only three instances are members of the pool. A failover target must be in the same server pool, so AR cannot fail over to any of the six CDB1 instances. Statement B is false because a singleton service is not available on every instance in the pool; it runs on one instance. Statement D is false because AR is not tied to HOST01; it can be relocated to another instance in prod_pool if the current instance fails or is stopped. The commands executed on HOST01 create the service but do not pin it permanently to that host.Community Comment Notes
As Jaroslav113 noted, "all the instances are not in the prod_pool" — only three of the six CDB1 instances are there, which invalidates option A. jackhsu0704 also identified the service as a singleton and selected C and E, matching the service's one-instance-at-a-time behavior. krwi1 voted AC by assuming every CDB1 instance runs in prod_pool, but that contradicts the six-instance count versus cardinality of three. The AC vote majority likely stems from this same misconception, while the CE reasoning aligns with Oracle's policy-managed service model.Official Reference
Exam Strategy
In policy-managed RAC questions, always check the server pool cardinality versus the total number of database instances. Then determine the service cardinality (SINGLETON vs UNIFORM); a singleton is confined to its pool and runs on one instance at a time.
Frequently Asked Questions
Why can AR not fail over to any available CDB1 instance?
Because CDB1 has six instances, but prod_pool has cardinality 3, so only three instances are in the pool; a singleton service is restricted to its server pool.
What does singleton mean for the AR service in prod_pool?
Singleton means AR runs on exactly one instance in prod_pool at a time and can fail over to another instance within that same pool.