OMG (Object Management Group) -OCRES - Advanced - UM0-411 Set 2

Thread ✘ Distributed Thread ✘ Schedulable Thread ✘ Distributable Thread ✔

RTCorba ✘ RTCORBA ✘ RTScheduling ✘ RTDynScheduling ✔ RTDynamicScheduling ✔

A ClientProtocolPolicy can only be set at the client-side. ✘ A ClientProtocolPolicy can be set on either the client or server side. ✘ A ClientProtocolPolicy that matches one of the target's available protocols (if published in its IOR) must be provided for a successful binding. ✘ If the ORB fails to make a connection because none of the protocols is available on the client, a COMM_FAILURE system exception is raised. ✔

It is defined by a CLIENT_PROTOCOL_POLICY_TYPE 48. ✘ It is used to establish allowable binding protocols in order of preference. ✘ It raises a COMM_FAILURE system exception if set on both client and server sides. ✘ It is used to check for availability of proper protocols on the client ORB before attempting a connection. ✔

ORB level only ✘ ORB and POA level ✘ Root POA level only ✘ POA and Object level ✔

maximum laxity first ✘ earliest deadline first ✘ minimize accrued utility ✘ rate monotonic analysis ✔

Set policies on the server side at POA creation time and allow per connection changes later. ✘ Set policies on the client side at object bind time and adjust later if the protocol is specified as configurable. ✘ Set policies at POA creation time on the client side or object bind time on the server side and permit no changes. ✘ Set policies at POA creation time on the server side or object bind time on the client side and permit no changes. ✔

"Least Laxity First" requires the knowledge of estimated execution time for each thread. ✘ "Fixed Priority" is the only scheduling discipline that allows hard real time requirements to be met. ✘ "Earliest Deadline First" only satisfies the soft real-time criterion minimize number of missed deadlines". ✘ "Maximum Accrued Utility" associates a utility function with each thread in order to create a dispatching rule. ✔

INV_POLICY ✘ BAD_PARAM ✘ BAD_OPERATION ✘ NO_RESOURCES ✔

It defines how different scheduling disciplines may interoperate. ✘ It defines mapping rules from scheduling parameters to RTOS primitives. ✘ It specifies interfaces that will allow the development of scheduler-independent applications. ✘ It defines a set of ORB/scheduler interfaces that will allow the development of ORB-independent schedulers. ✔