New Year Sale ! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

SAP Exam C_DBADM_2404 Topic 1 Question 2 Discussion

Actual exam question for SAP's C_DBADM_2404 exam
Question #: 2
Topic #: 1
[All C_DBADM_2404 Questions]

Which scenarios are supported for a database copy using backup and recovery from a source machine to a target machine? Note: There are 2 correct answers to this question.

Show Suggested Answer Hide Answer
Suggested Answer: B, C

Contribute your Thoughts:

Corinne
6 months ago
I actually think you're right, Eve. Different CPU architectures should be manageable too.
upvoted 0 times
...
Sue
6 months ago
Haha, this question is like a riddle wrapped in a mystery inside an enigma. But I'll go with B and D - can't mix and match the SID and version, that's for sure!
upvoted 0 times
Pok
6 months ago
Yeah, it's like trying to fit a square peg in a round hole.
upvoted 0 times
...
Joni
6 months ago
D) The source system release version is higher than the target system.
upvoted 0 times
...
Yvonne
6 months ago
Definitely, it's important to make sure they match when doing a database copy.
upvoted 0 times
...
Albina
6 months ago
I agree, mixing SIDs and versions can cause a lot of issues.
upvoted 0 times
...
Kayleigh
6 months ago
A) The source system has more nodes than the target system.
upvoted 0 times
...
Douglass
6 months ago
Yeah, you're right. Mixing SIDs and versions can cause issues.
upvoted 0 times
...
Jutta
6 months ago
I think B and D are the correct answers.
upvoted 0 times
...
...
Rolf
7 months ago
I'm not sure about that. I think the correct answers might be different SIDs and different CPU architecture.
upvoted 0 times
...
Stephaine
7 months ago
What about the source system having more nodes than the target system? I feel like it could still work.
upvoted 0 times
...
Izetta
7 months ago
Ah, the age-old debate of 'Can I restore a database to a system with a different architecture?' B and D seem like the way to go here.
upvoted 0 times
...
Beckie
7 months ago
I'm going with B and C. As long as the hardware is compatible, you should be able to restore the database, even if the CPUs are different.
upvoted 0 times
Elena
6 months ago
Yes, I think sticking with B and C would be the best choice.
upvoted 0 times
...
Ruthann
6 months ago
That makes sense. So, B and C are the safest options for database copy.
upvoted 0 times
...
Lyndia
6 months ago
I think A might not be supported because of the different number of nodes.
upvoted 0 times
...
Carmela
7 months ago
I'm not sure about A, but I think D might cause compatibility issues.
upvoted 0 times
...
Fallon
7 months ago
What about A and D? Do you think those scenarios are supported?
upvoted 0 times
...
Jackie
7 months ago
B) The source system and target system have different SIDS.
upvoted 0 times
...
Tayna
7 months ago
I agree, as long as the hardware is compatible, it should work.
upvoted 0 times
...
Telma
7 months ago
B) The source system and target system have different SIDS.
upvoted 0 times
...
Lizette
7 months ago
I think B and C are the correct answers.
upvoted 0 times
...
...
Tula
7 months ago
I think the correct answers are B and D. The SID and version should match, but the CPU architecture can be different.
upvoted 0 times
...
Tonette
7 months ago
I agree, Different SIDs shouldn't be an issue for backup and recovery.
upvoted 0 times
...
Glenna
7 months ago
Totally. I think one correct answer is the source and target systems having different SIDs. It makes sense.
upvoted 0 times
...
Carma
7 months ago
This question about database copy scenarios seems tricky.
upvoted 0 times
...
Sang
8 months ago
D) The source system release version is higher than the target system.
upvoted 0 times
...
Dalene
8 months ago
A) The source system has more nodes than the target system.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77