Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Adobe AD0-E717 Exam - Topic 10 Question 47 Discussion

In a new release of a module, a developer decides to rename a table that was defined in the earlier versions. Which action, if any, allows the developer to prevent data loss?
C) Define the table and columns mapping in the db.schema_whitelist.json
A) Define onCreate='migrateDataFromAnotherTable(old_table_name)' attribute in the table tag.
B) Declarative schema supports RENAME TABLE', so the data will be migrated to the new table automatically.

Adobe AD0-E717 Exam - Topic 10 Question 47 Discussion

Actual exam question for Adobe's AD0-E717 exam
Question #: 47
Topic #: 10
[All AD0-E717 Questions]

In a new release of a module, a developer decides to rename a table that was defined in the earlier versions. Which action, if any, allows the developer to prevent data loss?

Show Suggested Answer Hide Answer
Suggested Answer: C

When renaming a table in Magento, to prevent data loss, the developer must define the table and its columns mapping in the db_schema_whitelist.json file. This declarative schema approach ensures that the data migration tool knows about the changes and can migrate data from the old table to the newly named table without losing any data.


by Barb at May 04, 2025, 11:30 AM

Limited Time Offer

25%

Off

Get Premium AD0-E717 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Jannette
6 months ago
Wait, can you really just rename it without losing data?
upvoted 0 times
...
Jacki
6 months ago
I think A is a good option too, but B seems safer.
upvoted 0 times
...
Kate
6 months ago
B is correct, RENAME TABLE handles it automatically.
upvoted 0 times
...
Selma
6 months ago
Definitely going with B, no doubt about it!
upvoted 0 times
...
Vinnie
7 months ago
C sounds interesting, but I’m not sure it’s necessary here.
upvoted 0 times
...
Chi
7 months ago
I'm a bit confused about the options. I thought renaming a table would always require some manual migration steps, but maybe option B is the exception?
upvoted 0 times
...
Glendora
7 months ago
I feel like I saw a similar question in our practice tests, but I can't recall if the db.schema_whitelist.json mapping is really necessary for this scenario.
upvoted 0 times
...
Dyan
7 months ago
I think option B sounds familiar because we discussed how declarative schema can handle renaming tables automatically. That might be the safest choice.
upvoted 0 times
...
Erasmo
7 months ago
I remember something about using the onCreate attribute to handle data migration, but I'm not entirely sure if that's the best approach here.
upvoted 0 times
...
Denny
8 months ago
I think the key here is to prevent data loss. Option B seems like the safest bet, since it should automatically migrate the data to the new table. But I'll double-check the other options just to be sure.
upvoted 0 times
...
Isaiah
8 months ago
I'm a bit confused by this question. I'm not familiar with the RENAME TABLE feature in declarative schema. I'll need to do some research on that before I can confidently answer this.
upvoted 0 times
...
Nada
8 months ago
Okay, let me see. I think option A might work, where you define an onCreate migration to move the data from the old table to the new one. But I'm not 100% sure if that's the best approach.
upvoted 0 times
...
Lauran
8 months ago
Hmm, I'm not sure about this one. I'll have to think it through carefully. Maybe I should review the module documentation again to see if there are any other options.
upvoted 0 times
...
Ariel
8 months ago
I'm pretty confident that the answer is B. Declarative schema supports RENAME TABLE, so the data should be migrated to the new table automatically.
upvoted 0 times
...
Luisa
12 months ago
Option B is the way to go. Declarative schema is the future, and it should handle this kind of migration seamlessly.
upvoted 0 times
Stephaine
11 months ago
C) Define the table and columns mapping in the db.schema_whitelist.json
upvoted 0 times
...
Richelle
11 months ago
B) Declarative schema is definitely the way to go for seamless migration.
upvoted 0 times
...
Beata
11 months ago
A) Define onCreate=\'migrateDataFromAnotherTable(old_table_name)\' attribute in the table tag.
upvoted 0 times
...
Launa
11 months ago
B) Declarative schema supports RENAME TABLE', so the data will be migrated to the new table automatically.
upvoted 0 times
...
...
Sabrina
1 year ago
I'm not sure, but I think option A could also work if the developer ensures data migration is handled properly in the onCreate function.
upvoted 0 times
...
Francesco
1 year ago
I agree with Caprice, option B seems like the safest option to prevent data loss during the table renaming process.
upvoted 0 times
...
Caprice
1 year ago
I think option B is the best choice because it supports renaming the table without losing data.
upvoted 0 times
...
Nenita
1 year ago
Haha, Option A is hilarious! Migrating data from another table? That's just asking for trouble.
upvoted 0 times
...
Stephanie
1 year ago
I think Option C is the way to go. Defining the table and column mapping is a more reliable way to handle schema changes.
upvoted 0 times
Tasia
1 year ago
Defining the mapping in the JSON file can help ensure smooth data migration.
upvoted 0 times
...
Luann
1 year ago
I think using db.schema_whitelist.json is a good practice for preventing data loss.
upvoted 0 times
...
Aron
1 year ago
I agree, Option C seems like the most reliable choice.
upvoted 0 times
...
...
Kirk
1 year ago
Option B seems correct, but I'm not sure if it's supported in all database systems.
upvoted 0 times
...

Save Cancel