Pass Microsoft PL-200 Exam in First Attempt Guaranteed!

This response applies to the different subject of One-to-many lookup relationship design, rather than directly to Many-to-many relational association: Inspect the table relationship metadata, child lookup values, requiredness and behavior when a parent record changes.. In this scenario: An event management solution must track attendees across sessions and the analyst plans fifty hard-coded lookup columns. The relevant technical behavior is: Many-to-many associations represent repeated membership on both sides; a separate intersection table is useful when the link itself needs data. The appropriate implementation is: Implement an appropriate many-to-many relationship or explicit junction table when the association requires its own attributes. Independent validation: Check cardinality, association-specific fields, querying needs and a create/remove test across both parent tables. Accept only when: The same entity can be linked to multiple counterparts and all required association details are stored without duplicate lookup slots.

This response applies to the different subject of Dataverse column choices formulas and rollups, rather than directly to Many-to-many relational association: Choose column types appropriately and evaluate supported choice, formula and rollup semantics for derived or aggregated information.. In this scenario: An event management solution must track attendees across sessions and the analyst plans fifty hard-coded lookup columns. The relevant technical behavior is: Many-to-many associations represent repeated membership on both sides; a separate intersection table is useful when the link itself needs data. The appropriate implementation is: Implement an appropriate many-to-many relationship or explicit junction table when the association requires its own attributes. Independent validation: Check cardinality, association-specific fields, querying needs and a create/remove test across both parent tables. Accept only when: The same entity can be linked to multiple counterparts and all required association details are stored without duplicate lookup slots.

This is an unsafe or unsupported shortcut: Force a genuinely many-to-many model into a single-valued lookup and claim it supports all simultaneous memberships. It fails to address Many-to-many relational association. In this scenario: An event management solution must track attendees across sessions and the analyst plans fifty hard-coded lookup columns. The relevant technical behavior is: Many-to-many associations represent repeated membership on both sides; a separate intersection table is useful when the link itself needs data. The appropriate implementation is: Implement an appropriate many-to-many relationship or explicit junction table when the association requires its own attributes. Independent validation: Check cardinality, association-specific fields, querying needs and a create/remove test across both parent tables. Accept only when: The same entity can be linked to multiple counterparts and all required association details are stored without duplicate lookup slots.

This is an unsafe or unsupported shortcut: Force a genuinely many-to-many model into a single-valued lookup and claim it supports all simultaneous memberships. It fails to address Many-to-many relational association. In this scenario: An event management solution must track attendees across sessions and the analyst plans fifty hard-coded lookup columns. The relevant technical behavior is: Many-to-many associations represent repeated membership on both sides; a separate intersection table is useful when the link itself needs data. The appropriate implementation is: Implement an appropriate many-to-many relationship or explicit junction table when the association requires its own attributes. Independent validation: Check cardinality, association-specific fields, querying needs and a create/remove test across both parent tables. Accept only when: The same entity can be linked to multiple counterparts and all required association details are stored without duplicate lookup slots.

This response applies to the different subject of Dataverse activity tables and timeline records, rather than directly to Many-to-many relational association: Inspect activity table metadata, regarding relationships, timeline settings and test appointment or task records on target forms.. In this scenario: An event management solution must track attendees across sessions and the analyst plans fifty hard-coded lookup columns. The relevant technical behavior is: Many-to-many associations represent repeated membership on both sides; a separate intersection table is useful when the link itself needs data. The appropriate implementation is: Implement an appropriate many-to-many relationship or explicit junction table when the association requires its own attributes. Independent validation: Check cardinality, association-specific fields, querying needs and a create/remove test across both parent tables. Accept only when: The same entity can be linked to multiple counterparts and all required association details are stored without duplicate lookup slots.

This response applies to the different subject of Dataverse column choices formulas and rollups, rather than directly to Many-to-many relational association: Inspect the column type, expression or rollup definition, refresh behavior, related records and displayed values after sample changes.. In this scenario: An event management solution must track attendees across sessions and the analyst plans fifty hard-coded lookup columns. The relevant technical behavior is: Many-to-many associations represent repeated membership on both sides; a separate intersection table is useful when the link itself needs data. The appropriate implementation is: Implement an appropriate many-to-many relationship or explicit junction table when the association requires its own attributes. Independent validation: Check cardinality, association-specific fields, querying needs and a create/remove test across both parent tables. Accept only when: The same entity can be linked to multiple counterparts and all required association details are stored without duplicate lookup slots.

