Step 1: Recall the two address spaces involved.
A running process only knows about logical, or virtual, addresses, the ones the CPU generates while executing instructions. But actual data sits somewhere in physical RAM, at physical addresses. Something has to bridge this gap every single time memory is accessed.
Step 2: Identify what does the bridging.
That bridge is the page table. For every page number in the logical address, the page table stores the corresponding frame number in physical memory, so the Memory Management Unit can translate one into the other on the fly.
Step 3: Rule out the distractors.
Storing file metadata is the job of the file system's inode or directory structures, tracking free memory is handled by free frame lists or bitmaps, and CPU scheduling is entirely unrelated, it is managed by the scheduler, not the page table. None of these describe what a page table actually stores.
Step 4: State the conclusion.
The defining job of a page table is address translation,
\[ \boxed{\text{Map logical to physical addresses}} \]