Adobe Exam AD0-E717 Topic 2 Question 39 Discussion

Actual exam question for Adobe's AD0-E717 exam

Question #: 39
Topic #: 2

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?

ADefine onCreate='migrateDataFromAnotherTable(old_table_name)' attribute in the table tag.

BDeclarative schema supports RENAME TABLE', so the data will be migrated to the new table automatically.

CDefine the table and columns mapping in the db.schema_whitelist.json

Show Suggested 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 Nu at Nov 14, 2024, 07:26 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Glenn

2 months ago

Is it just me, or does option A sound like something a developer would come up with after a long night of debugging? 'Migratedata' is not a real function, is it?

upvoted 0 times

Bernardine

2 months ago

I think Option B is the safest bet, let the schema handle the migration automatically.

upvoted 0 times

...

Herminia

2 months ago

Option A does sound a bit sketchy, but maybe it's a creative solution.

upvoted 0 times

...

Amira

3 months ago

I'm not sure, but I think option A could also work if the developer wants more control over the data migration process.

upvoted 0 times

...

Vanesa

3 months ago

I agree with Louis, option B seems like the safest option to prevent data loss.

upvoted 0 times

...

Delmy

3 months ago

Option B all the way! Automatic data migration? Sign me up! Though I do wonder if the database has a 'rename' superpower or something.

upvoted 0 times

...

Twana

3 months ago

C looks like the way to go. Mapping the table and column names in the schema file is a clean and reliable approach.

upvoted 0 times

Georgeanna

2 months ago

C) Define the table and columns mapping in the db.schema_whitelist.json

upvoted 0 times

...

Silva

2 months ago

B) Declarative schema supports RENAME TABLE', so the data will be migrated to the new table automatically.

upvoted 0 times

...

Wendell

2 months ago

A) Define onCreate=migrateDataFromAnotherTable(old_table_name) attribute in the table tag.

upvoted 0 times

...

Louis

3 months ago

I think option B is the best choice because it says the data will be migrated automatically.

upvoted 0 times

...

Christiane

3 months ago

Option A sounds interesting, but I'm not sure if that's a valid action. Defining an onCreate attribute to migrate data seems a bit hacky.

upvoted 0 times

Elenor

3 months ago

I agree, option A does seem like a workaround. Option B sounds more reliable for preventing data loss.

upvoted 0 times

...

Roy

3 months ago

C) Define the table and columns mapping in the db.schema_whitelist.json

upvoted 0 times

...

Helga

3 months ago

B) Declarative schema supports RENAME TABLE', so the data will be migrated to the new table automatically.

upvoted 0 times

...

Tijuana

3 months ago

A) Define onCreate=`migrateDataFromAnotherTable(old_table_name)` attribute in the table tag.

upvoted 0 times

...

Bernardo

3 months ago

I think option B is the correct answer. Declarative schema supports RENAME TABLE, so the data will be automatically migrated to the new table.

upvoted 0 times

Teri

3 months ago

I'm not sure, but I think option B is more reliable in this case.

upvoted 0 times

...

James

3 months ago

But what about option A? Would that also work?

upvoted 0 times

...

Phillip

3 months ago

I think so too, it's the safest option to prevent data loss.

upvoted 0 times

...

Shawn

3 months ago

I agree, option B seems like the best choice.

upvoted 0 times

...