This is an unsafe or unsupported shortcut: Force a genuinely many-to-many model into a single-valued lookup and claim it supports all simultaneous memberships. It fails to address Many-to-many relational association. In this scenario: An event management solution must track attendees across sessions and the analyst plans fifty hard-coded lookup columns. The relevant technical behavior is: Many-to-many associations represent repeated membership on both sides; a separate intersection table is useful when the link itself needs data. The appropriate implementation is: Implement an appropriate many-to-many relationship or explicit junction table when the association requires its own attributes. Independent validation: Check cardinality, association-specific fields, querying needs and a create/remove test across both parent tables. Accept only when: The same entity can be linked to multiple counterparts and all required association details are stored without duplicate lookup slots.

This response applies to the different subject of Standard versus custom Dataverse table selection, rather than directly to Many-to-many relational association: The modeled tables represent each real-world entity once, preserve supported standard capabilities and satisfy the documented data relationships.. In this scenario: An event management solution must track attendees across sessions and the analyst plans fifty hard-coded lookup columns. The relevant technical behavior is: Many-to-many associations represent repeated membership on both sides; a separate intersection table is useful when the link itself needs data. The appropriate implementation is: Implement an appropriate many-to-many relationship or explicit junction table when the association requires its own attributes. Independent validation: Check cardinality, association-specific fields, querying needs and a create/remove test across both parent tables. Accept only when: The same entity can be linked to multiple counterparts and all required association details are stored without duplicate lookup slots.

This response applies to the different subject of Dataverse cascading relationship behavior, rather than directly to Many-to-many relational association: Child records are retained, restricted, reassigned or deleted exactly as the approved lifecycle and audit policy specifies.. In this scenario: An event management solution must track attendees across sessions and the analyst plans fifty hard-coded lookup columns. The relevant technical behavior is: Many-to-many associations represent repeated membership on both sides; a separate intersection table is useful when the link itself needs data. The appropriate implementation is: Implement an appropriate many-to-many relationship or explicit junction table when the association requires its own attributes. Independent validation: Check cardinality, association-specific fields, querying needs and a create/remove test across both parent tables. Accept only when: The same entity can be linked to multiple counterparts and all required association details are stored without duplicate lookup slots.

This is an unsafe or unsupported shortcut: Enable broad cascade delete on every relationship to keep the database tidy without evaluating retention and business impact. It fails to address Dataverse cascading relationship behavior. In this scenario: An account deletion unexpectedly removes all related tasks because a relationship cascade setting was copied without review. The relevant technical behavior is: Dataverse relationship cascading rules can propagate defined operations to related rows, so deletion and reassignment policies must be deliberate. The appropriate implementation is: Configure relationship behavior and individual cascade actions to match retention, assignment, share and delete requirements; test them on sample records. Independent validation: Inspect relationship cascade settings and compare before-and-after parent and child records during controlled assign and delete tests. Accept only when: Child records are retained, restricted, reassigned or deleted exactly as the approved lifecycle and audit policy specifies.

This response applies to the different subject of Dataverse activity tables and timeline records, rather than directly to Dataverse cascading relationship behavior: Choose supported activity tables and activity relationships for time-based interactions, and configure the timeline to surface relevant activities.. In this scenario: An account deletion unexpectedly removes all related tasks because a relationship cascade setting was copied without review. The relevant technical behavior is: Dataverse relationship cascading rules can propagate defined operations to related rows, so deletion and reassignment policies must be deliberate. The appropriate implementation is: Configure relationship behavior and individual cascade actions to match retention, assignment, share and delete requirements; test them on sample records. Independent validation: Inspect relationship cascade settings and compare before-and-after parent and child records during controlled assign and delete tests. Accept only when: Child records are retained, restricted, reassigned or deleted exactly as the approved lifecycle and audit policy specifies.

