In the lesson's page translation, which address component remains unchanged?

• The virtual page number being translated
• The offset within the page
• The complete virtual address being translated

An address belongs to a process's virtual address space. Does that alone mean the process can access it?

• No; it may be unmapped or lack permission for that access
• Yes; membership maps it and permits every attempted access
• Yes; membership keeps its page resident and writable in RAM

With virtual memory and backing storage, every valid virtual page must remain in RAM at the same time.

Page size is 256 address units. Virtual address 877 lies on page 3, which maps to frame 6. What is its physical address?

In a toy system, page size is 100 address units. Virtual page 4 has offset 65 and maps to physical frame 8. What is the physical address?

• 465
• 800
• 865

What information does a TLB cache for address translation?

• Virtual-page to physical-frame mappings and permissions
• The full data bytes read from each translated memory page
• The source-code lines used to calculate every virtual address

A program writes an unintended value to its own permitted writable page. Does this alone show that address translation or permission checking failed?

• Yes; every permitted write must preserve all earlier program data
• Yes; page translation should repair the program's update logic
• No; access permission does not prove the algorithm correct

Two processes have separate page tables, but the OS intentionally maps one writable page in each to the same physical frame. What follows?

• Both are isolated from every byte of that shared frame
• Both can change the shared frame where writing is allowed
• Both lose the ability to access any other mapped memory page