Without a Team class, you'd need two arrays: homeColors[i] and guestColors[i]. Easy to swap indices or compare the wrong arrays.
Classes keep related properties together, making bugs harder to write. The code reads like the problem: check if the home team's home color matches the guest team's guest color.
Classes turn that sentence directly into code without mental translation from indices to meaning. You learned that classes scale with complexity. Add more team properties later? Just add fields to the class.
Your comparison logic stays clean. This is why object-oriented programming beats parallel arrays in real projects.