This response applies to the different subject of Alternate keys and Dataverse migration integrity, rather than directly to Dataverse cascading relationship behavior: Define suitable alternate keys for stable business identifiers and use key-aware import or upsert with tested collision handling.. In this scenario: An account deletion unexpectedly removes all related tasks because a relationship cascade setting was copied without review. The relevant technical behavior is: Dataverse relationship cascading rules can propagate defined operations to related rows, so deletion and reassignment policies must be deliberate. The appropriate implementation is: Configure relationship behavior and individual cascade actions to match retention, assignment, share and delete requirements; test them on sample records. Independent validation: Inspect relationship cascade settings and compare before-and-after parent and child records during controlled assign and delete tests. Accept only when: Child records are retained, restricted, reassigned or deleted exactly as the approved lifecycle and audit policy specifies.

This response applies to the different subject of Dataverse record ownership and table security model, rather than directly to Dataverse cascading relationship behavior: Table ownership influences available record-level security semantics and is selected when the Dataverse table is created, rather than being an ordinary later property change.. In this scenario: An account deletion unexpectedly removes all related tasks because a relationship cascade setting was copied without review. The relevant technical behavior is: Dataverse relationship cascading rules can propagate defined operations to related rows, so deletion and reassignment policies must be deliberate. The appropriate implementation is: Configure relationship behavior and individual cascade actions to match retention, assignment, share and delete requirements; test them on sample records. Independent validation: Inspect relationship cascade settings and compare before-and-after parent and child records during controlled assign and delete tests. Accept only when: Child records are retained, restricted, reassigned or deleted exactly as the approved lifecycle and audit policy specifies.

This is an unsafe or unsupported shortcut: Enable broad cascade delete on every relationship to keep the database tidy without evaluating retention and business impact. It fails to address Dataverse cascading relationship behavior. In this scenario: An account deletion unexpectedly removes all related tasks because a relationship cascade setting was copied without review. The relevant technical behavior is: Dataverse relationship cascading rules can propagate defined operations to related rows, so deletion and reassignment policies must be deliberate. The appropriate implementation is: Configure relationship behavior and individual cascade actions to match retention, assignment, share and delete requirements; test them on sample records. Independent validation: Inspect relationship cascade settings and compare before-and-after parent and child records during controlled assign and delete tests. Accept only when: Child records are retained, restricted, reassigned or deleted exactly as the approved lifecycle and audit policy specifies.

This response applies to the different subject of Standard versus custom Dataverse table selection, rather than directly to Dataverse cascading relationship behavior: Standard tables provide built-in business semantics while custom tables support new data concepts; duplicating a standard table can fragment identity and functionality.. In this scenario: An account deletion unexpectedly removes all related tasks because a relationship cascade setting was copied without review. The relevant technical behavior is: Dataverse relationship cascading rules can propagate defined operations to related rows, so deletion and reassignment policies must be deliberate. The appropriate implementation is: Configure relationship behavior and individual cascade actions to match retention, assignment, share and delete requirements; test them on sample records. Independent validation: Inspect relationship cascade settings and compare before-and-after parent and child records during controlled assign and delete tests. Accept only when: Child records are retained, restricted, reassigned or deleted exactly as the approved lifecycle and audit policy specifies.

This response applies to the different subject of Dataverse column choices formulas and rollups, rather than directly to Dataverse cascading relationship behavior: Inspect the column type, expression or rollup definition, refresh behavior, related records and displayed values after sample changes.. In this scenario: An account deletion unexpectedly removes all related tasks because a relationship cascade setting was copied without review. The relevant technical behavior is: Dataverse relationship cascading rules can propagate defined operations to related rows, so deletion and reassignment policies must be deliberate. The appropriate implementation is: Configure relationship behavior and individual cascade actions to match retention, assignment, share and delete requirements; test them on sample records. Independent validation: Inspect relationship cascade settings and compare before-and-after parent and child records during controlled assign and delete tests. Accept only when: Child records are retained, restricted, reassigned or deleted exactly as the approved lifecycle and audit policy specifies.

This response applies to the different subject of One-to-many lookup relationship design, rather than directly to Dataverse cascading relationship behavior: Inspect the table relationship metadata, child lookup values, requiredness and behavior when a parent record changes.. In this scenario: An account deletion unexpectedly removes all related tasks because a relationship cascade setting was copied without review. The relevant technical behavior is: Dataverse relationship cascading rules can propagate defined operations to related rows, so deletion and reassignment policies must be deliberate. The appropriate implementation is: Configure relationship behavior and individual cascade actions to match retention, assignment, share and delete requirements; test them on sample records. Independent validation: Inspect relationship cascade settings and compare before-and-after parent and child records during controlled assign and delete tests. Accept only when: Child records are retained, restricted, reassigned or deleted exactly as the approved lifecycle and audit policy specifies.

