Bird
Raised Fist0
Rubyprogramming~20 mins

File.open with block (auto-close) in Ruby - Practice Problems & Coding Challenges

Choose your learning style10 modes available
Challenge - 5 Problems
🎖️
File Handling Mastery
Get all challenges correct to earn this badge!
Test your skills under time pressure!
❓ Predict Output
intermediate
2:00remaining
What is the output of this Ruby code using File.open with a block?

Consider the following Ruby code snippet:

File.open("test.txt", "w") do |file|
  file.puts "Hello, world!"
end
puts File.exist?("test.txt")

What will be printed when this code runs?

Ruby
File.open("test.txt", "w") do |file|
  file.puts "Hello, world!"
end
puts File.exist?("test.txt")
Anil
Btrue
Cfalse
DAn error is raised
Attempts:
2 left
💡 Hint

Think about whether the file is created and closed properly after the block.

❓ Predict Output
intermediate
2:00remaining
What does this code print when reading a file with File.open and a block?

Given a file "data.txt" containing the text "Ruby Rocks!", what will this code output?

File.open("data.txt", "r") do |file|
  puts file.read
end
Ruby
File.open("data.txt", "r") do |file|
  puts file.read
end
AAn error is raised
BAn empty line
CRuby Rocks!
Dnil
Attempts:
2 left
💡 Hint

Remember that file.read reads the entire content of the file.

❓ Predict Output
advanced
2:00remaining
What error does this code raise when using File.open without a block but forgetting to close?

What happens when you run this Ruby code?

file = File.open("example.txt", "w")
file.puts "Hello"
# No file.close called
Ruby
file = File.open("example.txt", "w")
file.puts "Hello"
AIOError: not closed
BRuntimeError: closed stream
CSyntaxError
DNo error, but file remains open until program ends
Attempts:
2 left
💡 Hint

Think about what happens if you don't explicitly close a file in Ruby.

🧠 Conceptual
advanced
1:30remaining
Why is using File.open with a block preferred over without a block?

Which of the following is the main advantage of using File.open with a block?

AIt automatically closes the file after the block finishes
BIt speeds up file reading
CIt prevents any errors from occurring
DIt makes the file read-only
Attempts:
2 left
💡 Hint

Think about resource management and safety.

❓ Predict Output
expert
2:30remaining
What is the output of this Ruby code using File.open with a block and exception handling?

Consider this Ruby code:

begin
  File.open("missing.txt", "r") do |file|
    puts file.read
  end
rescue Errno::ENOENT
  puts "File not found"
end

What will be printed when this code runs and the file "missing.txt" does not exist?

Ruby
begin
  File.open("missing.txt", "r") do |file|
    puts file.read
  end
rescue Errno::ENOENT
  puts "File not found"
end
AFile not found
Bnil
CAn unhandled exception is raised
DAn empty line
Attempts:
2 left
💡 Hint

Think about how exceptions are handled in Ruby.

Practice

(1/5)
1. What happens to the file after the block finishes when you use File.open('file.txt') do |f| ... end in Ruby?
easy
A. The file remains open until you manually close it.
B. The file is automatically closed after the block ends.
C. The file is deleted after the block ends.
D. The file is locked and cannot be accessed again.

Solution

  1. Step 1: Understand File.open with block behavior

    When you open a file with a block, Ruby automatically manages the file resource.
  2. Step 2: Recognize automatic closing

    After the block finishes, Ruby closes the file automatically to prevent resource leaks.
  3. Final Answer:

    The file is automatically closed after the block ends. -> Option B
  4. Quick Check:

    File.open with block = auto-close [OK]
Hint: File.open with block always auto-closes the file [OK]
Common Mistakes:
  • Thinking the file stays open after the block
  • Assuming the file is deleted automatically
  • Believing the file locks after block ends
2. Which of the following is the correct syntax to open a file named data.txt for reading using a block in Ruby?
easy
A. File.open('data.txt') |file| puts file.read end
B. File.open('data.txt') puts file.read end
C. File.open('data.txt') { |file| puts file.read }
D. File.open('data.txt') do puts file.read end

