C++ Multiple Choice Questions Page 13 of 14

Home » C++ » MCQs

Showing Page 13 (241 - 260)

Question: 241


(A) True
(B) False



Level: Practitioner
Category of MCQ: exceptions in C++

Question: 242


(A) Function declaration has error
(B) Behaviour is unknown
(C) Function will throw only standard exceptions defined in <exception>
(D) Function will not throw any exception



Level: Practitioner
Category of MCQ: exceptions in C++

Question: 243


(A) True
(B) False



Level: Beginner
Category of MCQ: loops in C++

Question: 244


(A) 100
(B) 0
(C) Compilation Error
(D) Garbage Value is printed



Level: Expert
Category of MCQ: inheritance in C++

Question: 245


(A) Equal
(B) EqualEqual
(C) EqualNotEqual
(D) NotEqual



Level: Practitioner
Category of MCQ: conditional in C++

Question: 246


(A) Yes
(B) No



Level: Beginner
Category of MCQ: namespace in C++

Question: 247


(A) Before all #include
(B) After #include<iostream>
(C) In middle of #includes
(D) After all #inludes



Level: Beginner
Category of MCQ: namespace in C++

Question: 248


(A) Using the entire namespace, using only single name from namespace
(B) There is no difference
(C) We can't use only cout from std namespace



Level: Beginner
Category of MCQ: namespace in C++

Question: 249


(A) Runtime Error
(B) Compilation Erro
(C) Nothing is printed
(D) CppBuzz.com



Level: Beginner
Category of MCQ: namespace in C++

Question: 250


(A) Program is terminated without printing anything on console
(B) Prints 'constructor' and then it is terminated
(C) constructor.destructor. but ptr is never freed
(D) constructor.destructor. And ptr is freed



Level: Practitioner
Category of MCQ: pointers in C++

Question: 251


(A) C++11's weak_ptrs are used with shared_ptrs.
(B) C++11's weak_ptrs can be used without weak_ptrs
(C) C++11's weak_ptrs are replacement of unique_ptr
(D) C++11's weak_ptrs are used for unique ownership



Level: Practitioner
Category of MCQ: pointers in C++

Question: 252


(A) We can only use these smart pointers to refer to objects allocated with new
(B) It is recommended that you do not use both 2 shared_ptr and raw pointer on the same object
(C) It can't be copied or assigned to another shared_ptr
(D) We can also reset a shared_ptr by assigning it the value nullptr



Level: Practitioner
Category of MCQ: pointers in C++

Question: 253


(A) This is valid code snippet with no error
(B) Error: Copy construction is not allowed at line 2
(C) Error: Assignment is not allowed at line 2
(D) Error: Runtime exception



Level: Practitioner
Category of MCQ: pointers in C++

Question: 254


(A) We can't transfer the ownership of unique pointers
(B) It is possible using copy constructor - unique_ptr<Thing> ptr2(ptr1);
(C) ptr2 = std::move(ptr1);
(D) ptr2 = ptr1



Level: Expert
Category of MCQ: pointers in C++

Question: 255


(A) Address of memory allocated | Garbage Value
(B) Address of memory allocated | 0
(C) Address of ptr | 0
(D) Address of ptr | Garbage Value



Level: Beginner
Category of MCQ: new_delete in C++

Question: 256


(A) Program runs without any error
(B) Compilation Error
(C) Runtime error (Segmentation fault)
(D) None of the above



Level: Beginner
Category of MCQ: new_delete in C++

Question: 257


(A) bad_exception
(B) overflow_error
(C) out_of_range
(D) bad_alloc



Level: Practitioner
Category of MCQ: new_delete in C++

Question: 258


(A) 08
(B) 04
(C) 84
(D) 48



Level: Practitioner
Category of MCQ: inheritance in C++

Question: 259


(A) base
(B) Nothing is printed
(C) basebase
(D) None of the Above



Level: Practitioner
Category of MCQ: inheritance in C++

Question: 260


(A) Hello Derived
(B) Hello Base
(C) Hello Derived Hello Base
(D) Hello Base Hello Derived



Level: Practitioner
Category of MCQ: typecasting in C++

Browse By Categories


MCQs

About Us | Contact Us | Privacy Policy | Career  | Online Training
Youtube   LinkedIn   Facebook   Twitter   Instagram  
Copyright©CppBuzz.com
Like many websites, we use cookies to ensure best browsing experience on our website. While using this website, you acknowledge to have read and accepted our cookie and privacy policy.