This is an unsafe or unsupported shortcut: Enable broad cascade delete on every relationship to keep the database tidy without evaluating retention and business impact. It fails to address Dataverse cascading relationship behavior. In this scenario: An account deletion unexpectedly removes all related tasks because a relationship cascade setting was copied without review. The relevant technical behavior is: Dataverse relationship cascading rules can propagate defined operations to related rows, so deletion and reassignment policies must be deliberate. The appropriate implementation is: Configure relationship behavior and individual cascade actions to match retention, assignment, share and delete requirements; test them on sample records. Independent validation: Inspect relationship cascade settings and compare before-and-after parent and child records during controlled assign and delete tests. Accept only when: Child records are retained, restricted, reassigned or deleted exactly as the approved lifecycle and audit policy specifies.

This response applies to the different subject of Dataverse search scope and indexing, rather than directly to Dataverse cascading relationship behavior: Authorized users find relevant records through supported search with intended table scope and acceptable index freshness.. In this scenario: An account deletion unexpectedly removes all related tasks because a relationship cascade setting was copied without review. The relevant technical behavior is: Dataverse relationship cascading rules can propagate defined operations to related rows, so deletion and reassignment policies must be deliberate. The appropriate implementation is: Configure relationship behavior and individual cascade actions to match retention, assignment, share and delete requirements; test them on sample records. Independent validation: Inspect relationship cascade settings and compare before-and-after parent and child records during controlled assign and delete tests. Accept only when: Child records are retained, restricted, reassigned or deleted exactly as the approved lifecycle and audit policy specifies.

This response applies to the different subject of One-to-many lookup relationship design, rather than directly to Dataverse cascading relationship behavior: Each child record resolves to the correct parent and related views display accurate links after parent metadata changes.. In this scenario: An account deletion unexpectedly removes all related tasks because a relationship cascade setting was copied without review. The relevant technical behavior is: Dataverse relationship cascading rules can propagate defined operations to related rows, so deletion and reassignment policies must be deliberate. The appropriate implementation is: Configure relationship behavior and individual cascade actions to match retention, assignment, share and delete requirements; test them on sample records. Independent validation: Inspect relationship cascade settings and compare before-and-after parent and child records during controlled assign and delete tests. Accept only when: Child records are retained, restricted, reassigned or deleted exactly as the approved lifecycle and audit policy specifies.

This is an unsafe or unsupported shortcut: Enable broad cascade delete on every relationship to keep the database tidy without evaluating retention and business impact. It fails to address Dataverse cascading relationship behavior. In this scenario: An account deletion unexpectedly removes all related tasks because a relationship cascade setting was copied without review. The relevant technical behavior is: Dataverse relationship cascading rules can propagate defined operations to related rows, so deletion and reassignment policies must be deliberate. The appropriate implementation is: Configure relationship behavior and individual cascade actions to match retention, assignment, share and delete requirements; test them on sample records. Independent validation: Inspect relationship cascade settings and compare before-and-after parent and child records during controlled assign and delete tests. Accept only when: Child records are retained, restricted, reassigned or deleted exactly as the approved lifecycle and audit policy specifies.

This response applies to the different subject of Dataverse search scope and indexing, rather than directly to Dataverse cascading relationship behavior: Configure Dataverse search and approved searchable columns or tables, then account for index updates and test representative queries.. In this scenario: When an assigned account owner changes, associated records should follow a defined reassignment policy but remain on the old owner. The relevant technical behavior is: Dataverse relationship cascading rules can propagate defined operations to related rows, so deletion and reassignment policies must be deliberate. The appropriate implementation is: Configure relationship behavior and individual cascade actions to match retention, assignment, share and delete requirements; test them on sample records. Independent validation: Inspect relationship cascade settings and compare before-and-after parent and child records during controlled assign and delete tests. Accept only when: Child records are retained, restricted, reassigned or deleted exactly as the approved lifecycle and audit policy specifies.

