Question 40
The AI governance team needs to assess the following access or risk decision: An EU-only dataset is proposed for a model that may route to another region. What measurement should be required at the technical acceptance gate?
Explanation
Correct Answer
“Confirmed routing location, compliant policy assessment, supported feature availability and measured inference latency” is supported by this requirement: An EU-only dataset is proposed for a model that may route to another region. Regional model availability and data-handling implications require explicit configuration review. Verify it using confirmed routing location, compliant policy assessment, supported feature availability and measured inference latency.
Incorrect Answers
“A statement that the company uses Snowflake somewhere” would not meet the requirement that an EU-only dataset is proposed for a model that may route to another region. Regional model availability and data-handling implications require explicit configuration review. The more reliable approach is to verify region availability and cross-region inference settings against contractual data locality, latency and feature constraints before enabling routing.
“Number of remote regions enabled without data-governance approval” would not meet the requirement that an EU-only dataset is proposed for a model that may route to another region. Regional model availability and data-handling implications require explicit configuration review. The more reliable approach is to verify region availability and cross-region inference settings against contractual data locality, latency and feature constraints before enabling routing.
“A model name appearing in online documentation without an account-region test” would not meet the requirement that an EU-only dataset is proposed for a model that may route to another region. Regional model availability and data-handling implications require explicit configuration review. The more reliable approach is to verify region availability and cross-region inference settings against contractual data locality, latency and feature constraints before enabling routing.