I85PREP
⌘ K
Informatica MDM SaaS Foundation study materials
Informatica MDM SaaS Foundation study resources

Informatica MDM SaaS Foundation practice questions

One question at a time. Build your Informatica MDM SaaS Foundation understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1MDM & 360 Applications

In Informatica MDM SaaS, what is the primary purpose of a Business Entity 360 application?

  1. To configure the trust settings that resolve conflicting attribute values
  2. To provide a consolidated, role-specific view of a master record with related interactions and attributes Correct answer.
  3. To schedule batch jobs that load source data into the staging tables
  4. To define the match and merge rules that create the golden record

Explanation

A 360 application surfaces the mastered record together with related data so business users can act on a complete view. Match rules, trust settings, and load jobs belong to the mastering pipeline rather than to the presentation layer.

Question 2MDM & 360 Applications

Which capability lets a SaaS MDM deployment expose master data to downstream systems through a governed, versioned interface?

  1. A published API or data service built on the business entity model Correct answer.
  2. A scheduled email report of golden records
  3. A direct SQL connection into the operational MDM database
  4. A manual CSV export triggered by an administrator

Explanation

SaaS MDM exposes master data through governed, versioned APIs and data services modeled on business entities. Direct database access and ad hoc exports bypass the governance and contract that downstream consumers rely on.

Question 3MDM & 360 Applications

A data steward opens a 360 application and sees two records that appear to describe the same customer. What is the most appropriate first action within the 360 experience?

  1. Ignore the duplicate until the next scheduled batch run
  2. Delete one of the records manually from the source system
  3. Review the candidate match and submit a merge or unmerge decision through the stewardship workflow Correct answer.
  4. Change the match rule thresholds in production to force a merge

Explanation

The 360 application is designed to route suspected duplicates into a stewardship workflow where a human reviews and decides. Editing source systems, altering production match rules, or deferring indefinitely all bypass controlled data governance.

Question 4MDM & 360 Applications

Which statement best describes the relationship between a business entity and its business entity services in MDM SaaS?

  1. Business entity services are the read and write operations exposed for a business entity model Correct answer.
  2. Business entity services replace the need for a data model entirely
  3. Each business entity can expose exactly one service operation
  4. A business entity is created automatically whenever any service is invoked

Explanation

A business entity defines the model, and the services are the operations exposed against that model for consumers. Services depend on the model rather than replacing it, and an entity can expose multiple operations.

Question 5MDM & 360 Applications

A business user needs a dashboard that shows a customer's open orders alongside the mastered customer profile. Which MDM SaaS capability is intended for this requirement?

  1. A 360 application that aggregates related business data around the master record Correct answer.
  2. A trust score that ranks the customer profile above the order data
  3. A match rule that links orders to customers during the batch load
  4. A hierarchy definition that nests orders under the customer

Explanation

360 applications are built to present the master record together with related business data from connected systems. Match rules, trust scores, and hierarchies serve mastering and relationship modeling rather than cross-system presentation.

Question 6MDM & 360 Applications

What distinguishes a hierarchy in MDM SaaS from a simple reference relationship between two records?

  1. A hierarchy is the mechanism that assigns trust scores to attributes
  2. A hierarchy stores a copy of every source record for audit purposes
  3. A hierarchy is only a label applied to a single record for reporting
  4. A hierarchy models multi-level parent-child structure with levels and validity over time Correct answer.

Explanation

Hierarchies represent structured, often multi-level relationships such as organizational rollups, with defined levels and effective dates. Labels, audit copies, and trust scoring are separate concepts in the platform.

Question 7MDM & 360 Applications

An organization wants different departments to see only the portions of the 360 view relevant to their role. Which MDM SaaS concept supports this?

  1. Source system credentials embedded in the 360 application
  2. Role-based access and configurable 360 layouts per user group Correct answer.
  3. A single global layout shared by every user with no restrictions
  4. Disabling the stewardship workflow for non-admin users

Explanation

