Which configuration supports the desired vehicle record list behavior?

Which configuration supports the desired vehicle record list behavior?

• A. A user filter for the status field with a default option corresponding to active.
• B. A global view setting to show both active and inactive records by default.
• C. Hard coding the records list to only include active records without a filter.
• D. A separate report to retrieve only active records on demand.

Answer: (A)

The key idea is controlling what the list shows by default through a configurable filter on the data. By applying a filter on the status field and giving it a default value of active, the list automatically presents only active vehicles when it first loads. This matches a common expectation: start with a focused view (active records) and still let the user adjust the filter if they want to see inactive records later. Using a user filter keeps things flexible and maintainable. It lets users refine the results without hard-coding the list to a single subset, and it avoids the extra steps of running separate reports. The other approaches either force a fixed set of records (hard-coded active only) or require additional actions (a separate report) to view the same information, which adds friction and reduces interactivity. A global view setting that shows both by default would not deliver the default-active behavior that the filter with a default value provides.

The key idea is controlling what the list shows by default through a configurable filter on the data. By applying a filter on the status field and giving it a default value of active, the list automatically presents only active vehicles when it first loads. This matches a common expectation: start with a focused view (active records) and still let the user adjust the filter if they want to see inactive records later.

Using a user filter keeps things flexible and maintainable. It lets users refine the results without hard-coding the list to a single subset, and it avoids the extra steps of running separate reports. The other approaches either force a fixed set of records (hard-coded active only) or require additional actions (a separate report) to view the same information, which adds friction and reduces interactivity. A global view setting that shows both by default would not deliver the default-active behavior that the filter with a default value provides.