✅ The answer is B) Convert the Lookup to Master-Detail, then create the Roll-Up Summary field. This is the most-tested data-modeling rule on the Admin exam, so let's lock down why — and why each other option fails.
The core rule: a declarative Roll-Up Summary field can only live on the MASTER side of a Master-Detail relationship. A Lookup has no built-in roll-up. So before you can SUM those Invoice Amounts onto the Account, the relationship itself has to be Master-Detail.
Roll-Up Summary 101:
• Lives on the parent (master), aggregates the child (detail) records.
• Four operations: COUNT, SUM, MIN, MAX (with optional filter criteria).
• Requires Master-Detail — full stop. Lookup ≠ roll-up summary declaratively.
Converting Lookup → Master-Detail (classic gotcha):
• Every existing child must already have a parent populated — no orphans, or the conversion is blocked.
• The relationship field effectively becomes required on the child.
• The child then inherits the parent's sharing & security, loses its own Owner field, and is subject to cascade delete (delete the Account, its Invoices go too).
• Limits: up to 2 master-detail relationships per object; a cap on roll-up fields per object (default 25, can vary by edition).
Why the others lose:
❌ A) "Works on any relationship" — false. Roll-Up Summary does NOT work on Lookup. The trap answer.
❌ C) Apex trigger — could technically sum a Lookup's children, but the scenario says declaratively, no code. Wrong tool, not the first step.
❌ D) Formula field — a cross-object formula reaches UP from child to one parent, not DOWN to aggregate many children. It can't SUM a set of child records.
Honest footnote: if you truly can't convert (e.g., the child already has another master), the declarative alternative is a Record-Triggered Flow that recalculates the parent total. But on the EXAM, "Lookup + need a SUM + declarative" → convert to Master-Detail and use a Roll-Up Summary.
Bottom line: "Sum/count child records, declaratively, on the parent" → Roll-Up Summary → which requires Master-Detail. See the word Lookup in that scenario? Your first move is convert to Master-Detail (after confirming every child has a parent).
📱 Data modeling, the sharing model, Flow automation, reports and 600+ real Admin questions with full explanations on RUOK SF Admin:
https://t.co/6tnPt3b5gG
Hey everyone, Kevin from RUOK's cert prep team here! Happy Friday — as the Summer '26 features keep landing in production orgs this month, it's the perfect time to drill the data-modeling fundamentals the exam never stops testing. Today's one trips up a TON of Admins: when you can (and can't) build a roll-up summary. Get this and you'll never misread a "sum the child records" scenario again. Salesforce Certified Administrator focus.
🎯 Layer B Quiz: Roll up that total
You have a custom object Invoice that currently has a Lookup relationship to Account. You need a field on the Account that automatically SUMs the Amount of all related Invoices and recalculates whenever an invoice changes — declaratively, no code. What must you do FIRST?
A) Just create a Roll-Up Summary field on Account — it works on any relationship
B) Convert the Lookup to a Master-Detail relationship, then create the Roll-Up Summary field
C) Write an Apex trigger on Invoice to update the Account
D) Add a formula field on Account that references the child records
Answer below 👇
#Salesforce #SFAdmin #SalesforceCertified #AdminExam
答え: C
居住用財産の特例は「所有期間がどこで効くか」で整理すると迷いません。
C ○ 軽減税率の特例(措法31条の3)は、譲渡した年の1月1日時点で所有期間が10年を超えていることが要件です。「譲渡日」ではなく「1月1日基準」がポイント。
A × 3,000万円特別控除(措法35条)は所有期間の長短を問わず適用できます。10年超の要件があるのは軽減税率のほう。両者の要件を入れ替えるのが定番のひっかけ。
B × 配偶者・直系血族など特別の関係者への譲渡には3,000万円特別控除は適用されません。「配偶者に譲渡しても適用できる」は誤り。
D × 3,000万円特別控除と軽減税率の特例は重複適用(併用)できます。「いずれか一方しか適用できない」は誤り。なお買換え特例とは併用できない点も合わせて押さえましょう。
「3,000万円控除=所有期間問わず/軽減税率=1/1で10年超」「両者は併用可」を軸に、宅建リベンジの過去問で居住用財産の特例を一気に固めましょう。
👉 https://t.co/w4BcLu8asB
#宅建 #税その他
RUOK(るおく)の宅建試験支援担当・田中葵です!週末は腰を据えて税その他を固める好機ですね。去年の私は「3,000万円控除と軽減税率って一緒に使えたっけ?」で毎回手が止まっていました。居住用財産の特例は"所有期間がどこで効くか"を整理すると一気にスッキリします。
【4択クイズ|税その他(所得税・居住用財産の譲渡)】
個人が居住用財産(マイホーム)を譲渡した場合の所得税の特例に関する次の記述のうち、正しいものはどれですか。
A. 居住用財産を譲渡した場合の3,000万円特別控除は、譲渡した居住用財産の所有期間が10年を超えていなければ適用を受けることができない。
B. 居住用財産を配偶者に譲渡した場合であっても、3,000万円特別控除の適用を受けることができる。
C. 居住用財産を譲渡した場合の軽減税率の特例は、譲渡した年の1月1日において所有期間が10年を超える場合に適用を受けることができる。
D. 3,000万円特別控除と軽減税率の特例は、いずれか一方しか適用できず、重複して適用することはできない。
答えと解説はリプ欄で👇
#宅建 #宅建試験 #宅建2026 #宅建リベンジ #税その他
Salesforce認定管理者の佐藤美咲です。今日の一問です。
営業部から『商談(Opportunity)を8万件、一括で取り込みたい』と相談が。最も適切なツールは?
A) データインポートウィザード
B) データローダ
C) レポートのエクスポート
D) インライン編集
答えと理由はリプライに。
#Salesforce
✅ The answer is C) Partial Copy Sandbox — the one type built for "realistic SAMPLE data + a fairly frequent refresh." Let's lock down all four so you never second-guess the scenario.
The exam tests two things per sandbox: (1) does it copy production DATA? and (2) how often can you REFRESH it?
• Developer — Metadata only, NO production data. ~200 MB. Refresh: 1 day. Solo build/test, no real records.
• Developer Pro — Metadata only, NO production data, more storage (~1 GB). Refresh: 1 day. Bigger build/test or your own loaded test data — still no production copy.
• Partial Copy — Metadata + a SAMPLE of production data via a sandbox template (you pick the objects), up to 10,000 records per selected object, ~5 GB. Refresh: 5 days. The UAT/QA sweet spot. ← your scenario.
• Full — A COMPLETE copy of production (all data + metadata). Refresh: 29 days. For perf/load testing and staging — but only refreshable ~once a month.
Decision rule: need real data? → Partial Copy or Full (Dev/Dev Pro have none). Representative sample + frequent refresh? → Partial Copy. Exact full-scale replica? → Full (accept the 29-day wait).
Why the others lose:
❌ A) Developer — copies no production data at all. Testers get an empty org.
❌ B) Developer Pro — same, just more storage. More room ≠ real records.
❌ D) Full — has real data, but it's a complete copy (not a sample) and refreshes only every 29 days — too heavy and too slow to re-sync for your case.
Exam quick-fire (Summer '26 / Platform Administrator — Environments):
• Sandbox templates apply to Partial Copy + Full only (they pick which objects' data to copy).
• Refresh interval = minimum wait between refreshes: Dev/Dev Pro 1 day, Partial 5 days, Full 29 days.
• A refreshed sandbox is a fresh, separate org — record IDs differ; re-check deactivated email/automation so test runs don't email real customers.
• Flow: build in Dev/Dev Pro → validate in Partial/Full (UAT) → deploy via change sets, packages, or Metadata API.
Bottom line: "representative sample of real data, refreshed every few days, for UAT" → Partial Copy.
📱 Environments & deployment, the sharing model, Flow automation, reports and 600+ real Admin questions with full explanations on RUOK SF Admin:
https://t.co/6tnPt3b5gG
Hey everyone, Kevin from RUOK's cert prep team here! Let's talk about a question that trips up Admins who've only ever worked in a single org — sandboxes. The exam loves to hand you a scenario ("test X against Y kind of data, refreshed Z often") and ask which sandbox fits. Get the four types straight and these become free points — on the exam AND on the job. Salesforce Certified Administrator focus.
🎯 Layer B Quiz: Which Sandbox for UAT?
You're prepping a release. You need a sandbox that holds a representative SAMPLE of real production data (not the whole org) so testers can run UAT against realistic records — and you want to refresh it every few days during the testing cycle. Which sandbox type fits best?
A) Developer Sandbox
B) Developer Pro Sandbox
C) Partial Copy Sandbox
D) Full Sandbox
Answer below 👇
#Salesforce #SFAdmin #SalesforceCertified #AdminExam