360 applications support role-based access and layout configuration so each user group sees the data and panels relevant to its responsibilities. A single unrestricted layout, embedded credentials, and disabling workflows do not achieve controlled, role-specific views.

Question 8MDM & 360 Applications

Which outcome indicates that a 360 application has been designed effectively for its users?

  1. Administrators rebuild the layout manually for every individual user
  2. Users can resolve data issues and complete their tasks without leaving the 360 experience Correct answer.
  3. The application displays every attribute from every source system by default
  4. Users must export data to spreadsheets to complete most of their work

Explanation

An effective 360 application keeps users in context so they can review, act, and resolve issues in one place. Forcing exports, per-user rebuilds, or unfiltered attribute dumps signals poor design.

Question 9MDM & 360 Applications

In MDM SaaS, what is the role of the data steward within the 360 application?

  1. To review, correct, and approve master data through governed tasks and workflows Correct answer.
  2. To manage the network configuration of the SaaS tenant
  3. To design the physical database schema for the MDM repository
  4. To write the ETL mappings that ingest source records

Explanation

Data stewards use the 360 application to review exceptions, correct attributes, and approve changes through governed workflows. Schema design, network administration, and ETL development are distinct technical roles.

Question 10MDM & 360 Applications

A retailer wants to search all master records for a customer by partial name and phone number from within the 360 application. Which capability addresses this?

  1. Configurable search with indexed and fuzzy matching across entity attributes Correct answer.
  2. A trust score threshold applied to the phone attribute
  3. A batch match job that runs overnight and emails results
  4. A hierarchy rollup that groups customers by region

Explanation

360 applications provide configurable search, including fuzzy and indexed matching, so users can locate records interactively. Batch matching, hierarchy rollups, and trust thresholds do not deliver interactive record lookup.

Question 11MDM & 360 Applications

What is the purpose of a match rule set in the context of feeding a 360 application?

  1. To schedule when the 360 application refreshes its dashboards
  2. To identify which source records should consolidate into a single master record Correct answer.
  3. To define the API version exposed to downstream consumers
  4. To control which panels appear on the 360 layout for each role

Explanation

Match rule sets determine which records are considered the same entity and should be consolidated into a master record. Layout configuration, API versioning, and dashboard refresh scheduling are separate concerns.

Question 12MDM & 360 Applications

A team wants to add a custom attribute to a business entity used by a 360 application. What is the appropriate approach in MDM SaaS?

  1. Extend the business entity model through supported configuration and publish the change to the 360 layout Correct answer.
  2. Create a separate shadow entity and join it manually in every report
  3. Store the attribute only in the source system and never master it
  4. Modify the underlying database table directly with a DDL script

Explanation

Model extensions are made through supported configuration so the change is governed and can be surfaced in the 360 layout. Direct DDL, shadow entities, and leaving the attribute unmastered all break the managed model.

Question 13MDM & 360 Applications

Which statement accurately describes how a 360 application consumes mastered data compared with source data?

  1. It shows only raw source records and hides the mastered record
  2. It presents the mastered record while allowing drill-through to contributing source records Correct answer.
  3. It permanently discards source records once a master is created
  4. It requires users to query each source system separately

Explanation

A 360 view centers on the mastered record but preserves lineage by allowing drill-through to the contributing sources. Hiding the master, discarding sources, or forcing separate queries defeats the purpose of consolidation.

Question 14MDM & 360 Applications

What does a trust score contribute to the MDM SaaS mastering process?

  1. It sets the retention period for audit history
  2. It ranks competing attribute values so survivorship can select the most reliable one Correct answer.
  3. It determines which users may view the 360 application
  4. It controls the frequency of batch ingestion jobs

Explanation

Trust scores express confidence in attribute values from different sources and guide survivorship when values conflict. Access control, audit retention, and job frequency are governed by other settings.

Question 15MDM & 360 Applications

