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

- Free Preparation Discussions

Amazon MLS-C01 Exam - Topic 3 Question 92 Discussion

Actual exam question for Amazon's MLS-C01 exam
Question #: 92
Topic #: 3
[All MLS-C01 Questions]

A law firm handles thousands of contracts every day. Every contract must be signed. Currently, a lawyer manually checks all contracts for signatures.

The law firm is developing a machine learning (ML) solution to automate signature detection for each contract. The ML solution must also provide a confidence score for each contract page.

Which Amazon Textract API action can the law firm use to generate a confidence score for each page of each contract?

Show Suggested Answer Hide Answer
Suggested Answer: A

The AnalyzeDocument API action is the best option to generate a confidence score for each page of each contract. This API action analyzes an input document for relationships between detected items. The input document can be an image file in JPEG or PNG format, or a PDF file. The output is a JSON structure that contains the extracted data from the document. The FeatureTypes parameter specifies the types of analysis to perform on the document. The available feature types are TABLES, FORMS, and SIGNATURES. By setting the FeatureTypes parameter to SIGNATURES, the API action will detect and extract information about signatures from the document. The output will include a list of SignatureDetection objects, each containing information about a detected signature, such as its location and confidence score. The confidence score is a value between 0 and 100 that indicates the probability that the detected signature is correct. The output will also include a list of Block objects, each representing a document page. Each Block object will have a Page attribute that contains the page number and a Confidence attribute that contains the confidence score for the page. The confidence score for the page is the average of the confidence scores of the blocks that are detected on the page. The law firm can use the AnalyzeDocument API action to generate a confidence score for each page of each contract by using the SIGNATURES feature type and returning the confidence scores from the SignatureDetection and Block objects.

The other options are not suitable for generating a confidence score for each page of each contract. The Prediction API call is not an Amazon Textract API action, but a generic term for making inference requests to a machine learning model. The StartDocumentAnalysis API action is used to start an asynchronous job to analyze a document. The output is a job identifier (JobId) that is used to get the results of the analysis with the GetDocumentAnalysis API action. The GetDocumentAnalysis API action is used to get the results of a document analysis started by the StartDocumentAnalysis API action. The output is a JSON structure that contains the extracted data from the document. However, both the StartDocumentAnalysis and the GetDocumentAnalysis API actions do not support the SIGNATURES feature type, and therefore cannot detect signatures or provide confidence scores for them.

References:

* AnalyzeDocument

* SignatureDetection

* Block

* Amazon Textract launches the ability to detect signatures on any document


Contribute your Thoughts:

0/2000 characters
Nidia
3 months ago
Totally agree with A, confidence scores are crucial!
upvoted 0 times
...
Caitlin
3 months ago
Wait, can ML really handle all those contracts accurately?
upvoted 0 times
...
Goldie
3 months ago
B sounds off, I don’t think Prediction API does that.
upvoted 0 times
...
Ludivina
4 months ago
I think C might be better for detecting signatures.
upvoted 0 times
...
Rozella
4 months ago
Definitely A! AnalyzeDocument is the way to go for signatures.
upvoted 0 times
...
Alex
4 months ago
I’m leaning towards option A because it mentions setting the FeatureTypes parameter to SIGNATURES, which seems relevant to our task.
upvoted 0 times
...
Iluminada
4 months ago
I feel like the GetDocumentAnalysis action might be the one we need, but I need to double-check if it actually returns confidence scores for each page.
upvoted 0 times
...
Tashia
4 months ago
I remember practicing with the StartDocumentAnalysis action, but I can't recall if it specifically provides confidence scores for signatures.
upvoted 0 times
...
Vincent
5 months ago
I think the AnalyzeDocument API action sounds familiar, but I'm not entirely sure if it's the right one for getting confidence scores.
upvoted 0 times
...
Lisandra
5 months ago
I've got a good feeling about this. The GetDocumentAnalysis API action looks like it will do the trick. I just need to use that to detect the signatures and return the confidence scores.
upvoted 0 times
...
Rhea
5 months ago
Okay, I think I've got this. The AnalyzeDocument API action is the way to go here. I just need to set the FeatureTypes parameter to SIGNATURES and I'll get the confidence scores for each page.
upvoted 0 times
...
Ligia
5 months ago
Hmm, this seems like a tricky one. I'll need to carefully review the Amazon Textract API documentation to determine the best approach.
upvoted 0 times
...
Wilda
5 months ago
I'm a bit confused on this one. Is the Prediction API the right call, or should I be using the StartDocumentAnalysis action? I'll need to double-check the requirements.
upvoted 0 times
...
Tawny
5 months ago
This looks like a tricky one. I'll need to carefully review the options and think through the security implications of each approach.
upvoted 0 times
...
Gerardo
5 months ago
I'm pretty confident that the purpose of a build tool is to compile source code into binaries and executables. That's the core function of a build tool, so I'll go with option A.
upvoted 0 times
...
Claudia
5 months ago
Hmm, I'm a bit unsure about the specific components to include in a requirements management plan. I'll need to review my notes to make sure I cover all the important elements.
upvoted 0 times
...
Antonio
2 years ago
Good points. I feel C makes more sense as it's about starting the document analysis for signatures.
upvoted 0 times
...
Trinidad
2 years ago
True, but I believe GetDocumentAnalysis is a follow-up call after starting the analysis. My guess is still on C, to initiate the process.
upvoted 0 times
...
Karan
2 years ago
Why not D? GetDocumentAnalysis also sounds reasonable for getting confidence scores per page.
upvoted 0 times
...
Theola
2 years ago
I agree with user2. AnalyzeDocument with FeatureTypes set to SIGNATURES seems logical, but C sounds like it deals with larger documents.
upvoted 0 times
...
Trinidad
2 years ago
I think it's either A or C. AnalyzeDocument sounds right, but StartDocumentAnalysis is specific to detecting signatures.
upvoted 0 times
...
Antonio
2 years ago
Wow, this question is tricky. I'm not sure which Textract API to use here.
upvoted 0 times
...

Save Cancel