Confused for the following question.PLease let me know the correct option

What do you think would be the best 2 options of those available? Can you explain your thinking, and why you are confused?

Quality is the responsibility of the Development team and they should undertake testing themselves to the best of their abilities is the answer.

Is lacking an specialist in some area of knowledge an impedimet for the development team to perform their work towards the sprint goal and based on the DoD?

An specialist is someone with high skills on some specific domain. It will be helpful for the team to have someone skilled on testing/quality so their work can be tested faster and better, however Dev Teams in scrum claim to be cross-functional. That means that even if they have not specialists within their lines they are still capable of performing work on other non-specialized areas at some level so that the SBI's end up being "done". Remember "done" based on the DoD considering that some quality is needed/defined to reach it (I'm assuming so since it is almost a must that sw is tested at some quality level) and it is applied to all items in development for the current sprint. Notice that the question does not mention at which part of the sprint the dev team is raising this issue.

Also, the dev team members try to do things on their own better than turning to others who are not part of the team. 

I believe these thoughts yeld to the two correct answers. Please correct me if I'm wrong.

Scrum Team is cross-functional. So, each and every team member is responsible for quality and value-driven delivery.

Considering that the Dev Team is supposed to be a team of cross functional developers, meaning no specialists and no restricted responsibilities; what answers go along with that? More importantly, are there choices within the answers given that goes against that principle? 

Lets go with an approach of removing the incorrect options. In my opinion :

Option#1: "Request for a specialist tester to join the team and queue testing for them to do when they arrive in a later Sprint"

My view: This option is wrong based on "specialist", since dev team are cross functional and when the increment created in a sprint involves end to end implementation.

Option#3: "Produce an Increment that will be tested by a dedicated test team after the Sprint to guarantee the quality"

My View: This option is wrong based on "dedicated test team", since dev team are cross functional and when the increment created in a sprint involves end to end implementation.

Hence Option#2 and Option#4 are the correct options.

+1

I had the same question about this.  I thought the answer was "Quality is the responsibility of the Development team and they should undertake testing themselves to the best of their abilities".  Then I saw the instruction "Pick 2".

1 & 4. The development team doesn't mean developers. It the entire scrum team that's called as Development team.

If tester is not there then it is NOT an impediment (unless it is penetration or some kind of specialised testing). 

You may request for a dedicated tester but the budget allows it. But it is optional for a scrum team to have a dedicated tester. All that matters at the end of the sprint is a good, well created MVP.

Request for a specialist tester to join the team and queue testing for them to do when they arrive in a later Sprint

The reason why this is not the correct answer is because all work including testing needs to be "done" in the current Sprint, not a later Sprint.  The Increment needs to meet the definition of "Done" by the end of the Sprint.  Later Testing Sprints are known as Scrumbuts.

All that matters at the end of the sprint is a good, well created MVP.

What is one of the most important concepts of Scrum I teach to Development Teams is to build a "done" Increment every Sprint.  The importance of "done" is critical for them to learn, to get to a cadence and culture of "done", versus Zombie Scrum where there is no beating heart.

Regarding Minimal Viable Product (MVP), it should be an Increment that satisfies the early adopters of your product.  The MVP will take at least one Sprint, usually more.  Once the MVP is delivered, there are no more MVPs for your product.  Every Increment afterwards informs the Product Owner, and the Product Backlog emerges from that based on learnings and empiricism.  

The development team doesn't mean developers. It the entire scrum team that's called as Development team.

The development team may include developers, QAs, BAs. Even PO and SM can be part of development team. You are incorrect however to state that the entire scrum team is called development team. A Scrum team consists of DT, PO, SM.

If tester is not there then it is NOT an impediment (unless it is penetration or some kind of specialised testing). 

It actually is an impediment. In all of the software develeopment setups I've been part of (or heard of), there was at least a tester (some were dedicated to the team, others were shared - depending on the company and the internal setup).

Would the software Scrum teams (note I'm referring to software alone, as Scrum can be applied to other instances) truly be cross-functional in the absence of testers? In the vast majority of cases, they definitely would not be.

"The Increment needs to meet the definition of "Done" by the end of the Sprint" 

Yes wanted to say this only. you have put it better. Thanks