DP-900 Identify considerations practice questions
7-day money-back guarantee — full refund within 7 days of purchase if you've completed under 20% of the questions. See pricing →
Certifications Tools Flashcards Career Paths Exam Guides Blog Pricing For Teams About
Try 20 questions free →

DP-900 Identify considerations for relational data on Azure: 260 practice questions

DP-900 260 questions 12 shown free

12 of the 260 Identify considerations for relational data on Azure questions in the Certsqill DP-900 bank, shown in full below. Each one carries an explanation for every option, not just the correct one — the wrong answers are where the marks go.

Preparing for DP-900? Take the free 5-min readiness check →

1. Azure SQL Database: Which Azure option best fits?

Medium
Your logistics company needs a relational database that uses the SQL Server database engine. Microsoft must manage the underlying infrastructure, operating system, and database platform, while developers retain responsibility for schemas, permissions, queries, and application data. Which Azure option best fits?
  1. Blob Storage
    Blob Storage provides object storage, not a managed relational database using the SQL Server engine.
  2. Azure Database for PostgreSQL Flexible Server
    PostgreSQL Flexible Server is managed, but it uses the PostgreSQL engine rather than the required SQL Server engine.
  3. Azure SQL Database ✓
    Azure SQL Database is a managed relational PaaS service based on the SQL Server engine, while customers manage schemas, access, queries, and data.
  4. SQL Server on an Azure virtual machine
    A SQL Server virtual machine provides guest operating-system and SQL instance control, leaving more infrastructure and maintenance responsibility with the customer.
The trap
Object storage does not provide relational schemas and queries. Managed scope does not establish database-engine compatibility. A VM does not provide the requested managed operating-system boundary.

Azure SQL Database provides a managed relational SQL Server platform without customer operating-system management.

2. A row represents one record: Which statement is correct?

Easy
A software company stores customer records in a relational table. Each record contains a customer identifier, name, and email address. The team asks what a row represents compared with a column. Which statement is correct?
  1. A column represents one complete customer record.
    A column represents one attribute across records, such as email address, rather than one complete customer.
  2. A row represents one record, and a column represents an attribute. ✓
    Relational tables organize records as rows and named attributes, with defined types, as columns.
  3. A row represents one attribute shared by every customer.
    A row represents one record, while an attribute shared across records is represented by a column.
  4. A column represents a separate database for each customer.
    A column is an attribute within one table, not a separate database or storage boundary.
The trap
This reverses row and column meanings. This confuses table structure with database boundaries. This assigns column meaning to a row.

Rows are records; columns are named attributes describing those records.

3. Azure SQL Managed Instance: Which service is the most appropriate starting choice?

Medium
A college is moving an existing SQL Server workload to Azure. The application depends on instance-level compatibility and SQL Server Agent jobs, but the college does not require guest operating-system customization. Which service is the most appropriate starting choice?
  1. Azure Database for PostgreSQL Flexible Server
    PostgreSQL Flexible Server supports a different open-source engine and does not provide SQL Server compatibility.
  2. SQL Server on an Azure virtual machine
    A virtual machine provides instance and operating-system control, but exceeds the stated need for managed instance compatibility.
  3. Azure SQL Database
    Azure SQL Database is managed database PaaS, but its database scope does not provide the requested instance-level compatibility.
  4. Azure SQL Managed Instance ✓
    Managed Instance offers managed service scope with high SQL Server compatibility and many instance-level capabilities.
The trap
Engine compatibility is decisive here. This overlooks the stated instance-level requirement. This adds guest-management responsibility without requirement.

Managed Instance combines managed operations with broader SQL Server instance compatibility than SQL Database.

4. Primary key: Which relational concept directly enforces this requirement?

Medium
A media studio has a table of video assets. The business requires every asset identifier to identify exactly one row and never be missing. Which relational concept directly enforces this requirement?
  1. View
    A view is a named query presentation and does not inherently enforce unique, non-null row identifiers.
  2. Index
    An index can accelerate suitable access patterns, but it is not the direct relational identity constraint.
  3. Primary key ✓
    A primary key uniquely identifies each row and does not permit null values for the key.
  4. Foreign key
    A foreign key references values in another table and primarily supports referential integrity between related records.
The trap
This addresses relationships, not direct row identity. This confuses presentation with constraint enforcement. This confuses access support with key semantics.

A primary key enforces unique, non-null identification for each relational row.

5. SQL Server on an Azure virtual machine: Which approach fits?

Hard
Your retailer must run a licensed SQL Server application in Azure. The application requires installing a custom operating-system component and changing guest OS settings. The team accepts responsibility for maintaining that operating system and SQL Server instance. Which approach fits?
  1. SQL Server on an Azure virtual machine ✓
    SQL Server on an Azure virtual machine provides guest OS and SQL instance control, with greater management responsibility.
  2. Azure SQL Managed Instance
    Managed Instance provides broader SQL compatibility, but customers still do not administer its guest operating system.
  3. Azure Database for MySQL Flexible Server
    MySQL Flexible Server is a managed different-engine service and does not provide SQL Server guest operating-system control.
  4. Azure SQL Database
    Azure SQL Database does not provide customer control of the guest operating system or arbitrary operating-system components.
The trap
The requirement explicitly needs guest OS control. This fails both engine and control requirements. Instance compatibility is not guest OS administration.

A SQL Server virtual machine is appropriate when guest OS customization and instance control are required.

6. Unique visit-service combinations: What does this choice provide?

Medium
A clinic records services delivered during each patient visit. A patient can receive the same service on many dates, and a visit can include multiple services. The designer proposes a composite primary key made from VisitID and ServiceID. What does this choice provide?
  1. Guaranteed faster performance for every query
    A key may support access through an index, but no key guarantees improvement for every query.
  2. Unique visit-service combinations ✓
    The composite key makes each combination of VisitID and ServiceID unique and identifies each junction-table row.
  3. A foreign-key relationship to every referenced table
    A composite primary key identifies rows; separate foreign-key constraints are needed to enforce references.
  4. Automatic enforcement of every clinical business rule
    A key enforces its defined uniqueness and nullability rules, not every separate business or clinical requirement.
The trap
This makes an unsupported universal performance claim. Key identity does not automatically create references. This overstates what primary keys enforce.

The composite key uniquely identifies each visit-and-service pairing in the junction table.

7. Managed database PaaS: Which responsibility model best describes this requirement?

Easy
An energy provider wants a managed relational database service. The team wants Microsoft to handle underlying infrastructure and configured maintenance, while the team manages database permissions, data, and workload design. Which responsibility model best describes this requirement?
  1. Database analyst role
    A role describes a person’s work, not the cloud responsibility model for operating a database service.
  2. Managed database PaaS ✓
    A managed database PaaS service handles underlying platform responsibilities while customers manage data, access, and workload design.
  3. File storage service
    File storage provides shared files rather than managed relational database engines, schemas, queries, and constraints.
  4. Self-managed database on IaaS
    IaaS provides infrastructure, but customers retain substantially more responsibility for the guest operating system and database environment.
The trap
This confuses organizational roles with service models. This assigns too much platform responsibility to the team. Storage services do not replace relational database services.

Managed database PaaS delegates platform operations while customers retain data and workload responsibilities.

8. A nullable foreign key from Invoices.CustomerID: Which design directly supports this relationship and permits

Medium
The Customers table has a primary key named CustomerID. A finance team has Customers and Invoices tables. Each invoice must reference an existing customer, although some draft invoices may temporarily have no customer assigned. Which design directly supports this relationship and permits the stated draft condition?
  1. A unique index on Customers.CustomerID
    A unique index supports uniqueness on the customer side but does not require invoice references to be valid.
  2. A primary key on Invoices.CustomerID
    A primary key identifies invoice rows but does not make Invoices.CustomerID reference Customers.CustomerID.
  3. A nullable foreign key from Invoices.CustomerID to Customers.CustomerID ✓
    The nullable foreign key permits drafts without a customer while requiring every supplied CustomerID to reference the Customers primary key.
  4. A view joining Customers and Invoices
    A view can present related data but does not enforce valid customer references when invoice rows are changed.
The trap
Uniqueness alone is not referential integrity. Row identity is not the required relationship. A query presentation does not enforce the relationship.

A nullable foreign key enforces valid supplied customer references while allowing unassigned draft invoices.

9. Azure SQL Managed Instance: The exhibit compares options.

Medium
An online store requires SQL Server Agent jobs and instance-level compatibility, but the team does not want to manage a guest operating system. The exhibit compares options.
  1. Azure Database for MySQL Flexible Server
    Flexible Server is a managed MySQL service, so it cannot provide SQL Server Agent compatibility.
  2. Azure SQL Database
    Azure SQL Database is managed database scope, but it does not provide SQL Server Agent instance features.
  3. Azure SQL Managed Instance ✓
    Managed Instance supplies managed instance scope and supports many SQL Server instance-level features, including SQL Server Agent.
  4. SQL Server on an Azure virtual machine
    A virtual machine supports SQL Server Agent and broad control, but requires guest operating-system administration.
The trap
The required engine is SQL Server, not MySQL. Database scope is narrower than the required instance capability. It satisfies compatibility while adding unwanted operating-system management.

Managed Instance provides instance-level SQL Server compatibility without requiring guest operating-system administration.

10. A one-to-many relationship: Which relationship best describes these tables?

Medium
A nonprofit stores donors and their donations. Each donor may make several donations, while every donation belongs to one donor. Which relationship best describes these tables?
  1. A junction table
    A junction table normally represents many-to-many associations, not repeated donations belonging to one donor.
  2. One-to-one relationship
    A one-to-one relationship allows each donor and donation to match only one counterpart.
  3. A one-to-many relationship ✓
    One donor can relate to many donations, with each donation referencing one donor through a foreign key.
  4. A many-to-many relationship
    Many-to-many would allow each donation to belong to multiple donors, unlike the stated ownership.
The trap
Each donation has exactly one donor. The relationship has one repeating side, not two. Donors can have multiple donations.

The donor is the one side, and donations form the many side of the relationship.

11. Size shared pool capacity for aggregate demand rather than: Select TWO suitable choices.

Medium
A data team runs several Azure SQL databases for separate applications. Their workloads peak at different times, and they want shared capacity without combining schemas or databases. Select TWO suitable choices.

Select two. More than one option is correct — every correct one is ticked below.

  1. Merge all application schemas into one database
    Merging schemas changes the separate-database design and is unnecessary for sharing elastic-pool resources.
  2. Size shared pool capacity for aggregate demand rather than every peak ✓
    Sizing shared pool capacity for aggregate demand uses the pool model instead of provisioning each separate database for its individual peak.
  3. Move every database to SQL Server on an Azure virtual machine
    A virtual machine provides SQL Server instance control but does not directly provide elastic-pool resource sharing.
  4. Replace the databases with MySQL Flexible Server instances
    MySQL Flexible Server uses a different database engine and does not provide the Azure SQL elastic-pool model for these databases.
  5. Use one elastic pool for suitable databases with offset peaks ✓
    An elastic pool provides shared resources for suitable Azure SQL databases whose demand varies over time.
The trap
Elastic pools share resources without physically merging databases. More infrastructure control does not solve shared variable demand. Changing engines is not a resource-sharing solution.

Elastic pools share capacity across separate Azure SQL databases with offset or variable demand.

12. A junction table: Which relational structure represents this association?

Easy
A manufacturer allows each product to use many materials, and each material can appear in many products. Which relational structure represents this association?
  1. A view
    A view presents query results but does not itself model repeated associations between products and materials.
  2. A primary key constraint
    A primary key uniquely identifies rows but does not alone represent many-to-many associations.
  3. A junction table ✓
    A junction table stores product-material pairs, allowing multiple matches on both sides of the relationship.
  4. A foreign key
    One foreign key commonly supports a one-to-many reference, not both sides having many matches.
The trap
A single reference cannot represent all pairings. Presentation logic is not relationship structure. Uniqueness does not model all product-material pairings.

A junction table stores each product-material pairing and represents many-to-many relationships.

248 more Identify considerations for relational data on Azure questions

The remaining 248 questions in this domain are part of the full DP-900 bank — 1080 questions, every option explained. Start with the free five-minute check and see your score per domain.

Test your DP-900 readiness — free

Other DP-900 domains

Part of the Certsqill DP-900 question bank · Identify considerations for relational data on Azure · Every answer, right and wrong, comes with its own explanation.