HOTSPOT - For each of the following statements, select Yes if the statement is true. Otherwise, select No. NOTE: Each correct selection is worth one point. Hot Area:
All statements are correct
Here’s why:
Atomicity: In a transactional database that guarantees atomicity, all statements in a transaction must complete successfully or the transaction must roll back. This is a fundamental property of ACID transactions.
Consistency: In a transactional database that guarantees consistency, all data changes will be logged and accounted for. This ensures that the database transitions from one valid state to another, maintaining the integrity of the data.
Isolation: In a transactional database that guarantees isolation, processes can see only data in a consistent state. This means that the concurrent execution of transactions results in a system state that would be obtained if transactions were executed serially.
These properties are part of the ACID (Atomicity, Consistency, Isolation, Durability) properties that most transactional databases aim to achieve.
In Atomicity, the transaction must not be successful. The keyword is complete but it can succeed or fail completely. It is No because the question says "must complete successfully"
it is YYY. it is the very definition of a transaction in the context of a RDBMS.
transaction: atomic, independent, consistent, durable (ACID properties).
I think there's a case for YNY because logging isn't related to consistency but my choice would be YYY because a database has to log all changes to support transactions. Rollbacks and commits are usually handled through the log: As an application makes changes, those changes are recorded in the log. When the appliction does a commit, those changes in the log are applied to the tables giving a visible and consistent result; in a rollback, those log changes are skipped. Plus, if only for audit purposes, a database has to log all changes.
How else do you ensure transactional consistency, if, according to you, "logging isn't related to consistency...?"
Apparently, you've never heard of TRANSACTION Log in MS-SQL Server, or REDO Log in Oracle Database?
PS: All the three statements are True (Yes, Yes, Yes).
After careful research, the answer I find most logical is Y,N,Y
Look at this: https://www.databricks.com/glossary/acid-transactions#:~:text=ACID%20is%20an%20acronym%20that,operations%20are%20called%20transactional%20systems.
YYY
Yes, in a transactional database that guarantees consistency, all data changes will be logged and accounted for. This is because a transactional database follows the ACID (Atomicity, Consistency, Isolation, Durability) properties, which ensures that all transactions are executed in a reliable and consistent manner.
When a transaction is executed, the database system ensures that all changes made to the data are logged in a transaction log. This log contains a record of all changes made during the transaction, including updates, inserts, and deletions. If any part of the transaction fails, the database system uses the transaction log to roll back the transaction and undo any changes that were made.
By logging all data changes, the database system can ensure that the data remains consistent and that no data is lost or corrupted. In addition, the transaction log provides a history of all changes made to the data, which can be used for auditing and troubleshooting purposes.
YYY
Yes, all statements in a transaction in a transactional database that guarantees atomicity must complete successfully or the transaction must roll back.
Yes, in a transactional database that guarantees consistency, all data changes will be logged and accounted for.
Yes, in a transactional database that guarantees isolation, processes can see only data in a consistent state.
These three properties are collectively known as the ACID properties of a transactional database, and they ensure that database transactions are executed in a reliable and consistent manner. The atomicity property guarantees that transactions are all or nothing, the consistency property ensures that data is always in a valid state, and the isolation property ensures that transactions do not interfere with each other.
YNN
In a transactional database that guarantees durability, all data changes will be logged and accounted for.
In a transactional database that guarantees consistency, processes can see only data in a consistent state.
Isolation: Concurrent transactions cannot interfere with one another and must result in a consistent database state. https://learn.microsoft.com/en-us/training/modules/explore-core-data-concepts/5-transactional-data-processing So, the third option is Y.
This section is not available anymore. Please use the main Exam Page.DP-900 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
snowfox
Highly Voted 2 years, 8 months agojellybiscuit
Highly Voted 2 years, 8 months agoFdman
Most Recent 7 months, 2 weeks agoprofesorklaus
7 months, 3 weeks agoson_el
1 year, 1 month agojppdks
1 year, 3 months ago984d4d8
8 months, 2 weeks agoAnuragsharma83
1 year, 7 months agojaszi
1 year, 7 months agoKingcrimson1
1 year, 7 months agotestdumps2017
1 year, 9 months agophvogel
1 year, 10 months agoYomzie
1 year, 2 months agoDataEngDP
1 year, 12 months agoAbhifzd
2 years agotangerine141
2 years, 2 months agoAzurre
2 years, 2 months agoPinha
2 years, 3 months agoDusica
2 years, 5 months agofarfan
2 years, 5 months ago