A customer service representative needs to log a complaint against a master customer record and have it visible to other teams. Which MDM SaaS feature best supports this?

  1. Interaction or activity capture attached to the master record within the 360 application Correct answer.
  2. A hierarchy level that stores complaint text
  3. A trust score applied to the complaint field
  4. A new match rule that links complaints to customers

Explanation

360 applications support capturing interactions and activities against the master record so they are shared across teams. Match rules, hierarchy levels, and trust scores are not storage mechanisms for user-entered interactions.

Question 16MDM & 360 Applications

Which consideration is most important when designing a 360 layout for executive users versus operational users?

  1. Restricting operational users from seeing any master data
  2. Tailoring panels and metrics to each group's decisions while sharing the same governed master data Correct answer.
  3. Giving executives a separate, ungoverned copy of the data
  4. Building one layout and requiring all users to adapt to it

Explanation

Layouts should be tailored to the decisions each audience makes while drawing on the same governed master data. Separate ungoverned copies, blanket restrictions, and a single rigid layout all undermine the platform's value.

Question 17MDM & 360 Applications

In MDM SaaS, how does a business entity service typically differ from a direct table query?

  1. The service enforces model rules and governance, while a table query bypasses them Correct answer.
  2. The service is available only during business hours, while a table query is always available
  3. The service is read-only, while a table query supports writes
  4. The service returns only counts, while a table query returns full records

Explanation

Business entity services apply the model's rules, validation, and governance as data is read or written. Direct table queries skip those controls, and services are not limited to counts, read-only access, or business hours.

Question 18MDM & 360 Applications

What is a key benefit of using a SaaS MDM 360 application rather than building a custom portal on the operational database?

  1. It guarantees that source systems never contain duplicates
  2. It delivers governed, upgradable master data experiences without custom maintenance of the core Correct answer.
  3. It removes the need to define any data model for the entity
  4. It eliminates the need for stewardship review entirely

Explanation

A SaaS 360 application provides governed, continuously upgraded experiences while the vendor maintains the core. It does not remove the need for modeling, prevent source duplicates, or eliminate stewardship.

Question 19MDM & 360 Applications

Which MDM SaaS feature allows a user to see how a golden record's attribute value was derived?

  1. Lineage and source drill-through from the mastered attribute to its contributing records Correct answer.
  2. A scheduled batch job that recomputes the attribute
  3. A role assignment that grants edit rights
  4. A hierarchy rollup of the attribute across regions

Explanation

Lineage and drill-through show which source records contributed a value and how it was selected. Hierarchies, role assignments, and batch recomputation do not explain derivation to the user.

Question 20MDM & 360 Applications

A business entity is configured with a relationship to another entity. What does this enable within the 360 application?

  1. Displaying and navigating related records of the other entity from the master record Correct answer.
  2. Removing the requirement for role-based access controls
  3. Replacing the need for a match rule between the entities
  4. Automatically merging the two entities into one master record

Explanation

Relationships let the 360 application surface and navigate related records, such as a customer's linked accounts. They do not merge entities, substitute for match rules, or affect access controls.

Question 21MDM & 360 Applications

What is the most appropriate use of a hierarchy in a 360 application for a sales organization?

  1. Defining which users can log in to the tenant
  2. Replacing the match rule set used to consolidate accounts
  3. Storing the audit history of every attribute change
  4. Rolling up accounts or customers under managers and regions for aggregated visibility Correct answer.

Explanation

Hierarchies support rollups such as accounts under managers and regions, giving aggregated visibility in the 360 view. Audit history, authentication, and matching are handled by other platform capabilities.

Question 22MDM & 360 Applications

Which scenario best justifies extending a 360 application with a custom panel?

  1. Source data has not yet been modeled in the business entity
  2. An administrator prefers a different color scheme
  3. Users need a role-specific summary of related data that is not available in the standard panels Correct answer.
  4. The standard panels already meet every user requirement

Explanation

Custom panels are justified when standard panels cannot present role-specific related data users need. Cosmetic preferences and unmodeled source data are not valid reasons to build custom panels.

Question 23MDM & 360 Applications

In MDM SaaS, which capability helps ensure that a 360 application shows current data after source systems update their records?

  1. Configured data ingestion and refresh processes that update the mastered record Correct answer.
  2. Periodic deletion and recreation of the business entity
  3. Disabling source system updates to keep data stable
  4. Manual re-entry of each changed value by a steward

Explanation

Ingestion and refresh processes propagate source changes into the mastered record so the 360 view stays current. Manual re-entry, entity recreation, and blocking source updates are impractical and harmful.

Question 24MDM & 360 Applications

What distinguishes a 360 application's read model from the MDM operational store?

  1. The read model contains only unmastered raw source data
  2. The read model is used exclusively for batch matching
  3. The read model permanently replaces the operational store
  4. The read model is optimized for fast, role-specific presentation of consolidated data Correct answer.

Explanation

The 360 read model is tuned for fast presentation of consolidated, role-specific data while the operational store remains the system of record for mastering. It does not replace the store, hold only raw data, or perform matching.

Question 25MDM & 360 Applications

A steward identifies that a golden record has an incorrect phone number surviving from a low-quality source. Which action best reflects governed remediation in MDM SaaS?

  1. Edit the value directly in the source database without recording the change
  2. Correct the value through the stewardship workflow and adjust trust or survivorship rules as appropriate Correct answer.
  3. Disable the source system from all future ingestion
  4. Lower the match threshold until the record splits

Explanation

Governed remediation corrects the value through the workflow and addresses the root cause by reviewing trust and survivorship rules. Direct source edits, disabling ingestion, and misusing match thresholds do not fix the underlying governance issue.

Question 26MDM & 360 Applications

In MDM SaaS, what is the primary purpose of a business entity model within a 360 application?

  1. To physically store raw source extracts before any standardization occurs
  2. To schedule the batch jobs that load reference data into the data lake
  3. To encrypt sensitive attributes while they are in transit between systems
  4. To define the logical structure, attributes, and relationships that the 360 view presents to users Correct answer.

Explanation

A business entity model describes the logical shape of a master domain: its attributes, relationships, and constraints. The 360 application is rendered against this model, so it determines what users can view and interact with. It is a definition layer, not a storage or transport mechanism.

Question 27MDM & 360 Applications

A company wants a single 360 view that shows a customer's core attributes alongside their recent orders and open service cases. Which MDM SaaS concept supports bringing these related domain records together in one view?

  1. Relationship-driven related records surfaced in the 360 layout Correct answer.
  2. A separate match rule set per downstream application
  3. A manual spreadsheet exported nightly by the steward
  4. A standalone reference data set copied into each source system

Explanation

The 360 application composes a view from the master record plus related records reached through defined relationships. This lets core attributes and transactional context such as orders and cases appear together. Reference data and match rule sets serve different purposes and do not compose the view.

Question 28MDM & 360 Applications

What best describes the role of the MDM SaaS data model in governing which attributes appear on a 360 record page?

  1. Attributes defined on the entity become available for display and are governed centrally by the model Correct answer.
  2. Attributes are chosen at runtime by each end user without any configuration
  3. Attributes appear automatically whenever a source system sends a new column
  4. Attributes are fixed at installation and can never be changed afterward

Explanation

The data model is the central definition of entity attributes, and the 360 page draws from it. Changes are made through model configuration rather than by ad hoc source columns. This keeps the view consistent and governed across consumers.

Question 29MDM & 360 Applications

An administrator needs to give a new group of regional analysts access to the customer 360 application with read-only rights. Which MDM SaaS mechanism is designed for this?

  1. Role-based access control assigning the analysts a read-only role Correct answer.
  2. A hierarchy definition that groups customers by region
  3. A new match rule that limits which records are merged
  4. A survivorship rule that prefers regional source values

Explanation

Access to 360 applications is governed by roles and permissions assigned to users or groups. A read-only role grants viewing without edit rights. Match rules, hierarchies, and survivorship rules affect data behavior rather than access control.

Question 30MDM & 360 Applications

Which statement best captures how a 360 application differs from a source system's own user interface?

  1. It only shows data that was manually entered by data stewards
  2. It presents consolidated master data across sources rather than a single system's local records Correct answer.
  3. It displays raw unstandardized values exactly as each source sent them
  4. It replaces the need for any source system to store its own transactional data

Explanation

A 360 application is built on mastered, consolidated data spanning multiple sources. A source system's UI shows only its own local records. The 360 view therefore offers a cross-system perspective that no single source provides.

Question 31MDM & 360 Applications

A product manager asks what 'golden record' means in the context of a 360 application. Which answer is most accurate?

  1. The record with the most attributes populated, chosen regardless of source quality
  2. The oldest record in the system, retained for audit purposes only
  3. A temporary staging row that is deleted after each load
  4. The single consolidated master record that the 360 view presents after matching and survivorship Correct answer.

Explanation

The golden record is the consolidated, trusted version of an entity produced by matching and survivorship. The 360 application presents this record to users. It is not simply the oldest or the widest record, and it is not a transient staging row.

Question 32MDM & 360 Applications

Which capability lets users of a 360 application move from a summary view of a customer to the individual source records that contributed to it?

  1. Creating a new business entity for each source system
  2. Disabling survivorship so all values display simultaneously
  3. Drill-down to contributing source records from the consolidated view Correct answer.
  4. Exporting the entire domain to a flat file for offline review

Explanation

360 applications commonly support drill-down so users can inspect the source records behind a consolidated value. This supports verification and stewardship. Exporting, disabling survivorship, or duplicating entities do not provide this traceability.

Question 33MDM & 360 Applications

What is the main benefit of configuring a 360 application with reusable layout templates across multiple business entities?

  1. Consistent user experience and lower configuration effort for each new entity Correct answer.
  2. Elimination of the need for any access control configuration
  3. Guaranteed automatic matching of records across all entities
  4. Reduced storage cost because templates compress the data

Explanation

Layout templates let teams reuse a proven page structure across entities, which speeds configuration and keeps the user experience consistent. Templates do not perform matching, compress data, or remove the need for security configuration.

Question 34MDM & 360 Applications

A sales operations team wants a 360 view where account managers see a customer's open opportunities alongside the mastered account profile. Which design approach fits best?

  1. Store opportunity data as a custom attribute on the customer entity
  2. Replace the customer entity with an opportunity entity
  3. Create a separate 360 application per account manager
  4. Add a related-records panel driven by a relationship to the opportunity domain Correct answer.

Explanation

Related records are surfaced through relationships, so a panel driven by the opportunity relationship keeps the account profile intact while adding context. Per-user applications, attribute flattening, or entity replacement all distort the model.

Question 35MDM & 360 Applications

A steward needs to correct a misspelled legal name on a golden record and ensure the change persists even after the next source load. Which approach is most appropriate in MDM SaaS?

  1. Override the attribute value on the master record so survivorship respects the manual correction Correct answer.
  2. Delete the source record that supplied the incorrect value
  3. Disable matching for the entity so no further updates occur
  4. Edit the value directly in the source system and wait for the next load

Explanation

Manual overrides on the master record are designed to persist and take precedence over automated survivorship. Editing the source alone may be overwritten or reintroduced by later loads. Deleting records or disabling matching damages data quality and identity resolution.

Question 36MDM & 360 Applications

An organization wants the 360 application to show a computed customer lifetime value that combines order totals from two source systems. Which approach is most suitable?

  1. Enter the lifetime value manually for each customer during onboarding
  2. Ask each source system to send a precomputed lifetime value field and pick one by survivorship
  3. Define a calculated attribute that derives the value from related records at view time Correct answer.
  4. Create a separate entity for lifetime value with no relationship to the customer

Explanation

A calculated attribute derives values from related data, keeping the metric consistent as underlying records change. Relying on competing source fields invites survivorship conflicts, and manual entry does not scale. An unrelated entity would not connect the metric to the customer.

Question 37MDM & 360 Applications

A 360 application must display a customer's segment, which is maintained as a shared code list across many systems. Which MDM SaaS construct should supply this value?

  1. A match rule set that links customers to segments
  2. A reference data set that manages the code list and its mappings Correct answer.
  3. A hierarchy that orders customers by revenue
  4. A survivorship rule that averages segment codes

Explanation

Reference data manages shared code lists and their cross-system mappings so values stay consistent. Match rules, hierarchies, and survivorship rules address identity, structure, and value selection rather than code list management.

Question 38MDM & 360 Applications

A team notices that the 360 application shows a customer's address from an outdated source even though a newer, more reliable source supplies a different address. What should they review first?

  1. The layout template assigned to the 360 page
  2. The survivorship rules and trust settings that determine which source value wins Correct answer.
  3. The frequency of hierarchy rebuilds
  4. The number of users assigned to the analyst role

Explanation

When an unexpected source value survives, the survivorship rules and trust configuration are the primary cause. Layout, user roles, and hierarchy rebuilds do not decide which attribute value becomes the golden value.

Question 39MDM & 360 Applications

A business wants the 360 application to highlight duplicate-looking customer records that were not automatically merged. Which MDM SaaS feature best supports reviewing these potential matches?

  1. A calculated attribute that sums record counts
  2. A suspect or potential-match review queue for steward adjudication Correct answer.
  3. A reference data set of customer status codes
  4. A hierarchy that nests customers under accounts

Explanation

Suspect records are potential matches that fall below automatic merge thresholds and are routed for steward review. This lets humans confirm or reject links. Calculated attributes, hierarchies, and reference data do not perform match adjudication.

Question 40MDM & 360 Applications

A 360 application must show only active customers by default while still allowing analysts to view inactive ones on demand. Which design choice best meets this requirement?

  1. Delete inactive customers from the master store
  2. Create a second entity that holds only active customers
  3. Apply a default filter on status with an option for users to clear it Correct answer.
  4. Restrict the application so inactive records are never loaded

Explanation

A default filter narrows the initial view while preserving access to the full data set when the filter is removed. Deleting records, splitting entities, or blocking loads would lose data and complicate governance.

Question 41MDM & 360 Applications

A customer service team wants to record a short free-text note on a master customer that persists with the record and is visible to other teams. Which approach is most appropriate?

  1. Use a notes or interaction capability attached to the master record Correct answer.
  2. Send the note through the match rule configuration
  3. Overwrite the customer's legal name field with the note
  4. Add the note to the source system's order comment field

Explanation

Notes and interactions are designed to attach contextual commentary to a master record without altering core attributes. Overwriting attributes corrupts data, and source-side or match-rule workarounds do not persist as record-level notes.

Question 42MDM & 360 Applications

A global company needs the 360 view to show customer names in the local language for regional users while keeping a canonical name for corporate reporting. Which design is most appropriate?

  1. Let each region overwrite the canonical name with its local value
  2. Store only the local-language name and translate it during reporting
  3. Use a single name attribute and rely on users to interpret it
  4. Model separate localized and canonical name attributes and present each to the relevant audience Correct answer.

Explanation

Modeling distinct localized and canonical attributes preserves both regional usability and consistent corporate reporting. Overwriting or collapsing into one field creates conflicts, and runtime translation of a single stored value is unreliable.

Question 43MDM & 360 Applications

A 360 page is slow to load because it retrieves many related records for each customer. Which optimization is most appropriate?

  1. Limit the related-records panel to a summarized or paged subset with drill-down Correct answer.
  2. Disable access control to reduce processing
  3. Remove all relationships from the entity model
  4. Convert every related record into a separate entity

Explanation

Paging or summarizing related records keeps the initial page responsive while preserving access through drill-down. Removing relationships, disabling security, or exploding entities harms the model and does not address performance cleanly.

Question 44MDM & 360 Applications