Solution

  1. Step 1: Identify correct block syntax

    Ruby uses either curly braces or do...end with a block parameter like |file|.
  2. Step 2: Check each option

    File.open('data.txt') { |file| puts file.read } correctly uses { |file| ... }. Others have syntax errors or missing block parameters.
  3. Final Answer:

    File.open('data.txt') { |file| puts file.read } -> Option C
  4. Quick Check:

    Correct block syntax = File.open('data.txt') { |file| puts file.read } [OK]
Hint: Use {|var| ...} or do |var| ... end for blocks [OK]
Common Mistakes:
  • Missing block parameter |file|
  • Incorrect block delimiters
  • Omitting do or braces
3. What will be the output of this Ruby code?
File.open('test.txt', 'w') do |f|
  f.puts 'Hello'
end

content = File.read('test.txt')
puts content
medium
A. Hello
B. test.txt
C. nil
D. Error: file not found

Solution

  1. Step 1: Write 'Hello' to file inside block

    The block writes the string 'Hello' followed by a newline to 'test.txt'.
  2. Step 2: Read and print file content

    After the block, the file is closed automatically. Then File.read reads the content, which is 'Hello\n'. Printing it outputs 'Hello'.
  3. Final Answer:

    Hello -> Option A
  4. Quick Check:

    File.write + read = Hello [OK]
Hint: File.open with block writes and auto-closes file [OK]
Common Mistakes:
  • Expecting file to be empty
  • Thinking file is not saved before reading
  • Confusing file name with content
4. Identify the error in this Ruby code snippet:
file = File.open('log.txt', 'w') do |f|
  f.puts 'Log entry'
end
file.puts 'Another entry'
medium
A. file is nil because File.open with block returns the block's value, not the file object.
B. The file is not opened in write mode.
C. Missing block parameter |f| in File.open.
D. File is not closed automatically.

Solution

  1. Step 1: Understand return value of File.open with block

    When using a block, File.open returns the block's last expression, not the file object.
  2. Step 2: Analyze variable 'file'

    Here, 'file' is assigned the block's return value, which is nil because f.puts returns nil. So calling file.puts causes an error.
  3. Final Answer:

    file is nil because File.open with block returns the block's value, not the file object. -> Option A
  4. Quick Check:

    File.open block returns block value, not file [OK]
Hint: File.open with block returns block result, not file object [OK]
Common Mistakes:
  • Expecting File.open with block to return file object
  • Trying to use file after block ends
  • Ignoring file mode argument
5. You want to read a file and count how many lines contain the word 'error'. Which Ruby code correctly uses File.open with a block to do this safely?
hard
A. count = 0 File.open('log.txt') { |f| f.each { |line| count += 1 if line.include?('error') } } puts count
B. count = 0 f = File.open('log.txt', 'r') f.each_line { |line| count += 1 if line.include?('error') } f.close puts count
C. count = 0 File.open('log.txt', 'r') do each_line { |line| count += 1 if line.include?('error') } end puts count
D. count = 0 File.open('log.txt', 'r') do |f| f.each_line { |line| count += 1 if line.include?('error') } end puts count

Solution

  1. Step 1: Use File.open with block and read lines

    count = 0 File.open('log.txt', 'r') do |f| f.each_line { |line| count += 1 if line.include?('error') } end puts count opens the file with a block and iterates each line safely.
  2. Step 2: Count lines containing 'error'

    Inside the block, it increments count if the line includes 'error'. The file auto-closes after the block.
  3. Final Answer:

    count = 0 File.open('log.txt', 'r') do |f| f.each_line { |line| count += 1 if line.include?('error') } end puts count -> Option D
  4. Quick Check:

    File.open block + each_line + count = count = 0 File.open('log.txt', 'r') do |f| f.each_line { |line| count += 1 if line.include?('error') } end puts count [OK]
Hint: Use File.open with block and each_line for safe file reading [OK]
Common Mistakes:
  • Forgetting to close file when not using block
  • Missing block parameter or using wrong syntax
  • Using methods outside block scope
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard