100% Latest & Updated Microsoft DP-300 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 110
Three independently confirmed SQL platform issues require separate evidence checks. Case A: A service principal successfully obtains an Entra token but receives a database user-not-found error. Case B: A stored procedure works for its owner but fails on a permission check for an ordinary application user. Case C: A report service must read one approved view but currently has db_owner membership. Select exactly THREE distinct diagnostic checks, one for each case.
- EXECUTE AS USER or effective permissions test and failed statement context
- Connection error identity claim database name and principal mapping
- Logical-server Microsoft Entra administrator configuration and successful token-based sign-in
- sys.database_principals plus the authenticated identity and database context
- SQL login usage inventory and secret rotation audit trail
- sys.database_role_members and effective SELECT privileges on the reporting view
Explanation
Correct Answers
A:EXECUTE AS USER or effective permissions test and failed statement context directly tests the observation that a stored procedure works for its owner but fails on a permission check for an ordinary application user. It helps the team evaluate whether it should reproduce the statement under the calling principal's security context. The check has a boundary: Using the dbo context can hide access weaknesses seen by normal users.
D:sys.database_principals plus the authenticated identity and database context directly tests the observation that a service principal successfully obtains an Entra token but receives a database user-not-found error. It helps the team evaluate whether it should create a suitable contained database user FROM EXTERNAL PROVIDER with required privileges. The check has a boundary: Authentication alone does not convey table permissions.
F:sys.database_role_members and effective SELECT privileges on the reporting view directly tests the observation that a report service must read one approved view but currently has db_owner membership. It helps the team evaluate whether it should replace broad db_owner membership with a narrowly scoped GRANT SELECT on the view. The check has a boundary: View ownership chaining and underlying security context should still be reviewed.
Incorrect Answers
B:Connection error identity claim database name and principal mapping is appropriate for the separate condition that a managed identity reaches the SQL endpoint but a connection fails due to the wrong database principal or requested scope. The actual 3 cases are A: A service principal successfully obtains an Entra token but receives a database user-not-found error; B: A stored procedure works for its owner but fails on a permission check for an ordinary application user; C: A report service must read one approved view but currently has db_owner membership. This option is not the specific diagnostic evidence for any of those stated cases.
C:Logical-server Microsoft Entra administrator configuration and successful token-based sign-in is appropriate for the separate condition that an Azure SQL logical server requires central identity administration before Microsoft Entra database accounts can be provisioned. The actual 3 cases are A: A service principal successfully obtains an Entra token but receives a database user-not-found error; B: A stored procedure works for its owner but fails on a permission check for an ordinary application user; C: A report service must read one approved view but currently has db_owner membership. This option is not the specific diagnostic evidence for any of those stated cases.
E:SQL login usage inventory and secret rotation audit trail is appropriate for the separate condition that a legacy SQL application uses password credentials that need controlled rotation and secure storage. The actual 3 cases are A: A service principal successfully obtains an Entra token but receives a database user-not-found error; B: A stored procedure works for its owner but fails on a permission check for an ordinary application user; C: A report service must read one approved view but currently has db_owner membership. This option is not the specific diagnostic evidence for any of those stated cases.
Question 111
A Microsoft Azure SQL solution proposal begins with this condition: Several engineers need identical read-only data access without individually maintained GRANT statements. Which Azure SQL service or administration concept most precisely fits this situation?
- Group-based SQL database role
- Authentication troubleshooting using token
- Minimum object permission
- Role and permission audit
Explanation
Correct Answer
A:Group-based SQL database role matches the precise requirement: several engineers need identical read-only data access without individually maintained GRANT statements. Role-based grants simplify controlled shared access. Important scope limit: Directory group membership changes and existing sessions may affect effective access timing.
Incorrect Answers
B:Authentication troubleshooting using token applies when a managed identity reaches the SQL endpoint but a connection fails due to the wrong database principal or requested scope, not when several engineers need identical read-only data access without individually maintained GRANT statements.
C:Minimum object permission applies when a report service must read one approved view but currently has db_owner membership, not when several engineers need identical read-only data access without individually maintained GRANT statements.
D:Role and permission audit applies when a developer claims SELECT access but DENY and inherited role memberships produce an unexpected effective permission, not when several engineers need identical read-only data access without individually maintained GRANT statements.
Question 112
The data platform team is assessing this situation: A report service must read one approved view but currently has db_owner membership. Which Azure SQL service or administration concept most precisely fits this situation?
- Execute-as user diagnostics
- Minimum object permission
- SQL authentication policy
- Contained Entra database user
Explanation
Correct Answer
B:Minimum object permission matches the precise requirement: a report service must read one approved view but currently has db_owner membership. The report can read intended data without unrelated schema control. Important scope limit: View ownership chaining and underlying security context should still be reviewed.
Incorrect Answers
A:Execute-as user diagnostics applies when a stored procedure works for its owner but fails on a permission check for an ordinary application user, not when a report service must read one approved view but currently has db_owner membership.
C:SQL authentication policy applies when a legacy SQL application uses password credentials that need controlled rotation and secure storage, not when a report service must read one approved view but currently has db_owner membership.
D:Contained Entra database user applies when a service principal successfully obtains an Entra token but receives a database user-not-found error, not when a report service must read one approved view but currently has db_owner membership.
Question 113
A database architecture review reports the following requirement: An Azure SQL Database connection uses a contained database user and administrators expect it to appear in server-level logins. Which Azure SQL service or administration concept most precisely fits this situation?
- SQL authentication policy
- Role and permission audit
- Minimum object permission
- Contained SQL user versus server login
Explanation
Correct Answer
D:Contained SQL user versus server login matches the precise requirement: an Azure SQL Database connection uses a contained database user and administrators expect it to appear in server-level logins. Database identity management can occur independently of classic instance login mappings. Important scope limit: Database contained users are not portable to every SQL Server instance configuration unchanged.
Incorrect Answers
A:SQL authentication policy applies when a legacy SQL application uses password credentials that need controlled rotation and secure storage, not when an Azure SQL Database connection uses a contained database user and administrators expect it to appear in server-level logins.
B:Role and permission audit applies when a developer claims SELECT access but DENY and inherited role memberships produce an unexpected effective permission, not when an Azure SQL Database connection uses a contained database user and administrators expect it to appear in server-level logins.
C:Minimum object permission applies when a report service must read one approved view but currently has db_owner membership, not when an Azure SQL Database connection uses a contained database user and administrators expect it to appear in server-level logins.
Question 114
A Microsoft Azure SQL solution proposal begins with this condition: A managed identity reaches the SQL endpoint but a connection fails due to the wrong database principal or requested scope. Which Azure SQL service or administration concept most precisely fits this situation?
- Authentication troubleshooting using token
- Contained SQL user versus server login
- Execute-as user diagnostics
- Group-based SQL database role
Explanation
Correct Answer
A:Authentication troubleshooting using token matches the precise requirement: a managed identity reaches the SQL endpoint but a connection fails due to the wrong database principal or requested scope. The failure is isolated to token audience authentication or authorization. Important scope limit: Adding firewall access does not repair an incorrect database principal mapping.
Incorrect Answers
B:Contained SQL user versus server login applies when an Azure SQL Database connection uses a contained database user and administrators expect it to appear in server-level logins, not when a managed identity reaches the SQL endpoint but a connection fails due to the wrong database principal or requested scope.
C:Execute-as user diagnostics applies when a stored procedure works for its owner but fails on a permission check for an ordinary application user, not when a managed identity reaches the SQL endpoint but a connection fails due to the wrong database principal or requested scope.
D:Group-based SQL database role applies when several engineers need identical read-only data access without individually maintained GRANT statements, not when a managed identity reaches the SQL endpoint but a connection fails due to the wrong database principal or requested scope.
Question 115
The data platform team is assessing this situation: A developer claims SELECT access but DENY and inherited role memberships produce an unexpected effective permission. Which Azure SQL service or administration concept most precisely fits this situation?
- Role and permission audit
- Group-based SQL database role
- Contained SQL user versus server login
- Execute-as user diagnostics
Explanation
Correct Answer
A:Role and permission audit matches the precise requirement: a developer claims SELECT access but DENY and inherited role memberships produce an unexpected effective permission. Conflicting privileges can be explained without guessing from one role name. Important scope limit: A DENY can override a GRANT and exceptions depend on security context.
Incorrect Answers
B:Group-based SQL database role applies when several engineers need identical read-only data access without individually maintained GRANT statements, not when a developer claims SELECT access but DENY and inherited role memberships produce an unexpected effective permission.
C:Contained SQL user versus server login applies when an Azure SQL Database connection uses a contained database user and administrators expect it to appear in server-level logins, not when a developer claims SELECT access but DENY and inherited role memberships produce an unexpected effective permission.
D:Execute-as user diagnostics applies when a stored procedure works for its owner but fails on a permission check for an ordinary application user, not when a developer claims SELECT access but DENY and inherited role memberships produce an unexpected effective permission.
Question 116
A database architecture review reports the following requirement: A legacy SQL application uses password credentials that need controlled rotation and secure storage. Which Azure SQL service or administration concept most precisely fits this situation?
- Contained Entra database user
- Minimum object permission
- SQL authentication policy
- Contained SQL user versus server login
Explanation
Correct Answer
C:SQL authentication policy matches the precise requirement: a legacy SQL application uses password credentials that need controlled rotation and secure storage. Credential exposure risk can be reduced while the legacy application remains supported. Important scope limit: Password-only SQL authentication does not supply Microsoft Entra conditional access.
Incorrect Answers
A:Contained Entra database user applies when a service principal successfully obtains an Entra token but receives a database user-not-found error, not when a legacy SQL application uses password credentials that need controlled rotation and secure storage.
B:Minimum object permission applies when a report service must read one approved view but currently has db_owner membership, not when a legacy SQL application uses password credentials that need controlled rotation and secure storage.
D:Contained SQL user versus server login applies when an Azure SQL Database connection uses a contained database user and administrators expect it to appear in server-level logins, not when a legacy SQL application uses password credentials that need controlled rotation and secure storage.
Question 117
A Microsoft Azure SQL solution proposal begins with this condition: A stored procedure works for its owner but fails on a permission check for an ordinary application user. Which Azure SQL service or administration concept most precisely fits this situation?
- Execute-as user diagnostics
- Authentication troubleshooting using token
- Role and permission audit
- Minimum object permission
Explanation
Correct Answer
A:Execute-as user diagnostics matches the precise requirement: a stored procedure works for its owner but fails on a permission check for an ordinary application user. The DBA isolates object permission differences behind the failure. Important scope limit: Using the dbo context can hide access weaknesses seen by normal users.
Incorrect Answers
B:Authentication troubleshooting using token applies when a managed identity reaches the SQL endpoint but a connection fails due to the wrong database principal or requested scope, not when a stored procedure works for its owner but fails on a permission check for an ordinary application user.
C:Role and permission audit applies when a developer claims SELECT access but DENY and inherited role memberships produce an unexpected effective permission, not when a stored procedure works for its owner but fails on a permission check for an ordinary application user.
D:Minimum object permission applies when a report service must read one approved view but currently has db_owner membership, not when a stored procedure works for its owner but fails on a permission check for an ordinary application user.
Question 118
A production database review needs evidence of this condition: An Azure SQL logical server requires central identity administration before Microsoft Entra database accounts can be provisioned. Which diagnostic artifact would most directly validate the stated condition?
- Effective permission queries and role-membership hierarchy
- Logical-server Microsoft Entra administrator configuration and successful token-based sign-in
- sys.database_principals and relevant server-level principal inventory
- sys.database_role_members and effective SELECT privileges on the reporting view
Explanation
Correct Answer
B:Logical-server Microsoft Entra administrator configuration and successful token-based sign-in directly tests the observation that an Azure SQL logical server requires central identity administration before Microsoft Entra database accounts can be provisioned. It helps the team evaluate whether it should configure an appropriate Microsoft Entra administrator for the Azure SQL resource. The check has a boundary: An Entra administrator does not make every directory user a database reader automatically.
Incorrect Answers
A:Effective permission queries and role-membership hierarchy applies when a developer claims SELECT access but DENY and inherited role memberships produce an unexpected effective permission, not when an Azure SQL logical server requires central identity administration before Microsoft Entra database accounts can be provisioned.
C:Sys.database_principals and relevant server-level principal inventory applies when an Azure SQL Database connection uses a contained database user and administrators expect it to appear in server-level logins, not when an Azure SQL logical server requires central identity administration before Microsoft Entra database accounts can be provisioned.
D:Sys.database_role_members and effective SELECT privileges on the reporting view applies when a report service must read one approved view but currently has db_owner membership, not when an Azure SQL logical server requires central identity administration before Microsoft Entra database accounts can be provisioned.
Question 119
Two independent Azure SQL administration tickets require separate actions. Case A: A service principal successfully obtains an Entra token but receives a database user-not-found error. Case B: A legacy SQL application uses password credentials that need controlled rotation and secure storage. Select exactly TWO distinct implementation steps, one for each case.
- Create a suitable contained database user FROM EXTERNAL PROVIDER with required privileges
- Apply least-privileged SQL credentials with managed secret rotation where required
- Inspect explicit GRANT DENY and role inheritance for the exact securable
- Reproduce the statement under the calling principal's security context
- Configure an appropriate Microsoft Entra administrator for the Azure SQL resource
Explanation
Correct Answers
A:Create a suitable contained database user FROM EXTERNAL PROVIDER with required privileges directly resolves the reported requirement that a service principal successfully obtains an Entra token but receives a database user-not-found error. The Entra identity can be mapped to an authorized database principal. The implementation must also respect this constraint: Authentication alone does not convey table permissions.
B:Apply least-privileged SQL credentials with managed secret rotation where required directly resolves the reported requirement that a legacy SQL application uses password credentials that need controlled rotation and secure storage. Credential exposure risk can be reduced while the legacy application remains supported. The implementation must also respect this constraint: Password-only SQL authentication does not supply Microsoft Entra conditional access.
Incorrect Answers
C:Inspect explicit GRANT DENY and role inheritance for the exact securable is appropriate for the separate condition that a developer claims SELECT access but DENY and inherited role memberships produce an unexpected effective permission. The actual 2 cases are A: A service principal successfully obtains an Entra token but receives a database user-not-found error; B: A legacy SQL application uses password credentials that need controlled rotation and secure storage. This option is not the specific implementation or corrective step for any of those stated cases.
D:Reproduce the statement under the calling principal's security context is appropriate for the separate condition that a stored procedure works for its owner but fails on a permission check for an ordinary application user. The actual 2 cases are A: A service principal successfully obtains an Entra token but receives a database user-not-found error; B: A legacy SQL application uses password credentials that need controlled rotation and secure storage. This option is not the specific implementation or corrective step for any of those stated cases.
E:Configure an appropriate Microsoft Entra administrator for the Azure SQL resource is appropriate for the separate condition that an Azure SQL logical server requires central identity administration before Microsoft Entra database accounts can be provisioned. The actual 2 cases are A: A service principal successfully obtains an Entra token but receives a database user-not-found error; B: A legacy SQL application uses password credentials that need controlled rotation and secure storage. This option is not the specific implementation or corrective step for any of those stated cases.
Question 120
Three independently confirmed SQL platform issues require separate evidence checks. Case A: Several engineers need identical read-only data access without individually maintained GRANT statements. Case B: A stored procedure works for its owner but fails on a permission check for an ordinary application user. Case C: A developer claims SELECT access but DENY and inherited role memberships produce an unexpected effective permission. Select exactly THREE distinct diagnostic checks, one for each case.
- EXECUTE AS USER or effective permissions test and failed statement context
- Connection error identity claim database name and principal mapping
- Effective permission queries and role-membership hierarchy
- Microsoft Entra group membership mapped to database role membership
- sys.database_role_members and effective SELECT privileges on the reporting view
- SQL login usage inventory and secret rotation audit trail
Explanation
Correct Answers
A:EXECUTE AS USER or effective permissions test and failed statement context directly tests the observation that a stored procedure works for its owner but fails on a permission check for an ordinary application user. It helps the team evaluate whether it should reproduce the statement under the calling principal's security context. The check has a boundary: Using the dbo context can hide access weaknesses seen by normal users.
C:Effective permission queries and role-membership hierarchy directly tests the observation that a developer claims SELECT access but DENY and inherited role memberships produce an unexpected effective permission. It helps the team evaluate whether it should inspect explicit GRANT DENY and role inheritance for the exact securable. The check has a boundary: A DENY can override a GRANT and exceptions depend on security context.
D:Microsoft Entra group membership mapped to database role membership directly tests the observation that several engineers need identical read-only data access without individually maintained GRANT statements. It helps the team evaluate whether it should grant a least-privileged database role to an Entra group principal. The check has a boundary: Directory group membership changes and existing sessions may affect effective access timing.
Incorrect Answers
B:Connection error identity claim database name and principal mapping is appropriate for the separate condition that a managed identity reaches the SQL endpoint but a connection fails due to the wrong database principal or requested scope. The actual 3 cases are A: Several engineers need identical read-only data access without individually maintained GRANT statements; B: A stored procedure works for its owner but fails on a permission check for an ordinary application user; C: A developer claims SELECT access but DENY and inherited role memberships produce an unexpected effective permission. This option is not the specific diagnostic evidence for any of those stated cases.
E:sys.database_role_members and effective SELECT privileges on the reporting view is appropriate for the separate condition that a report service must read one approved view but currently has db_owner membership. The actual 3 cases are A: Several engineers need identical read-only data access without individually maintained GRANT statements; B: A stored procedure works for its owner but fails on a permission check for an ordinary application user; C: A developer claims SELECT access but DENY and inherited role memberships produce an unexpected effective permission. This option is not the specific diagnostic evidence for any of those stated cases.
F:SQL login usage inventory and secret rotation audit trail is appropriate for the separate condition that a legacy SQL application uses password credentials that need controlled rotation and secure storage. The actual 3 cases are A: Several engineers need identical read-only data access without individually maintained GRANT statements; B: A stored procedure works for its owner but fails on a permission check for an ordinary application user; C: A developer claims SELECT access but DENY and inherited role memberships produce an unexpected effective permission. This option is not the specific diagnostic evidence for any of those stated cases.
Administering Microsoft Azure SQL Solutions (DP-300) Practice Tests