There are multiple ways to achieve this result. Since the objective is to impact the entire table, Client Construct is ideal for this purpose. This means having to use the Client Exporter and Client Importer functions in order to achieve this objective.
Client Exporter has multiple processing methods: Transport, R3Trans, and Direct. Using both the Transport and R3Trans options are naturals here because of the inherent nature of how R3 functionality works, which is during import the existing data in the table will be deleted first and then the data will be imported which leads to the result of replacing or overwriting all of the existing data.
Now the reality is that most customers do not want to generate and release transports to perform this task - especially when Prod is used as the source system - and the Qlik team understands the reluctance to do so, which means that using the Transport processing method may be less than ideal. This same result can be achieved using the R3Trans processing method which does not create a transport; however, of the three processing methods available, this one is typically the slowest so that makes it less than ideal (although this may be mitigated if the amount of data being copied is not significant).
As of version 8.6.1, an enhancement was released which allows for this same overwriting result to be achieved using the Direct processing method. The key here is that when using the Client Importer function there is a new option named 'Delete Table Data Before Import'. With this option selected, the expected behavior is that the data in the table(s) being imported will first be purged and then the data imported. If this option is not selected, then this same overwriting objective may not be achieved. Notice in the capture below showing this new setting that the default remains as 'Replace Conflicting Data' and so the user must specifically select this new feature in order to use it.