Option A is correct because Global Tables use last writer wins (LWW) conflict resolution by default; if the application writes to both regions simultaneously, the latest write from the region with the highest timestamp wins, but replication is typically sub-second. However, if the 'ReplicationGroup' is misconfigured, replication can be delayed. But the question mentions strong consistency reads, which are not supported for Global Tables (they support eventual consistency only).
Actually, strong consistency reads are not available for Global Tables; using them would cause an error. However, the scenario says they notice a delay, which is expected for eventual consistency. Option A is wrong: strong consistency reads are not supported for Global Tables.
Option B is correct: strong consistency reads are not supported, but the scenario says they are using them; this would cause an error, not delay. Option C: DynamoDB Streams must be enabled for Global Tables; if disabled, writes would not replicate at all. Option D: Auto Scaling does not affect replication.
Given the options, the most likely cause is that DynamoDB Streams is not enabled on the table, which would prevent replication entirely. But the question says 'not visible after several seconds', which suggests eventual consistency delay. Actually, the correct answer is that Global Tables only support eventual consistency, so strong consistency reads are not possible; but the question says they are using them, which might be a misconfiguration.
However, typical exam: strong consistency reads on Global Tables are not supported; using them would cause an error, not a delay. So Option B is plausible: they might have requested strong consistency reads on a global table, which would fail. But the scenario says they notice a delay, not an error.
I think the intended answer is that Global Tables rely on DynamoDB Streams; if streams are disabled, writes won't replicate. So Option C. Let me re-evaluate: DynamoDB Streams must be enabled for the table to be used in Global Tables.
If streams are disabled, writes will not be replicated. That matches the symptom: writes to us-east-1 are not visible in eu-west-1. Option A: LWW is default, but it doesn't cause delay.
Option B: Strong consistency reads are not supported for Global Tables, but the scenario says they are using them; it's unclear if that causes delay or error. Option D: Auto Scaling does not affect replication. So Option C is most likely.