Class is the blueprint of whatever, a house.

Object is a house that's actually been built using that blueprint. You might have 50 houses (objects) defined by a single blueprint (class).

“Is this a reasonable analogy”

Kind of. That concept is sometimes referred to as the Factory Pattern. You give it some raw materials and it spits out some products.

While in this question it does use a class, classes are more basic than that.

I think of a Class like a blueprint for a car. And each car that is actually built from that blueprint as an Object. The blueprint can have settings, like paint colour, seat fabric and the like.

For the question in the OP, you can imagine you design a form in Word that you print out. The form has 2 blank fields; Question and Answer. This is a Class. You can call it QuestionClass (terrible name, used for clarity)

When you print those forms you are creating an Object. Also known as creating an Instance of the Class. Also known as Instantiating.
Then you can fill in the questions and answers on each sheet/Object.

You can, however, when designing your Class make it so you MUST supply the question and the answer for this instance when you create it, rather than add them later. You give the class some initial values. You call this an Initialiser.

Now take a step back. Make a new function that takes in a list of Question-Answer pairs and spits out a bunch of the QuestionClass Objects.

That’s a big chunk of the work done.

You are taking a short online class. The class has objectives.

The class itself is defined by what it is supposed to handle (students mastering X skills). But the class by itself is only a structure, a definition that can be used to standardize ehat this sourt of course will look like. Within that class are actual students producing work that is more or less in line with the class objectives. These are objects that belong to the class that contain work.

A class is the structured definition. So you could have a class “factory” that defines a factory as a large building that takes in raw materials and outputs a specific type of finished goods.

The automotive factory on Fifth would be an object in the Factory class. That factory itself would be populated with contents defined by how the factory was operating.

Likewise in Python, you can define a class Greeting that contains a single string. You can then define an object friendlyGreeting of type Greeting, and that object will automatically contain a single string, because that’s what objects of class Greeting have. You can then populate the string in friendlyGreeting with the characters “Hello World” and you have an instantiated object. You could then have another object inheriting Greeting named unfriendlyGreeting. It will also inherit the single string element. But if you never instantiate unfriendlyGreeting, it won’t be usable in your program, and will have no actual contents.

So to sum up, classes define the structure of objects you use in your program. Objects define specific “things” that you can make copies of and interact with in your program. When an object is actually used and is containing data to be used in a specific way in your program, it is instantiated (there is an actual instance of that object).

Classes are like definitions for what objects look like. A lot of times people will use the terms interchangably in non formal settings.

It so happens that the class they want you to make is like a factory, but not all classes are like that. They can do anything. It's just a different way to organize your code. Languages like C don't have classes and you can write Python code without classes. There is a concept called the "factory pattern" (not going to bore you with the details) but suffice to say, it's a very common thing so your analogy is correct -- but as long as you remember not all classes behave like that, just this specific one.