This is an unsafe or unsupported shortcut: Enable broad cascade delete on every relationship to keep the database tidy without evaluating retention and business impact. It fails to address Dataverse cascading relationship behavior. In this scenario: When an assigned account owner changes, associated records should follow a defined reassignment policy but remain on the old owner. The relevant technical behavior is: Dataverse relationship cascading rules can propagate defined operations to related rows, so deletion and reassignment policies must be deliberate. The appropriate implementation is: Configure relationship behavior and individual cascade actions to match retention, assignment, share and delete requirements; test them on sample records. Independent validation: Inspect relationship cascade settings and compare before-and-after parent and child records during controlled assign and delete tests. Accept only when: Child records are retained, restricted, reassigned or deleted exactly as the approved lifecycle and audit policy specifies.

This response applies to the different subject of Alternate keys and Dataverse migration integrity, rather than directly to Dataverse cascading relationship behavior: Define suitable alternate keys for stable business identifiers and use key-aware import or upsert with tested collision handling.. In this scenario: When an assigned account owner changes, associated records should follow a defined reassignment policy but remain on the old owner. The relevant technical behavior is: Dataverse relationship cascading rules can propagate defined operations to related rows, so deletion and reassignment policies must be deliberate. The appropriate implementation is: Configure relationship behavior and individual cascade actions to match retention, assignment, share and delete requirements; test them on sample records. Independent validation: Inspect relationship cascade settings and compare before-and-after parent and child records during controlled assign and delete tests. Accept only when: Child records are retained, restricted, reassigned or deleted exactly as the approved lifecycle and audit policy specifies.

This response applies to the different subject of One-to-many lookup relationship design, rather than directly to Dataverse cascading relationship behavior: A lookup creates a structured relationship between a child row and its referenced parent, supporting referential navigation beyond duplicated strings.. In this scenario: When an assigned account owner changes, associated records should follow a defined reassignment policy but remain on the old owner. The relevant technical behavior is: Dataverse relationship cascading rules can propagate defined operations to related rows, so deletion and reassignment policies must be deliberate. The appropriate implementation is: Configure relationship behavior and individual cascade actions to match retention, assignment, share and delete requirements; test them on sample records. Independent validation: Inspect relationship cascade settings and compare before-and-after parent and child records during controlled assign and delete tests. Accept only when: Child records are retained, restricted, reassigned or deleted exactly as the approved lifecycle and audit policy specifies.

This response applies to the different subject of Alternate keys and Dataverse migration integrity, rather than directly to Dataverse cascading relationship behavior: Alternate keys support uniqueness and identification for integration scenarios where the Dataverse row ID is not the source system key.. In this scenario: When an assigned account owner changes, associated records should follow a defined reassignment policy but remain on the old owner. The relevant technical behavior is: Dataverse relationship cascading rules can propagate defined operations to related rows, so deletion and reassignment policies must be deliberate. The appropriate implementation is: Configure relationship behavior and individual cascade actions to match retention, assignment, share and delete requirements; test them on sample records. Independent validation: Inspect relationship cascade settings and compare before-and-after parent and child records during controlled assign and delete tests. Accept only when: Child records are retained, restricted, reassigned or deleted exactly as the approved lifecycle and audit policy specifies.

This is an unsafe or unsupported shortcut: Enable broad cascade delete on every relationship to keep the database tidy without evaluating retention and business impact. It fails to address Dataverse cascading relationship behavior. In this scenario: When an assigned account owner changes, associated records should follow a defined reassignment policy but remain on the old owner. The relevant technical behavior is: Dataverse relationship cascading rules can propagate defined operations to related rows, so deletion and reassignment policies must be deliberate. The appropriate implementation is: Configure relationship behavior and individual cascade actions to match retention, assignment, share and delete requirements; test them on sample records. Independent validation: Inspect relationship cascade settings and compare before-and-after parent and child records during controlled assign and delete tests. Accept only when: Child records are retained, restricted, reassigned or deleted exactly as the approved lifecycle and audit policy specifies.

This response applies to the different subject of Virtual Dataverse tables for external records, rather than directly to Dataverse cascading relationship behavior: Check provider support, external identifiers, authentication, supported CRUD and querying operations and a representative application read.. In this scenario: When an assigned account owner changes, associated records should follow a defined reassignment policy but remain on the old owner. The relevant technical behavior is: Dataverse relationship cascading rules can propagate defined operations to related rows, so deletion and reassignment policies must be deliberate. The appropriate implementation is: Configure relationship behavior and individual cascade actions to match retention, assignment, share and delete requirements; test them on sample records. Independent validation: Inspect relationship cascade settings and compare before-and-after parent and child records during controlled assign and delete tests. Accept only when: Child records are retained, restricted, reassigned or deleted exactly as the approved lifecycle and audit policy specifies.

