Advanced Perl test (Advanced)

Sample questions

5 sample questions from the Advanced Perl test, with the answers. Samples are taken out of the live test, so you will not meet these when you sit it.

1. Which statement accurately compares Moose type constraints with traditional Perl validation methods?

   1. Moose type constraints are slower than traditional Perl validation methods and should be avoided in performance-critical applications.
   2. Moose type constraints and traditional Perl validation methods are functionally identical and offer no advantages over one another.
   3. Moose type constraints allow for precise validation of attribute values, while traditional Perl validation using regular expressions or custom subroutines can be error-prone and less maintainable.
   4. Moose type constraints are not compatible with older Perl versions and require significant boilerplate code for setup.

   Answer: C. Moose type constraints allow for precise validation of attribute values, while traditional Perl validation using regular expressions or custom subroutines can be error-prone and less maintainable.

   Moose type constraints provide a declarative and robust way to enforce data integrity, making code more readable and maintainable. Traditional Perl validation methods, such as using regular expressions or custom subroutines, are more verbose and can lead to inconsistencies or errors if not carefully implemented.

2. What is a key feature of Test::TempDir when managing temporary directories during testing?

   1. Test::TempDir does not support nested temporary directories.
   2. Test::TempDir automatically cleans up the temporary directory and its contents after the test completes, even if the test fails.
   3. Test::TempDir requires manual cleanup of temporary directories and files after each test.
   4. Test::TempDir only creates temporary files, not directories.

   Answer: B. Test::TempDir automatically cleans up the temporary directory and its contents after the test completes, even if the test fails.

   Test::TempDir is designed to create temporary directories that are automatically cleaned up after the test finishes, ensuring that no leftover files or directories are left on the system. This behavior is crucial for maintaining a clean testing environment and preventing test pollution. The other options incorrectly describe the functionality or are not relevant to the primary purpose of Test::TempDir.

3. What is the primary behavior of Test::TempDir with respect to temporary directory management during tests?

   1. Test::TempDir creates temporary directories that persist across test runs for performance optimization.
   2. Test::TempDir does not support directory creation and is only used for file-based temporary storage.
   3. Test::TempDir only creates temporary directories manually and requires the user to clean them up after each test.
   4. Test::TempDir creates temporary directories that are automatically cleaned up after tests finish, ensuring no leftover files.

   Answer: D. Test::TempDir creates temporary directories that are automatically cleaned up after tests finish, ensuring no leftover files.

   Test::TempDir is designed to create temporary directories during testing that are automatically removed once the tests are complete. This ensures that no temporary files or directories are left behind, which is crucial for maintaining a clean test environment and avoiding conflicts between test runs. Other options may describe unrelated features or incorrect behavior.

4. Which of the following is the most efficient and idiomatic Perl one-liner for parsing a log file and printing only lines containing the word 'ERROR'?

   1. Using a full Perl script with File::Slurp
   2. Using grep with a complex regular expression
   3. Using a Python script with the logging module
   4. perl -ne 'print if /ERROR/' log

   Answer: D. perl -ne 'print if /ERROR/' log

   The `perl -ne 'print if /ERROR/' log` command is a one-liner that efficiently processes a log file line by line, filtering and printing only lines that contain the word 'ERROR'. This is a common and effective method for quick log parsing in Perl. In contrast, using a full script with modules like `File::Slurp` or `Log::Log4perl` may be overkill for simple tasks, while tools like `grep` or `awk` may lack the flexibility of Perl's powerful regular expressions and in-line processing capabilities.

5. What is the difference between Test::Output and Test::More's is() when it comes to capturing and comparing output in Perl testing?

   1. Test::Output and Test::More's is() both capture output by redirecting STDOUT and STDERR, but Test::More's is() is more efficient for large outputs.
   2. Test::Output is used for capturing output, but Test::More's is() is not suitable for dynamic output and should be avoided for large outputs.
   3. Test::Output captures output by redirecting STDOUT and STDERR, while Test::More's is() compares strings directly and is better for small, static output checks.
   4. Test::Output is better for capturing large dynamic output, while Test::More's is() is suitable for small static output and handles redirection automatically.

   Answer: C. Test::Output captures output by redirecting STDOUT and STDERR, while Test::More's is() compares strings directly and is better for small, static output checks.

   Test::Output is designed to capture and test output from programs, which is useful for testing scripts that produce dynamic or large amounts of output. On the other hand, Test::More's is() function is more suitable for small, static output checks because it compares strings directly and is simpler to use for straightforward cases.