MENU
The following LOGISTIC procedure output analyzes the relationship between a binary response and an ordinal predictor variable, wrist_size Using reference cell coding, the analyst selects Large (L) as the reference level.
What is the estimated logit for a person with large wrist size?
Click the calculator button to display a calculator if needed.
Suggested Answer: D
Get Premium A00-240 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
12 comments · newest first
WE
Wenona
12 months ago
Totally agree, -1.0415 makes sense here!
LO
Lorenza
12 months ago
Wait, is -3.7727 even possible?
JO
Johnna
1 year ago
Definitely going with 0.5663!
HO
Hortencia
1 year ago
I think the estimated logit is -1.0415.
IR
Iraida
1 year ago
The reference level is Large (L).
EL
Elroy
1 year ago
I vaguely remember that the logit for the reference category is often not explicitly listed in the output. I wonder if that means I should be looking for a negative value like -1.0415 instead.
MA
Marvel
1 year ago
If Large is the reference level, then I believe the logit for that category should be the intercept. I think it might be around 0.0819, but I need to double-check my notes.
BR
Britt
1 year ago
I remember that when using reference cell coding, the reference level's logit is usually set to zero, but I'm not completely sure how that affects the calculation here.
EM
Emiko
1 year ago
I think we practiced a similar question where we had to interpret logits for different categories. I feel like the logit for large wrist size might be one of the negative values, but I can't recall exactly.
MA
Mayra
1 year ago
I'm a little confused on this one. I know the invoice date is part of the header, but I'm not sure about the other options. I'll have to make an educated guess.
RO
Rosendo
1 year ago
I feel like option A is misleading; I thought AWSR used more than just IP addresses for differentiating deployments.
FL
Florinda
1 year ago
This is a tricky one. I'm not super familiar with Azure Cosmos DB, so I'll have to rely on my general troubleshooting skills. I'm going to eliminate the options that seem unrelated to the problem, and then carefully consider the remaining ones to pick the best solution.