A county GIS parcel desk must keep constituent drawings and prompts in an approved Region even if another Region has a newer model. Which governance rule should win?
Select an answer to reveal the explanation.
Short Explanation
Think of constituent drawings that have to stay in the approved Region even if another Region has a newer model. Residency wins. Chasing novelty or copying everywhere drops the rule.
Full Explanation
The county GIS parcel desk must keep constituent drawings and prompts in an approved Region even when another Region offers a newer foundation model. Data residency is the governance rule that wins: keep AI content where policy and law require, and document that constraint so builders cannot silently relocate constituent materials for novelty. Model freshness does not outrank residency obligations for drawings residents entrusted to the county.
Moving drawings to chase the newer model fails by concept: novelty is not a residency waiver and does not authorize cross-Region relocation of regulated content. A Domain 2 hosting-tradeoff recap only fails because recalling hosting tradeoffs without a written residency rule still leaves drawings free to migrate. Copying drawings to every Region fails because multiplying copies expands the residency problem rather than satisfying an approved-Region mandate.
Exam caveat: residency includes logs, embeddings, backups, and failover replicas—not only the primary object store—so check invocation-log destinations and any cross-Region replication. Operational check: confirm Bedrock and storage endpoints for the parcel desk are in the approved Region, block or alert on cross-Region copy jobs for constituent drawings, and record the residency rule in the governance packet reviewers will use.