A business wants executives to see aggregated customer counts by region on the 360 landing page. Which MDM SaaS approach best supports this?

  1. Configure dashboard or summary widgets that aggregate over the mastered data Correct answer.
  2. Export all records to spreadsheets each morning
  3. Require executives to open each customer record individually
  4. Add a free-text notes field for regional totals

Explanation

Dashboard and summary widgets aggregate mastered data into high-level metrics suited to executive users. Manual record-by-record review, spreadsheet exports, and free-text notes do not provide reliable, current aggregates.

Question 45MDM & 360 Applications

A steward wants to understand why a particular customer record was linked to another during matching. Which information is most relevant to review?

  1. The number of dashboards configured for the entity
  2. The reference data set for country codes
  3. The layout template used by the 360 page
  4. The match rule and the attribute values that contributed to the match score Correct answer.

Explanation

Match decisions are driven by the configured match rules and the compared attribute values that produced the score. Layout, dashboards, and unrelated reference data do not explain why two records were linked.

Question 46MDM & 360 Applications

An organization needs the 360 application to reflect near-real-time updates from a high-volume source system. Which MDM SaaS capability is most relevant?

  1. A nightly full reload of the entire domain
  2. Disabling matching so loads complete faster
  3. Manual re-entry of changed records by stewards
  4. Incremental or event-driven ingestion that updates master records as changes arrive Correct answer.

Explanation

Incremental or event-driven ingestion propagates source changes promptly so the 360 view stays current. Full nightly reloads introduce latency, manual re-entry is unscalable, and disabling matching undermines data quality.

Question 47MDM & 360 Applications

A 360 application shows a customer's credit rating, which must be visible only to finance users. Which combination best enforces this requirement?

  1. A match rule that groups finance customers
  2. Attribute-level security combined with role-based access for finance users Correct answer.
  3. A hierarchy that places finance users under a region
  4. A default filter on the credit rating attribute

Explanation

Attribute-level security restricts sensitive fields, and role-based access limits them to the appropriate group. Filters, match rules, and hierarchies do not enforce field-level visibility for specific user groups.

Question 48MDM & 360 Applications

A team plans to extend the customer 360 application with a panel showing risk indicators computed from external data. What is the most important design consideration before building it?

  1. Confirming that the external data is integrated, governed, and refreshed through supported MDM processes Correct answer.
  2. Storing the risk indicators as free text in a notes field
  3. Granting every user edit rights to the risk indicators
  4. Ensuring the panel loads all external records at once for completeness

Explanation

Extensions should draw on governed, integrated data refreshed through supported processes so the panel is trustworthy and maintainable. Loading everything at once harms performance, broad edit rights create integrity risk, and free text cannot support computed indicators.

Question 49MDM & 360 Applications

Two source systems disagree on a customer's phone number, and neither is clearly more trustworthy. Which MDM SaaS strategy best resolves this for the 360 view?

  1. Always take the value from the system that loaded first
  2. Display both values and let each user choose
  3. Leave the attribute blank until sources agree
  4. Define survivorship rules with trust-based or recency-based precedence and route ambiguous cases to stewards Correct answer.

Explanation

Survivorship rules encode precedence such as trust or recency, and ambiguous cases can be escalated for steward review. Arbitrary first-loaded precedence is unreliable, user-level choice creates inconsistency, and blanking the field degrades the view.

Question 50MDM & 360 Applications

An architect must decide whether a new metric should be a stored attribute on the customer entity or a calculated attribute in the 360 application. Which consideration is most decisive?

  1. Whether the analyst role has more than ten users
  2. Whether the metric must be persisted for downstream consumers or derived on demand from related data Correct answer.
  3. Whether the 360 page uses a dark or light color theme
  4. Whether the metric name fits within the attribute label length

Explanation

The choice hinges on persistence and consumption needs: stored attributes suit downstream reuse, while calculated attributes suit on-demand derivation. Label length, theming, and user counts are irrelevant to this architectural decision.