I suggest using a hash instead of plain variables: 
#!/usr/bin/perl

use strict;
use warnings;

use Data::Dumper;

my %questions;
my $cur;

while (<DATA>) {
    $cur = $1 if /^\d+\.\s*(.*)$/;
    $questions{$cur}->{selected} = $1 if $cur and /^[A-Z]+\.\s*(.*)\s+
+\*$/;
    s/\s*\*\s*$//;
    push @{$questions{$cur}->{answers}}, $1 if $cur and /^[A-Z]+\.\s*(
+.*)\s*$/;
}

print Dumper \%questions;

__DATA__
1. What is my name?
A. Rooney *
B. Gerrard
C. Ronaldo
D. Ronaldinho
2. Who's your bet in the coming World Cup?
A. Brazil *
B. Germany
C. England
D. Cameroon

[download]

In reply to Re: Reading a File by Line then Analyzing each Line by neniro
in thread Reading a File by Line then Analyzing each Line by soon_j

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.