This response applies to the different subject of Dataverse search scope and indexing, rather than directly to Dataverse cascading relationship behavior: Inspect search availability, table search settings, searchable field configuration and query outcomes after indexing has caught up.. In this scenario: When an assigned account owner changes, associated records should follow a defined reassignment policy but remain on the old owner. The relevant technical behavior is: Dataverse relationship cascading rules can propagate defined operations to related rows, so deletion and reassignment policies must be deliberate. The appropriate implementation is: Configure relationship behavior and individual cascade actions to match retention, assignment, share and delete requirements; test them on sample records. Independent validation: Inspect relationship cascade settings and compare before-and-after parent and child records during controlled assign and delete tests. Accept only when: Child records are retained, restricted, reassigned or deleted exactly as the approved lifecycle and audit policy specifies.

This is an unsafe or unsupported shortcut: Enable broad cascade delete on every relationship to keep the database tidy without evaluating retention and business impact. It fails to address Dataverse cascading relationship behavior. In this scenario: When an assigned account owner changes, associated records should follow a defined reassignment policy but remain on the old owner. The relevant technical behavior is: Dataverse relationship cascading rules can propagate defined operations to related rows, so deletion and reassignment policies must be deliberate. The appropriate implementation is: Configure relationship behavior and individual cascade actions to match retention, assignment, share and delete requirements; test them on sample records. Independent validation: Inspect relationship cascade settings and compare before-and-after parent and child records during controlled assign and delete tests. Accept only when: Child records are retained, restricted, reassigned or deleted exactly as the approved lifecycle and audit policy specifies.

This is an unsafe or unsupported shortcut: Enable broad cascade delete on every relationship to keep the database tidy without evaluating retention and business impact. It fails to address Dataverse cascading relationship behavior. In this scenario: When an assigned account owner changes, associated records should follow a defined reassignment policy but remain on the old owner. The relevant technical behavior is: Dataverse relationship cascading rules can propagate defined operations to related rows, so deletion and reassignment policies must be deliberate. The appropriate implementation is: Configure relationship behavior and individual cascade actions to match retention, assignment, share and delete requirements; test them on sample records. Independent validation: Inspect relationship cascade settings and compare before-and-after parent and child records during controlled assign and delete tests. Accept only when: Child records are retained, restricted, reassigned or deleted exactly as the approved lifecycle and audit policy specifies.

This response applies to the different subject of One-to-many lookup relationship design, rather than directly to Dataverse cascading relationship behavior: Model the one-to-many relationship using an appropriate lookup on the many-side table and enforce required references where business rules demand them.. In this scenario: When an assigned account owner changes, associated records should follow a defined reassignment policy but remain on the old owner. The relevant technical behavior is: Dataverse relationship cascading rules can propagate defined operations to related rows, so deletion and reassignment policies must be deliberate. The appropriate implementation is: Configure relationship behavior and individual cascade actions to match retention, assignment, share and delete requirements; test them on sample records. Independent validation: Inspect relationship cascade settings and compare before-and-after parent and child records during controlled assign and delete tests. Accept only when: Child records are retained, restricted, reassigned or deleted exactly as the approved lifecycle and audit policy specifies.

This response applies to the different subject of Alternate keys and Dataverse migration integrity, rather than directly to Dataverse cascading relationship behavior: Review key status, source key uniqueness, upsert mappings and row counts before and after a repeated sample migration.. In this scenario: When an assigned account owner changes, associated records should follow a defined reassignment policy but remain on the old owner. The relevant technical behavior is: Dataverse relationship cascading rules can propagate defined operations to related rows, so deletion and reassignment policies must be deliberate. The appropriate implementation is: Configure relationship behavior and individual cascade actions to match retention, assignment, share and delete requirements; test them on sample records. Independent validation: Inspect relationship cascade settings and compare before-and-after parent and child records during controlled assign and delete tests. Accept only when: Child records are retained, restricted, reassigned or deleted exactly as the approved lifecycle and audit policy specifies.