OMG-OCRES-I200 無料問題集「OMG-Certified Real-time and Embedded Systems Specialist Intermediate」

（A）Memory fragmentation does not occur.

（B）Tasks must inform the run-time (e.g., operating system) the total amount of memory they will need
before they begin requesting memory.

（C）Garbage collection is not required.

（D）Memory allocation units are always the same fixed size.

（A）because the application is being developed on a POSIX-compliant Windows system, so debugging is
easy

（B）to meet the tight memory requirements of a small embedded processor

（C）because the POSIX interfaces guarantee meeting application time constraints

（D）to enhance the probability that the application could be moved to other platforms

（A）is the aggregation of all Transformation Specification Elements

（B）is one entry in a Transformation Specification

（C）provides a record of the inverse mapping transformation used to recover a model

（D）traces groups of input model items to the groups of model items into which they are transformed

（A）Application specification

（B）Data model specification

（C）Service specification

（D）Language specification

（A）loadAverage

（B）Utilization

（C）numThreads

（D）scheduler

（A）RT CORBA Current and RT Thread Scheduling

（B）RT CORBA and RT Portable Server

（C）RT CORBA Mutexes and RT Priority Inheritance

（D）RT CORBA Priority and RT Priority Mappings

（A）respecting thread priorities between CORBA clients and servers

（B）minimizing the latencies of operation invocations

（C）bounding the duration of thread priority inversions during end-to-end processing

（D）bounding the duration of memory access times

（A）Individual systems cannot mix CORBA/e and non-CORBA/e ORBs.

（B）Applications written for a CORBA/e ORB will run without modification on a non-CORBA/e ORB.

（C）CORBA/e ORBs in a system with non-CORBA/e ORBs will cause the entire system to behave in a
real-time manner.

（D）CORBA/e systems can successfully interoperate with non-CORBA/e CORBA systems.

（A）static_threads

（B）dynamic_threads

（C）allow_request_buffering

（D）stacksize

（A）determine the optimal scheduling for an application running on a particular RTOS

（B）define the RTOS worst case response time for each interface

（C）measure the RTOS features most suitable for an application that must meet real-time requirements

（D）measure the RTOS overall API overhead