Free AB-410 sample questions

Correct answer: A table supports a maximum of 5 prompt columns, and input columns cannot be formula columns, file columns, image columns, or other prompt columns.

In Microsoft Dataverse, a table supports a maximum of 5 prompt columns. Furthermore, input columns referenced by the prompt definition cannot be formula columns, file columns, image columns, or other prompt columns (their values are ignored if chosen). Every prompt definition also requires a single text input variable (defaulting to PromptColumnRecordId) filtered on the table's primary column, and execution occurs asynchronously.

Correct answer: Estimated consumption

According to official Microsoft documentation for prompt columns, makers and administrators track estimated credit usage in make.powerautomate.com by opening the Automation center, selecting AI Builder activity, and reviewing the 'Estimated consumption' view.

Correct answer: React code covering both the front-end layout and business logic

Generative pages in model-driven apps leverage generative AI to create React code that encapsulates both the front-end interface layout and underlying business logic based on natural language descriptions.

Correct answer: Generative pages can reference Dataverse tables, Power Platform connectors, and custom APIs, while the 'Include images' option sources graphics from curated stock libraries rather than generating new synthetic AI images.

Generative pages support referencing Dataverse tables, Power Platform connectors, Dataverse custom APIs, and uploaded reference mockups. When the 'Include images' option is selected in the prompt, the agent pulls images from curated stock libraries rather than generating synthetic AI images via generative diffusion models.

Correct answer: False

False. In model-driven apps, generative pages require explicit publishing along with the app before end users can access them during runtime. Generating and previewing the page in the designer does not automatically expose changes to runtime users.

Correct answer: Named formulas cannot invoke behavior functions, cannot cause side effects, and automatically recalculate only when referenced by active controls.

Named formulas declared in App.Formulas are immutable definitions that cannot be modified via Set() or UpdateContext(). They cannot contain side effects or behavior functions (such as Collect, Navigate, or Patch). They recalculate automatically only when their referenced dependencies change and when their value is actually requested by an active control or formula.