Two distinct types of problems can arise while an iOS or OS X application is running. Exceptions represent programmer-level bugs like trying to access an array element that doesn’t exist. They are designed to inform the developer that an unexpected condition occurred. Since they usually result in the program crashing, exceptions should rarely occur in your production code. On the other hand, errors are user-level issues like trying load a file that doesn’t exist. Because errors are expected during the normal execution of a program, you should manually check for these kinds of conditions and inform the user when they occur. Most of the time, they should not cause your application to crash. Is the statement above correct ?

In Objective-C programming, error handling is provided with (...) class available in Foundation framework.

(...) is an abstractClass which represents a stream of data. They are used in Archiving and Unarchiving objects. (...) objects are usually used in a method that is being implemented so that the class conforms to the protocol.

The (...) method can be used to see if an object belongs to a class that implements a particular protocol.

In Objective-C, retain counts are the way in which memory is managed in Objective-C

A derived class can access all the private members of its base class if it's defined in the interface class

What is true regarding messaging?

Which of the following is the fastest?

A class can have two methods with the same name, but with different argument types.

Why should you use an autorelease pool ?

Which of the following statements is correct?