The correct option is Row level security restricts access to whole rows while cell level security controls individual fields within a row.

Row level security controls whether an entire record is visible to a user based on policy attributes or filters. It operates at the row or record level so a user either sees the whole row or does not, and it is commonly used to enforce tenant isolation and data partitioning across users.

Cell level security controls access to specific fields inside a row so users may see some columns while other sensitive fields are masked or hidden. This finer granularity is often called column level or cell level security and it is useful when only particular attributes such as personal identifiers need stronger protection.

Row level security is always easier to configure than cell level security is incorrect because ease of configuration depends on the platform and available features. In some systems row rules are simpler but in others built in column protections make cell level controls straightforward, so you cannot assume one is always easier.

Row level security applies to relational tables while cell level security is only for key value stores is incorrect because both row and cell level controls are used across relational and non relational systems. Column or cell level protections are common in data warehouses and relational databases as well as in some key value or document stores.

Row level security provides stronger protection than cell level security is incorrect because strength depends on what you need to protect. Cell level security can provide stronger protection for specific sensitive attributes while row level security is better when entire records must be restricted. The approaches are complementary rather than one universally stronger.

Full AWS Practitioner Certification Question