시간 관리 및 검토 기법

130분 시간 배분

# Recommended time allocation:
# Minutes 0-90:   Answer all 65 questions in sequence
#   - Easy questions: 60-90 seconds each (bank extra time)
#   - Medium questions: 2 minutes each
#   - Hard/uncertain questions: max 3 minutes, then flag and move on
# Minutes 90-120: Review ALL flagged questions
# Minutes 120-130: Final scan for unanswered questions and obvious errors

표시하고 넘어가기 전략

# Flagging decision tree:
# Read question + answers
#   Can I eliminate 2 answers in 30 seconds? -> Yes: narrow to 2, choose best, optionally flag
#   Do I know the answer confidently? -> Yes: answer and move on (no flag)
#   Am I still uncertain after 2 minutes? -> Flag, select best guess, MOVE ON
#   Have I eliminated nothing? -> Select least-wrong option, flag, MOVE ON immediately

시간 배분 점검 지점

# Pacing checkpoints:
# After Q20: should be at ~40 min elapsed (2 min/q average)
# After Q40: should be at ~80 min elapsed
# After Q60: should be at ~120 min elapsed
# If behind at Q40 by more than 10 minutes:
#   Speed up immediately on remaining questions
#   Flag fewer questions; only flag when genuinely 50/50 uncertain
# If ahead: use extra time for deeper analysis on remaining questions

긴 시나리오형 문제 읽기

# Efficient scenario reading technique:
# Step 1: Read the LAST SENTENCE (the actual question)
# Step 2: Skim the scenario for constraint keywords:
#   - Resource type: compute / storage / database / network
#   - Access pattern: read-heavy / write-heavy / bursty / steady
#   - Operational: least overhead / no server management
#   - Cost: most cost-effective / minimise spend
#   - Availability: no downtime / multi-AZ / multi-region
# Step 3: Read the four answers with those constraints in mind
# Step 4: Eliminate distractors using the identified constraints

복수 응답형 문제 풀이

# Multiple-response strategy:
# Step 1: Note how many answers to select ('Choose TWO')
# Step 2: Eliminate clearly wrong options (target: eliminate at least 2)
# Step 3: From remaining, look for complementary answers that each address a different requirement
# Step 4: Avoid selecting two answers that do the same thing (redundant)
# Step 5: If you must guess on the last selection, pick the one that most directly addresses
#         the primary stated constraint

답을 바꾸는 실수 피하기

# Answer-changing rule:
# CHANGE: Only if you now recall a specific fact that changes the answer
# CHANGE: Only if you misread a key word (e.g., 'NOT' vs. 'most')
# CHANGE: Only if a later question provided clarifying context
#
# DO NOT CHANGE: Because of vague uncertainty
# DO NOT CHANGE: Because you think the answer 'looks wrong'
# DO NOT CHANGE: To balance the distribution of A/B/C/D answers
# Statistic: answer changes are wrong 60-70% of the time on average

메모장 / 화이트보드 활용하기

# Whiteboard usage examples:
# Flagged question shorthand:
# Q23: A vs C | constraint: no-code-change + lowest-cost
#
# Architecture sketch for VPC questions:
# [Internet] -> [IGW] -> [Public Subnet: ALB] -> [Private Subnet: EC2] -> [RDS]
#
# Shard calculation:
# Write: 8 MB/s -> 8 shards (write-bound)
# Read: 3 consumers x 4 MB/s = 12 MB/s -> 6 shards (read-bound)
# Need: max(8, 6) = 8 shards

마지막 10분

# Final 10-minute checklist:
# [ ] Review all flagged questions (prioritise)
# [ ] Verify no unanswered questions remain (scroll through all)
# [ ] For any still uncertain: choose the managed service over self-managed
# [ ] For any still uncertain: choose the AWS-native solution over third-party
# [ ] Do NOT change confident answers without a specific reason
# [ ] Check that multiple-response questions have the exact required number selected
# [ ] When satisfied: submit confidently

시험 전 준비 루틴

시험 후: 성적 보고서

모의 시험과 취약 영역 집중 학습

빠른 확인

레슨 요약