PCPP-32-101 Practice Exam Questions with Answers PCPP1 – Certified Professional in Python Programming 1 Certification

The correct answers are A. An attribute owned by every exception object and D. An attribute that holds interesting information that is particularly useful when the programmer wants to store exception details in other objects. A traceback is an attribute of an exception object that contains a stack trace representing the call stack at the point where the exception was raised. The traceback attribute holds information about the sequence of function calls that led to the exception, which can be useful for debugging and error reporting.

In the given code snippet, an instance of OwnMath exception is raised with an explicitly specified __cause__ attribute that refers to the original exception (ZeroDivisionError). This is an example of explicitly chaining exceptions in Python.

If the main window is too small to fit all its widgets, some widgets may be invisible. So, the correct answer is Option A.

When a window is not large enough to display all of its content, some widgets may be partially or completely hidden. The window will not automatically expand to fit all of its content, and no exception will be raised. The widgets will not be automatically scaled down to fit the window’s size.

If the main window is too small to fit all its widgets, some of the widgets may not be visible or may be partially visible. This is because the main window has a fixed size, and if there are more widgets than can fit within that size, some of them will be outside the visible area of the window.

To avoid this issue, you can use layout managers such as grid, pack, or place to dynamically adjust the size and position of the widgets as the window changes size. This will ensure that all the widgets remain visible and properly arranged regardless of the size of the main window.

References:

• https://www.tkdocs.com/tutorial/widgets.html#managers
• https://www.geeksforgeeks.org/python-tkinter-widgets/
• https://anzeljg.github.io/rin2/book2/2405/docs/tkinter/introduction.html

According to PEP 8 recommendations, the two best options are Option B and Option D.

Option B follows PEP 8’s suggestion that all lines should be limited to 79 characters and for longer blocks of text like docstrings or comments, the length should be limited to 72 characters1. Option D follows PEP 8’s conventions for writing good documentation strings (a.k.a. “docstrings”) which are immortalized in PEP 257. It suggests writing docstrings for all public modules, functions, classes, and methods2.

The cget() method in Python is used to read the configuration options of a widget in Tkinter. It retrieves the value of a specified configuration option for a Tkinter widget. Hence, option A is the correct answer.

ConfigParser is a built-in library in Python that allows you to read and write configuration files. The read method is used to read the configuration file which can be in any of the supported file formats, such as INI, YAML, and JSON. The read_dict method is used to read the configuration from a Python dictionary. The read_conf and read_str options are not valid methods in the ConfigParser module.

Therefore, the correct options to load a configuration using ConfigParser are A. read and D. read_string.

The unbind_all() method in Tkinter is used to remove all event bindings from a widget. It is a method of the widget object and can be called on any widget in the Tkinter application. Therefore, option A is the correct answer.

Option B is incorrect because the method can be called on any widget, not just the main window widget.

Option C is correct as unbind_all() does not take any parameters.

Option D is incorrect because the method only removes event bindings and does not cause the widgets to disappear.

So, the correct answers are A and C.

References:

• Tkinter documentation: https://docs.python.org/3/library/tkinter.html#event-bindings
• Tkinter tutorial: https://www.python-course.eu/tkinter_events_binds.php

The true statement related to PEP 257 is Option B. According to PEP 257, string literals occurring elsewhere in Python code may also act as documentation. They are not recognized by the Python bytecode compiler and are not accessible as runtime object attributes (i.e. not assigned to doc), but two types of extra docstrings may be extracted by software tools: String literals occurring immediately after a simple assignment at the top level of a module, class, or init method are called “attribute docstrings”. String literals occurring immediately after another docstring are called “additional docstrings”1.